everRun Release 7.9.4.1 Release Notes

These Release Notes (updated at 10:21 AM on 12/13/2024) are for everRun Release 7.9.4.1. See the following sections:

New Features and Enhancements

New in everRun Release 7.9.4.1

Release 7.9.4.1 provides bug fixes. See Bug Fixes for information.

New in everRun Release 7.9.4.0

everRun Release 7.9.4.0 provides security improvements, including 46 Fixed CVEs.

New in everRun Release 7.9.3.1

For information, see New in everRun Release 7.9.3.1.

New in everRun Release 7.9.3.0

For information, see New in everRun Release 7.9.3.0.

New in everRun Release 7.9.2.0

For information, see New in everRun Release 7.9.2.0.

New in everRun Release 7.9.1.0

For information, see New in everRun Release 7.9.1.0.

New in everRun Release 7.9.0.0

For information, see New in everRun Release 7.9.0.0.

Bug Fixes

Bugs Fixed in everRun Release 7.9.4.1

ZTC-24802: Update the heartbeat, pils, and stonith packages to expected versions to support reliable transition into maintenance mode.

Bugs Fixed in everRun Release 7.9.4.0

ZTC-19175: An upgrade from an earlier release to everRun 7.9.3.0 will not correct Tenable ID ID 20007 (SSL/TLS). The VM console connection is still using TLSv1.0 and TLSv1.1.

ZTC-19562: Windows guests may hang and be lost if APICv is enabled. APICv is now disabled by default.

ZTC-22566: Increase security of root accounts encryption method from md5 to sha512.

Bugs Fixed in everRun Release 7.9.3.1

For information, see Bug Fixes in everRun Release 7.9.3.1.

Bugs Fixed in everRun Release 7.9.3.0

For information, see Bug Fixes in everRun Release 7.9.3.0.

Bugs Fixed in everRun Release 7.9.2.0

For information, see Bug Fixes in everRun Release 7.9.2.0.

Bugs Fixed in everRun Release 7.9.1.1

For information, see Bug Fixes in everRun Release 7.9.1.1.

Bugs Fixed in everRun Release 7.9.1.0

For information, see Bug Fixes in everRun Release 7.9.1.0.

Bugs Fixed in everRun Release 7.9.0.0

For information, see Bug Fixes in everRun Release 7.9.0.0.

CVE Fixes

For a list of the CVE fixes, see Fixed CVEs.

Important Considerations

Upgrading to Release 7.9.4.1

Upgrade to everRun Release 7.9.4.1 following the upgrade path for the release that is running on your system, as listed in the table below.

Release Upgrade Path

Releases

7.9.4.0
7.9.3.1
7.9.3.0
7.9.2.0
7.9.1.1,
7.9.1.0,
7.9.0.0,
7.8.0.0, 7.7.0.0, 7.6.1.0, 7.6.0.0, 7.5.1.1, 7.4.3.2

 Upgrade directly to Release 7.9.4.1 following instructions in Upgrading everRun Software Using an Upgrade Kit.
7.8.0.2 Upgrade to Release 7.9.0.0 first, and then upgrade to Release 7.9.4.1. For information on upgrading to Release 7.9.0.0, see the everRun Release 7.9.0.0 Release Notes and Help.
7.6.1.1 Upgrade to Release 7.8.0.0 first, and then upgrade to Release 7.9.4.1. For information on upgrading to Release 7.8.0.0, see the everRun Release 7.8.0.0 Release Notes and Help.

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.9.4.1. For information on upgrading to Release 7.6.1.0, see the everRun Release 7.6.1.0 Release Notes and Help.

Before upgrading from Release 7.3.4.0 to 7.6.1.0, to prevent the system from hanging during the upgrade, perform the steps in KB0014738.

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.9.4.1. To upgrade to Release 7.3.4.0, see the everRun Release 7.3.4.0 Release Notes and Help.

Before upgrading from Release 7.3.4.0 to 7.6.1.0, to prevent the system from hanging during the upgrade, perform the steps in KB0014738.

During Upgrade, Refresh Browser and Accept New Certificate

During an everRun software upgrade, the browser may display a stale status after the first node has been upgraded and become the new primary node. This incorrect browser display status can occur if the browser has a new certificate from Stratus that needs to be accepted. You should refresh the browser and, if prompted, accept the new certificate. After you have accepted the new certificate, the browser displays the correct status of the upgrade.

After Upgrade, Update root Password in Host Operating System to Improve Security

In everRun Release 7.9.4.0 or higher, the default encryption for the root user account in the host operating system has changed from md5 to sha512 encryption. After upgrading to Release 7.9.4.0, if you want to take advantage of the increased security, optionally log on as root in the host operating system of each physical machine and run the passwd command to update the password and enable the sha512 encryption.

If you newly install or reinstall everRun, the new encryption automatically takes effect. Any updates to the root password will also use the new encryption.

e-Alerts Require Mail Server With TLS v1.2 Encryption

Beginning with everRun 7.9.1.0, the system requires that the mail server you configure for e-Alerts and password resets supports the TLS v1.2 protocol. Previously, TLS 1.0 or 1.1 was allowed. If your mail server does not support TLS 1.2, then no outgoing emails will be sent, even if they are configured in the everRun Availability Console. For information about configuring and enabling an encrypted connection for the mail server on a everRun system, see Configuring the Mail Server.

SNMP Disabled by Default on everRun Systems

SNMP is disabled by default on everRun systems. Starting with everRun Release 7.9.0.0 or higher, the SNMP process is also stopped in the console operating system on each node. For security reasons, if you need to enable SNMP, you should disable SNMP v1 and v2, and enable only version 3 by using the SNMP Restricted configuration. For details, see Configuring SNMP Settings and Security Hardening, as well as KB0015445.

Tested Guest Operating Systems

For a list of the guest operating systems tested with the current release, see Tested Guest Operating Systems. For information on guest operating systems tested or supported in previous releases, go to http://everrundoc.stratus.com, select the appropriate release, and then search for the guest operating system.

Known Issues

Potential Data Corruption When Deleting a VM Snapshot

When deleting a snapshot, a SCSI miscompare can result in guest data corruption. Deleting the most recent snapshot might be safe; however, when coalescing a deleted snapshot image into an older image, some contents of a VM's data volume might be overwritten with zeroes, resulting in data corruption.

Caution: Before deleting any snapshot on everRun Version 7.5.0.5 or newer systems, see KB0015440 for more information.

Guest Performance Issues with Large Guest Volumes

Guest volumes that are 2TB or greater in size and that become fragmented over time may significantly reduce guest performance. When volumes of this size are created, Stratus recommends that qcow2 be selected as the disk image format. The format qcow2, instead of raw, reduces performance slightly, but prevents the significant performance reduction seen with raw guest volumes of this size. For information on creating guest volumes, see Creating a Volume in a Virtual Machine.

Removable Media and Migrating a PM or VM Using the P2V Client

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 to the everRun system, the error message Conversion failed appears. To prevent this issue, 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 everRun system, for more information on using virt-p2v.

"The VM name has failed to start" Alert While Running the P2V Client Is Normal

While using the P2V client to migrate a VM from an everRun or ztC Edge system, it is normal if the source system displays the alert "The VM name has failed to start" during the migration process, because although the source VM is powered on and running the P2V client, the guest operating system does not start.

Maximum Path Length When Importing a VM

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.

Cannot Import RHEL 8.x VMs

You cannot import a VM running RHEL 8.x (with BIOS boot firmware) from a VMware ESXi 6.7.0 server to a everRun system.

Restart VMs for vmgenid Support

After a system is upgraded from Release 7.6.1.0 or earlier to Release 7.8.0.0 or higher 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. If you are upgrading from Release 7.7.0.0, you do not need to restart such VMs if they had previously been restarted on the system running Release 7.7.0.0.

Creating VCD fails when console browser is Microsoft Edge

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).

Mapping of Japanese Keyboards 106 and 109 For Console in IE10, IE11, or Firefox May Be Incorrect

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.

Cannot Enable SNMP Requests Without Traps

If you create an SNMP request in the everRun Availability Console, you must also create a trap; otherwise, the everRun Availability Console displays the error "Problem encountered updating SNMP. Make sure your settings are correct. Error: Configure SNMP failed." As a workaround, when creating a new SNMP request, click Enable SNMP Requests and Enable SNMP traps, do not define a Version 3 user, keep the default of Restricted requests, and specify at least one trap recipient. Adding a Version 3 user or clicking Unrestricted during the initial configuration might cause the configuration to fail. After the initial configuration is complete, you can then modify it to specify any settings that you require.

VMs Running Windows 2016 with the Maximum vCPUs and Memory Will Not Reboot Cleanly

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. To avoid the problem, reduce the number of vCPUs or the amount of memory assigned to the VM.

Some Browsers Unable to Connect a VNC When Using https

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):

The VNC console appears.

Reboot Required when Changing Node IP Address or Netmask Network Settings

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.

Accessing Stratus Knowledge Base Articles

The Stratus Customer Service Portal provides a searchable Knowledge Base with technical articles about all Stratus products, including everRun. In some cases, the online Help directly references these Knowledge Base articles (for example, KBnnnnnnn). You can access the Stratus Customer Service Portal and its Knowledge Base by using your existing portal credentials, or by creating a new user account, as follows.

To access the Knowledge Base

  1. Log on to the Stratus Customer Service Portal at https://service.stratus.com.

    If needed, create a new account as follows:

    1. Click Register.

    2. Enter your contact information including your company email address and registration code, and then click Submit.

      Your company email address must include a domain name (for example, stratus.com) for a company that is a registered customer of Stratus. The portal sends an email to administrators of the company's account to approve the request.

    3. Upon approval, click the link in the email that you receive from Stratus.
    4. Enter a new password and finish configuring your account.

    If you need assistance creating an account, contact your authorized Stratus service representative.

  2. In the portal, do one of the following:

    • In the Search box, enter keywords or the KB article number (KBnnnnnnn) associated with the information you need, and then click the search button.
    • Click Knowledge, click the name of a product, and then browse available articles.

Getting Help

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://service.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.