These Release Notes (updated at 9:34 PM on 4/29/2021) are for everRun Release 7.7.0.0. See the following sections:
The following features are new in everRun Release 7.7.0.0:
For information, see New in everRun Release 7.6.1.0.
For information, see New in everRun Release 7.6.0.0.
EV-50970: A USB may still be displayed in the user interface after it is pulled. Also, attempts to attach a USB to a guest may result in the incorrect USB being attached.
EV-50954: After power is restored to a single-node system after a power outage, a VM with an attached USB device does not boot.
EV-50699: Security scan fails because SNMP services are running, even when SNMP is not configured.
EV-50555: When you change the static IP address (DNS) in the console and you then reboot the system, the previous IP address is updated in resolv.conf.
EV-50407: The algorithm that determines when to reset the biz network may take up to 24 hours for the biz network to re-negotiate its speed.
EV-50232: Virtual CD Creation Wizard garbles text and button in Japanese version.
EV-50224: Active Directory User requires Domain Administrator rights.
EV-50213: Loading a VMware exported VM results in the console reporting "failed to load volume".
EV-49949: VM-specific axstore settings are removed during a node power cycle, but not during a simple node reboot.
EV-49947: After upgrading a system to 7.6.0.0/2.0.0.0, the system no longer sends some e-Alerts, call-home messages, and SNMP traps.
EV-49916: P2V using virt-p2v 1.36.10 fails with the error "Can't have a partition outside the disk!" when attempting to transfer a disk.
EV-49898: Importing an exported VMware VM fails if the vmdk file name does not include "disk".
EV-49881: When a DNS server does not respond, an alert is sent stating that the management port lost connection, and the port state is changed to a warning, "lost connectivity with network".
EV-49868: A VM with an attached USB device will not boot after in-guest shutdown.
EV-49795: Cannot perform a one-node recovery of VMs.
EV-49423: The console should display in-progress snapshot operations. Also snapshot operations on a guest should be prevented when snapshot processing for that guest is in progress.
EV-49380: The console is inaccessible after node reboot when a guest has a large, fragmented volume.
EV-49372: LogicalDisk-1 disappears from the console after selecting “Activate foreign disk”.
EV-49361: Attempts to generate diagnostics file can cause primary node to report an out-of-memory error.
EV-47842: The Reprovision Virtual Machine wizard initially accepts container-size values that are very close to the available size of the storage group, but later reports an insufficient-space error.
EV-47590: Disk cannot be added back to its original storage group and sometimes reports size as 0 after the disk is removed by clicking "Repair", then deleted and recreated in RAID BIOS.
EV-44035: Need AVCLI command to display disk OID.
For information, see Bug Fixes in everRun Release 7.6.1.0.
For information, see Bug Fixes in everRun Release 7.6.0.1.
For information, see Bug Fixes in everRun Release 7.6.0.0.
For a list of the CVE fixes, see Fixed CVEs.
Upgrade to everRun Release 7.7.0.0 following the upgrade path for the release that is running on your system, as listed in the table below.
| Release | Upgrade Path |
|---|---|
|
Releases 7.6.1.0, 7.6.0.0, 7.5.1.1, 7.4.3.2 |
Upgrade directly to Release 7.7.0.0 following instructions in Upgrading everRun Software Using an Upgrade Kit. |
|
Releases 7.5.1.0, 7.5.0.5, 7.4.3.0, 7.4.2.0, 7.4.1.0, 7.4.0.0, 7.3.4.0 |
Upgrade to Release 7.6.1.0 first, and then upgrade to Release 7.7.0.0. For information on upgrading to Release 7.6.1.0, see the everRun Release 7.6.1.0 Release Notes and Help. |
|
Releases 7.3.2.0 and earlier |
Upgrade to Release 7.3.4.0 first, then to Release 7.6.1.0, and finally to Release 7.7.0.0. To upgrade to Release 7.3.4.0, see the everRun Release 7.3.4.0 Release Notes and Help. |
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.
The following guest operating systems are not supported in Release 7.7.0.0:
Before migrating a PM or VM using a bootable P2V client (virt-p2v) ISO file, check if any removable media (for example, floppy disks, DVD drives, or external USB disks) are attached to the source image. If removable media are attached to the source image when you attempt to migrate a PM or VM, the error message Conversion failed appears. So, deselect the media in the virt-p2v window before starting the migration. To do so, access the virt-p2v window with the sections Target properties and Fixed hard disks, and then beneath Fixed hard disks, uncheck the box in the Convert column next to the removable media. See Migrating a Physical Machine or Virtual Machine to a System, particularly the section To migrate a PM or VM to the ztC Edge system, for more information on using virt-p2v.
USB 3.1 devices are not supported. Use USB 3.0 devices, instead.
When a system running everRun Release 7.4.3.x has a VM running Windows Server 2016 with an open console session, and you upgrade the system to Release 7.7.0.0, the console session displays Guest has not initialized the display (yet) and cannot open correctly. To correct the problem, shutdown and then restart the VM, and re-open the console session.
When you import a VM using the Import/Restore Virtual Machine wizard, the maximum length of the path to the VM, including the VM name, is 4096 characters for the import options Import from remote/network Windows Share(CIFS/SMB) and Import from remote/network NFS.
If you begin to import an OVA file and then the node is placed into maintenance mode or loses power, the OVA import fails, and any future attempt to import an OVA file fails. For information on a work-around for this problem, see KB-10035.
Importing a Linux VMware OVA file changes the network interface and networks-scripts file. After you import the file, you need to manually configure the network information using the following procedure:
On the Virtual Machines page, select the VM.
Click Console in the bottom panel to open the VM login page (for additional information, see Opening a Virtual Machine Console Session).
Login into the VM.
Open a command prompt window.
Issue the ifconfig command. In the command output, check if ip address is assigned to the virtual network interface eth0.
If ip address is not assigned to eth0, list the contents of the /etc/sysconfig/network-scripts directory.
Note the value of ifcfg-xxxx (though not ifcfg-lo).
Rename ifcfg-xxxx to be ifcfg-eth0.
Edit the ifcfg-eth0 file, changing the values of DEVICE and ONBOOT, as follows:
Save the file.
Issue the following command to restart network services:
Verify the IP assignment by issuing the command ifconfig. In the command output, confirm that ip address is assigned to eth0.
When you select Import from USB in the Import/Restore Virtual Machine wizard to import an OVA file, you can enter a file name or partial file name in the Search Files box. The box lists OVA files that have names matching the name entered in the box, and that reside in various directories:
For complete information on importing an OVA file, see Importing an OVF or OVA File.
You can recover or replace a PM from a temporary Preboot Execution Environment (PXE) server on the primary PM. After the procedure is complete, the Size Available column of a Storage Group displays a negative value with the following selections in the PXE procedures:
This is a display problem. The actual size in the system is accurate. To correct the display, re-assign the disk to the storage group.
On the Virtual Machines page of the everRun Availability Console, you can open a VM console session to display the console of the guest operating system running in the VM. When you open a console session to access a guest VM with a UEFI boot type, the console session has a maximum resolution of 800x600. For a higher resolution, connect to the VM using a Remote Desktop Connection.
Though everRun Release 7.7.0.0 supports creating VMs with a UEFI boot interface, it does not support creating snapshots of UEFI VMs.
After a system is upgraded to Release 7.7.0.0 using an upgrade kit, support for vmgenid on VMs running Windows Server 2019, Windows Server 2016, or Windows Server 2012 is not present until after the VMs are restarted. Therefore, you must restart such VMs to enable vmgenid support after the upgrade.
When you are using Microsoft Edge as the browser for the everRun Availability Console you cannot create a VCD: the process will fail. Instead, use another compatible browser (see Compatible Internet Browsers).
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.
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 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.
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).
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.
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 information in Upgrading everRun From Release 7.3.4.0 with a DVD is relevant when upgrading a system to Release 7.4.x.x. It is not relevant to Release 7.7.0.0.
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