These Release Notes (updated at 9:24 PM on 4/29/2021) are for everRun Release 7.6.0.0. See the following sections:
The following features are new in everRun Release 7.6.0.0:
You can add SNMPv3 users, who can enable SNMPv3 requests.
The default communication protocol is HTTPS.
When logging in to the everRun Availability Console for the first time, most browsers display one or more security messages, but you can proceed to the console. You can add a security exception later, to allow the site to load without the message(s).
EV-48962: SMD logs unnecessary messages.
EV-48473: VM(s) will not start because axstore.db has a size of 0.
EV-48341: Windows VM crashes when last available network adapter is disabled.
EV-48304: Memory leaks.
EV-48191: System Manager does not start the AX-QEMU after it was shutdown due to CoreFT Fault Handler.
EV-48006: Upgrading pre-7.5 untracked trial system will not accept full license.
EV-47903: Upgrade from 7.3.4 can hang after first node has been upgraded.
EV-47901: On systems with multiple 4k sector logical drives, data loss can occur after an upgrade to 7.5.0.5 if disk repair is attempted.
EV-47860: Guest AXs cannot communicate with each other if A-Links references were crossed.
EV-47754: System management restart causes a false node reboot alert message.
EV-47673: Private branded customization lost during node replace.
EV-47659: Performance graphs for VM IO & Disk performance under System tab is not shown correctly.
EV-47611: Interrupting and restarting mirror copy can fail.
EV-47091: Importing FT VM onto HA system cannot start due to unlicensed feature.
For a list of the CVE fixes, see Fixed CVEs.
You can upgrade to Release 7.6.0.0 from Release 7.3.4.0 or a later release.
If you are upgrading from an everRun release prior to 7.3.4.0, you must first upgrade to Release 7.3.4.0 (referring to the everRun Release 7.3.4.0 Release Notes), and then upgrade to Release 7.6.0.0 following instructions in Upgrading everRun Software.
Remove USB media before you upgrade. Guests with an attached USB media will fail to migrate during an upgrade. This prevents the upgrade from proceeding, leading to a failed upgrade.
Beginning in Release 7.5.1.1, everRun software no longer supports CentOS Releases 6.4, 6.5, and 6.6, nor RHEL Releases 6.4, 6.5, and 6.6 as guest operating systems. See Compatible Guest Operating Systems for the list of supported releases of guest operating systems.
When upgrading from version 7.5.x, an older version of Intel processor microcode may be loaded.
When upgrading to 7.6.0.0, one or more VMs may be lost. Refer to KB-9782 to upgrade to 7.6.0.0 safely.
When importing a VMware VM, you must shutdown the VM using operating system shutdown commands in addition to powering it off from the VMware console. If you shutdown the VM using only the VMware console, the import will fail.
Ubuntu 18.04 guests can be created directly or imported with no issues. However, P2V conversion and V2V conversion of Ubuntu 18.04 guest is not supported.
The mapping of the Japanese keyboards 106 and 109 may be incorrect when using IE10, IE11, or Firefox to access the everRun Availability Console. Use Chrome or remote connection software (VNC or RDP), instead.
A Windows 2016 VM with the maximum supported number of vCPUs and the maximum amount of memory will not reboot cleanly. To avoid the problem, reboot the VM using the Shutdown button (on the *Virtual Machines* page, in the bottom pane for the VM), and then restart the VM using the Start button.
The system cannot create application-consistent snapshots of VMs running Windows 2008 (32 bit) and Windows 2003 (32 bit). The system can create only crash-consistent snapshots of VMs running these operating systems.
If you use the P2V client (virt-p2v) to migrate a PM or VM from a source that is running VMware, the network driver might fail to install properly during the migration process, which leaves the VM network offline. If this happens, manually install the network driver in Device Manager. For instructions, see the Troubleshooting section of Migrating a Physical Machine or Virtual Machine to a System.
If you import a Windows-based VM with the Import/Restore Virtual Machine Wizard, the VirtIO network driver may fail to install properly the first time you start the VM, which leaves the VM network offline. If this happens, manually install the network driver in Device Manager. For instructions, see the Troubleshooting section of Importing an OVF File.
To avoid downtime, before removing a VM, always ensure that both nodes are in the running state and that neither node is in maintenance mode or in the process of synchronizing.
If you remove a VM while one node is shut down in maintenance mode, the operation may stall with the error, "There was a problem deleting vm-name." To correct the problem, you must restart the only running node.
The everRun Availability Console may improperly validate VM names to ensure that they meet the software requirements. If you are creating, reprovisioning, or renaming a VM with an unsuitable name, the operation may fail to execute.
To avoid any problems with VM operations, ensure that your VM names meet the following requirements:
After upgrading an everRun system from Release 7.3.4.x or earlier, if you insert a virtual CD (VCD) into a VM as described in Inserting a Virtual CD, the guest operating system may fail to display or mount the VCD.
This issue occurs because the guest OS is still running the QEMU hypervisor from the older version of everRun. To correct the issue, restart the guest operating system, which automatically loads the updated QEMU hypervisor. At your convenience, ensure that you restart the guest OS of each VM on your system to run the updated QEMU hypervisor.
If you are connected to the everRun Availability Console using an https URL in a Microsoft Internet Explorer or Mozilla® FireFox® browser, and you click Console after selecting a running VM from the Virtual Machines page, the message VNC: Unable to connect, retrying in n seconds may appear. To enable the VNC connection, click the https link to the VNC console page in the upper right-hand corner of the masthead, and continue with the appropriate procedure below (procedure in your browser may differ, depending on the version of your browser):
In Internet Explorer, the Security Alert wizard appears:
In FireFox, the Your connection is not secure window appears:
Click Confirm Security Exception.
The VNC console appears.
The everRun software on everRun systems does not support the exFAT File system. If you need to mount a USB medium to import or export a VM, as described in Mounting a USB Device or Network-mounted Folder on the everRun System, format the device with NTFS. (By default, most USB media are formatted with the FAT file system, which has a limited file size of 4 GB that may be too small for most VMs.)
When you remove a snapshot on an everRun system, the system must coalesce the snapshot by merging it with the next oldest snapshot. While the system is coalescing snapshots:
A user cannot start the VM associated with the snapshot(s) if the VM is currently stopped. The Start button is temporarily unavailable on the Virtual Machines page of the everRun Availability Console. So, if you need to delete a snapshot, do so while its associated VM is running, or allow the associated VM (if stopped) to remain stopped.
A user must not shutdown a VM associated with the coalescing snapshot(s). You must not shut down the associated VM from the guest operating system because doing so causes data corruption. You cannot shut down the VM using the everRun Availability Console because the console prevents you from doing so.
Avoid removing snapshots if you have an immediate need to perform any of these operations. After you remove a snapshot, wait at least 10-15 minutes before attempting any of these operations, or retry the operation if needed. You may need to wait much longer depending on the size of your volumes, the amount of VM activity, and the number of snapshots you remove.
For information about how to monitor coalescing operations that are underway, see KB-4272.
If you create and delete a snapshot of a volume that is currently in RAW format, the everRun software automatically converts the volume from RAW to QCOW3 (QCOW2v3) format. The conversion is expected because snapshots require QCOW3 format, but consider that changing the volume format may have performance implications for certain VM loads. You cannot convert a volume from QCOW3 back to RAW format.
Features in everRun Release 7.4.0.0 or higher allow you to copy VMs and export VMs that are stopped without requiring a snapshot. If routine snapshots will not be required, consider these alternatives to retain RAW format (and avoid growing the size of volume containers).
If you need to configure the network of an everRun system to work on a different subnet (for example, when shipping to another location or when reconfiguring network subnets), see KB-4264 for instructions.
When configuring the Windows QEMU guest agent, do not enable the option to save a log file during snapshots. If the QEMU guest agent attempts to create a log file during a snapshot, it may cause VSS timeouts that prevent the snapshot from completing.
When you change the IP address or netmask settings of a node as described in Configuring IP Settings, both the old and new settings are in effect until you reboot the node. Having both settings active may cause routing or connection issues.
USB 3.1 devices and USB 3.0 devices are supported only when inserted into a USB 3.0 port. Some USB devices claim to be 3.0 compatible, but are not. If you are using such a device, switch to another USB device that is 3.0 compatible.
The following Help topics have been updated since translation:
Beginning in Release 7.6.0.0, Help is available in German, Japanese, Chinese, and Portuguese.
The Stratus Customer Service Portal provides a searchable Knowledge Base with technical articles about all Stratus products, including everRun. In some cases, the Release Notes directly reference these Knowledge Base articles (for example, KB-nnnn). You can access the Customer Service Portal and the Knowledge Base articles by using your existing service portal credentials, or by creating a new user account, as follows.
To access the Knowledge Base
Log on to the Stratus Customer Service Portal at https://support.stratus.com.
If needed, create a new account as follows:
Enter your company email address and contact info, and click Register.
Your company email address must include a domain name (for example, stratus.com) for a company that is a registered customer of Stratus.
If you need assistance creating an account, contact your authorized Stratus service representative.
In the Keyword Search box, enter keywords associated with the information you need, and then click Search.
To search for an article by its KB-nnnn number, click Advanced Search. Next to Search by ID, type the article ID number (nnnn) and click Display.
If you have a technical question about everRun systems, you can find the latest technical information and online documentation at the Downloads page at https://www.stratus.com/services-support/downloads/?tab=everrun. You can also search the Knowledge Base in the Stratus Customer Service Portal at https://support.stratus.com.
If you cannot resolve your questions with these online resources, and the system is covered by a service agreement, contact your authorized Stratus service representative. For information, see the everRun Support page at https://www.stratus.com/services-support/customer-support/?tab=everrun.
Product Support and Downloads