3.2. Release Notes

This change disables the ability to use VDSM in clusters from 3.0 to 3.3. Red Hat Enterprise Virtualization 3.6 drops support for cluster levels between 3.0 and 3.3 and Manager versions 3.3 and below. Support for Red Hat Enterprise Virtualization Manager 3.4 is still available as tech-preview.

This change disables the ability to use VDSM in clusters from 3.0 to 3.3. Red Hat Enterprise Virtualization 3.6 drops support for cluster levels between 3.0 and 3.3 and Manager versions 3.3 and below. Support for Red Hat Enterprise Virtualization Manager 3.4 is still available as tech-preview.

With this change, the glusterfs-cli package must be installed. Please note that in the VDSM spec file, there is no dependency to glusterfs-cli. This means that VDSM installation will succeed even if glustefs-cli is not installed, and that the glusterfs-cli package must be installed manually.

With this change, the glusterfs-cli package must be installed. Please note that in the VDSM spec file, there is no dependency to glusterfs-cli. This means that VDSM installation will succeed even if glustefs-cli is not installed, and that the glusterfs-cli package must be installed manually.

The HTTP components packages required by the Red Hat Enterprise Virtualization Manager Java SDK package have been changed to match release 6.3 of JBoss Enterprise Application Platform. The location of the JAR files provided by the new required packages is different to the previous location, so users with scripts that depend on these locations must update those scripts accordingly. For example, if you have a script such as the following:

  java -classpath \

  myapp.jar:\

  /usr/share/java/rhevm-sdk-java/rhevm-sdk-java.jar:\

  /usr/share/java/httpcore.jar:\

  /usr/share/java/httpclient.jar \

  my.app.Main

The script must be updated to the following:

  java -classpath \

  myapp.jar:\

  /usr/share/java/rhevm-sdk-java/rhevm-sdk-java.jar:\

  /usr/share/java/httpcomponents-eap6/httpcore.jar:\

  /usr/share/java/httpcomponents-eap6/httpclient.jar \

  my.app.Main

Note that the location of the httpcore.jar and httpclient.jar files has changed from /usr/share/java to /usr/share/java/httpcomponents-eap6.

The HTTP components packages required by the Red Hat Enterprise Virtualization Manager Java SDK package have been changed to match release 6.3 of JBoss Enterprise Application Platform. The location of the JAR files provided by the new required packages is different to the previous location, so users with scripts that depend on these locations must update those scripts accordingly. For example, if you have a script such as the following:

  java -classpath \

  myapp.jar:\

  /usr/share/java/rhevm-sdk-java/rhevm-sdk-java.jar:\

  /usr/share/java/httpcore.jar:\

  /usr/share/java/httpclient.jar \

  my.app.Main

The script must be updated to the following:

  java -classpath \

  myapp.jar:\

  /usr/share/java/rhevm-sdk-java/rhevm-sdk-java.jar:\

  /usr/share/java/httpcomponents-eap6/httpcore.jar:\

  /usr/share/java/httpcomponents-eap6/httpclient.jar \

  my.app.Main

Note that the location of the httpcore.jar and httpclient.jar files has changed from /usr/share/java to /usr/share/java/httpcomponents-eap6.

With this release, the downtime during a virtual machine migration is reported. This is the duration of the handover time needed to transfer the execution from the source host to the destination host (the last phase of migration). 

Note: as part of this enhancement a more strict clock synchronization is enforced between the Manager and hosts. Previously, there was an alert when the host was 5 minutes off the Manager time; now it is 100 ms. The reason is that for accurate downtime reporting the source and destination hosts must have the same clock time. This may cause a lot of new alerts in environments which are not configured properly. The configuration option (used in engine-config) has changed from 'HostTimeDriftInSec' to 'HostTimeDriftInMS'.

With this release, the downtime during a virtual machine migration is reported. This is the duration of the handover time needed to transfer the execution from the source host to the destination host (the last phase of migration). 

Note: as part of this enhancement a more strict clock synchronization is enforced between the Manager and hosts. Previously, there was an alert when the host was 5 minutes off the Manager time; now it is 100 ms. The reason is that for accurate downtime reporting the source and destination hosts must have the same clock time. This may cause a lot of new alerts in environments which are not configured properly. The configuration option (used in engine-config) has changed from 'HostTimeDriftInSec' to 'HostTimeDriftInMS'.

Previously, the field "vm_disk_actual_size_mb", in "dwh_vm_disks_history_view", was the virtual machine disk size for the current snapshot of the virtual machine. It was decided that this information is irrelevant for collecting to the ovirt-engine-history database and what should be collected is the total disk size that the virtual machine is using, including all snapshots. From Red Hat Enterprise Virtualization 3.6 this field will show the Total virtual machine disk size. Previous collected data will be kept even though it is inaccurate.

Previously, the field "vm_disk_actual_size_mb", in "dwh_vm_disks_history_view", was the virtual machine disk size for the current snapshot of the virtual machine. It was decided that this information is irrelevant for collecting to the ovirt-engine-history database and what should be collected is the total disk size that the virtual machine is using, including all snapshots. From Red Hat Enterprise Virtualization 3.6 this field will show the Total virtual machine disk size. Previous collected data will be kept even though it is inaccurate.

Previously, Red Hat Enterprise Virtualization provided three ways to access a virtual machine graphical console from web portals: using an ActiveX/Firefox SPICE plugin, .vv file MIME type association to remote-viewer (called Native in the user interface), and web-based clients (technology preview). In this version of Red Hat Enterprise Virtualization, the browser-specific plugins have been deprecated in favor of more universal generic .vv file association, which allows for more flexibility (for example, using custom VNC viewers to view the console) and does not suffer from frequent browser changes and instabilities.

As a result, the default SPICE console mode has changed in new installations, which now default to the Native setting in the user interface. For existing installations that are upgraded this value is not changed, but can be configured by the global ClientModeSpiceDefault parameter with the engine-config tool.

Previously, Red Hat Enterprise Virtualization provided three ways to access a virtual machine graphical console from web portals: using an ActiveX/Firefox SPICE plugin, .vv file MIME type association to remote-viewer (called Native in the user interface), and web-based clients (technology preview). In this version of Red Hat Enterprise Virtualization, the browser-specific plugins have been deprecated in favor of more universal generic .vv file association, which allows for more flexibility (for example, using custom VNC viewers to view the console) and does not suffer from frequent browser changes and instabilities.

As a result, the default SPICE console mode has changed in new installations, which now default to the Native setting in the user interface. For existing installations that are upgraded this value is not changed, but can be configured by the global ClientModeSpiceDefault parameter with the engine-config tool.

QEMU capabilities for auto-convergence and/or Xor Binary Zero Run-Length-Encoding (XBZRLE) can be used to reduce virtual machine downtime and improve convergence during migration. This is supported by hierarchical configuration in 3 levels: global (engine-config), cluster, and virtual machine.

QEMU capabilities for auto-convergence and/or Xor Binary Zero Run-Length-Encoding (XBZRLE) can be used to reduce virtual machine downtime and improve convergence during migration. This is supported by hierarchical configuration in 3 levels: global (engine-config), cluster, and virtual machine.

To prevent connection failure with local USB devices on a Windows 7 client machine, update the Windows machine with Microsoft Security Update KB3033929 before installing the USB Development Kit Driver (spice-usbdk-win). Failure to apply this update before installing the spice-usbdk-win driver otherwise results in USB connection loss and an error reporting an unsigned driver.

See https://technet.microsoft.com/en-us/library/security/3033929 for more information on this security update.

To prevent connection failure with local USB devices on a Windows 7 client machine, update the Windows machine with Microsoft Security Update KB3033929 before installing the USB Development Kit Driver (spice-usbdk-win). Failure to apply this update before installing the spice-usbdk-win driver otherwise results in USB connection loss and an error reporting an unsigned driver.

See https://technet.microsoft.com/en-us/library/security/3033929 for more information on this security update.

With this update Red Hat Access plugin for Red Hat Enterprise Virtualization has been deprecated and has been converted into a page pointing to the product documentation. The features that were previously delivered by the plugin, such as Knowledgebase access and support case engagement, will continue to be available through the Red Hat Customer Portal. The log viewer has been removed entirely. Required data and logs can be collected by using the Log collector tool. For more information see https://access.redhat.com/solutions/2137681

With this update Red Hat Access plugin for Red Hat Enterprise Virtualization has been deprecated and has been converted into a page pointing to the product documentation. The features that were previously delivered by the plugin, such as Knowledgebase access and support case engagement, will continue to be available through the Red Hat Customer Portal. The log viewer has been removed entirely. Required data and logs can be collected by using the Log collector tool. For more information see https://access.redhat.com/solutions/2137681