4.5. Red Hat Virtualization 4.2 Batch Update 4 (ovirt-4.2.7)

The current release has a 'VDO Savings' field that displays the savings percentage for the Gluster Storage Domain, Volume, and Brick views.

The current release has a 'VDO Savings' field that displays the savings percentage for the Gluster Storage Domain, Volume, and Brick views.

In the current release, a filter for VNIC profiles, `clean-traffic-gateway`, supports private VLAN connections.

In the current release, a filter for VNIC profiles, `clean-traffic-gateway`, supports private VLAN connections.

The ovirt-log-collector now includes the RHV Log Collector Analyzer report. This analysis is generated by the rhv-log-collector-analyzer tool, which analyzes the RHV environment and detects anomalies in the system.

The ovirt-log-collector now includes the RHV Log Collector Analyzer report. This analysis is generated by the rhv-log-collector-analyzer tool, which analyzes the RHV environment and detects anomalies in the system.

Large snapshots can result in long pauses of a VM that can affect the accuracy of the System Time, upon which time stamps and other time related functions depend. Guest Time Synchronization enables synchronization of the VM’s System Time during the creation of snapshots when enabled. When this feature is enabled and the Guest Agent is running, the VDSM process on the Host attempts to synchronize the System Time of the VM with the Host’s System Time when snapshots are completed and the VM is un-paused. To turn on Guest Time Synchronization for snapshots, use the time_sync_snapshot_enable option. For synchronizing the VM’s System Time during abnormal scenarios that may cause the VM to pause, you can enable the time_sync_cont_enable option. By default, these features are disabled for backward compatibility.

Large snapshots can result in long pauses of a VM that can affect the accuracy of the System Time, upon which time stamps and other time related functions depend. Guest Time Synchronization enables synchronization of the VM’s System Time during the creation of snapshots when enabled. When this feature is enabled and the Guest Agent is running, the VDSM process on the Host attempts to synchronize the System Time of the VM with the Host’s System Time when snapshots are completed and the VM is un-paused. To turn on Guest Time Synchronization for snapshots, use the time_sync_snapshot_enable option. For synchronizing the VM’s System Time during abnormal scenarios that may cause the VM to pause, you can enable the time_sync_cont_enable option. By default, these features are disabled for backward compatibility.

Copying volumes to preallocated disks is slower than it can be, and does not make optimal use of available network resources. In this release, qemu-img uses out of order writing. As a result, write operations, such as importing, moving or copying large disks to preallocated storage, can be up to 6 times faster.

Copying volumes to preallocated disks is slower than it can be, and does not make optimal use of available network resources. In this release, qemu-img uses out of order writing. As a result, write operations, such as importing, moving or copying large disks to preallocated storage, can be up to 6 times faster.

In the current release, for compatibility versions 4.2 and 4.3, a warning in the Cluster screen indicates that the CPU types currently used are not supported in 4.3. The warning enables the user to change the cluster CPU type to a supported CPU type.

In the current release, for compatibility versions 4.2 and 4.3, a warning in the Cluster screen indicates that the CPU types currently used are not supported in 4.3. The warning enables the user to change the cluster CPU type to a supported CPU type.

When a VM is running, the disk size of the virtual machine should be no larger than was required during the initial allocation of disk space, unless you specify pre-allocation. Previously, when you set thin provisioning for importing a KVM-based VM into a Red Hat Virtualizaton environment, the disk size of the VM within the Red Hat Virtualization storage domain was inflated to the volume size or larger, even when the original KVM-based VM was much smaller.
KVM Sparseness is now supported so that when you import a virtual machine with thin provisioning enabled into a Red Hat Virtualization environment, the disk size of the original virtual machine image is preserved.

When a VM is running, the disk size of the virtual machine should be no larger than was required during the initial allocation of disk space, unless you specify pre-allocation. Previously, when you set thin provisioning for importing a KVM-based VM into a Red Hat Virtualizaton environment, the disk size of the VM within the Red Hat Virtualization storage domain was inflated to the volume size or larger, even when the original KVM-based VM was much smaller.
KVM Sparseness is now supported so that when you import a virtual machine with thin provisioning enabled into a Red Hat Virtualization environment, the disk size of the original virtual machine image is preserved.

In the current release, ovirt-ansible-hosted-engine-setup, ovirt-ansible-repositories, and ovirt-engine-setup role packages are included in the rhel-7-server-rhvh-4-rpms repository.

In the current release, ovirt-ansible-hosted-engine-setup, ovirt-ansible-repositories, and ovirt-engine-setup role packages are included in the rhel-7-server-rhvh-4-rpms repository.

QEMU Guest Agent packages for several Linux distributions have been added to ease offline installation of the guest agent.

QEMU Guest Agent packages for several Linux distributions have been added to ease offline installation of the guest agent.

The Red Hat Virtualization Manager 4.2 is a JBoss Application Server application that requires Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.2 to be installed on the host. To make sure that you install JBoss EAP 7.2, before you upgrade to Red Hat Virtualization Manager 4.2, enable the jb-eap-7-for-rhel-7-server-rpms.

For more information, see Enabling the Red Hat Virtualization Manager Repositories
 in the Red Hat Virtualization 4.2 Installation Guide at link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/installation_guide/#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[.

The Red Hat Virtualization Manager 4.2 is a JBoss Application Server application that requires Red Hat JBoss Enterprise Application Platform (JBoss EAP) 7.2 to be installed on the host. To make sure that you install JBoss EAP 7.2, before you upgrade to Red Hat Virtualization Manager 4.2, enable the jb-eap-7-for-rhel-7-server-rpms.

For more information, see Enabling the Red Hat Virtualization Manager Repositories
 in the Red Hat Virtualization 4.2 Installation Guide at link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/installation_guide/#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install[.

In this release the snapshot functionality introduced in 4.2.6 (ovirt-web-ui-1.4.3-1) has a problem where a user without any administrator role permissions cannot restore a virtual machine to a previously created snapshot. In such a case, the virtual machine enters into the "in preview" state, and only an administrator using the Administration Portal can resolve the virtual machine.

In this release the snapshot functionality introduced in 4.2.6 (ovirt-web-ui-1.4.3-1) has a problem where a user without any administrator role permissions cannot restore a virtual machine to a previously created snapshot. In such a case, the virtual machine enters into the "in preview" state, and only an administrator using the Administration Portal can resolve the virtual machine.

With this update, the CPU types Conroe, Penryn, Opteron G1, Opteron G2 and Opteron G3 have been deprecated. Red Hat Virtualization 4.3 will not support these CPU types.

With this update, the CPU types Conroe, Penryn, Opteron G1, Opteron G2 and Opteron G3 have been deprecated. Red Hat Virtualization 4.3 will not support these CPU types.