Chapter 3. Release Information

It is now possible to hot plug and unplug SR-IOV virtual functions to running virtual machines.

It is now possible to hot plug and unplug SR-IOV virtual functions to running virtual machines.

With this release, a single sign on module has been added that authenticates the user once, and allows access to both the Administration Portal and User Portal. Signing off from one portal closes the session on SSO and the user is logged out of all portals.

With this release, a single sign on module has been added that authenticates the user once, and allows access to both the Administration Portal and User Portal. Signing off from one portal closes the session on SSO and the user is logged out of all portals.

With this release, the Add Permissions dialog now has a new radio button called "My Groups", which lists the currently logged in user's groups. The user can use this option to grant permissions to other users in the same group.

With this release, the Add Permissions dialog now has a new radio button called "My Groups", which lists the currently logged in user's groups. The user can use this option to grant permissions to other users in the same group.

You can now replace bricks for replicate type Gluster volumes and perform maintenance tasks from the Administration Portal.

You can now replace bricks for replicate type Gluster volumes and perform maintenance tasks from the Administration Portal.

With this release, the Administration Portal and User Portal are now translated into Italian.

With this release, the Administration Portal and User Portal are now translated into Italian.

With this enhancement, the Manager monitors any unsynced entries in all Gluster replicated volumes. Unsynced entries are shown in the bricks subtab with the expected time to heal the entries. There will be a warning icon in the volume and the bricks status column when there is an unsynced entry.

With this enhancement, the Manager monitors any unsynced entries in all Gluster replicated volumes. Unsynced entries are shown in the bricks subtab with the expected time to heal the entries. There will be a warning icon in the volume and the bricks status column when there is an unsynced entry.

With this update, fence agents can now be specified using an IPv6 address. The whole fencing flow is now functional on IPv6 networks.

With this update, fence agents can now be specified using an IPv6 address. The whole fencing flow is now functional on IPv6 networks.

With this update, the engine-backup script no longer depends on ovirt-engine. This allows the backup of machines running ovirt services but not running ovirt-engine.

With this update, the engine-backup script no longer depends on ovirt-engine. This allows the backup of machines running ovirt services but not running ovirt-engine.

Data tables in the Administration portal support the 'Column Control' context menu which is triggered by right-clicking the table header area.

The context menu enables users to control the visibility and position of individual columns. This is useful for users who want to re-order columns.

Data tables in the Administration portal support the 'Column Control' context menu which is triggered by right-clicking the table header area.

The context menu enables users to control the visibility and position of individual columns. This is useful for users who want to re-order columns.

In 4.0, the "guest_info" section has been removed from the REST API VM resource as it is no longer required.

In 4.0, the "guest_info" section has been removed from the REST API VM resource as it is no longer required.

Previously, there was no authorization information for users in the session management table, so you could not distinguish between two users with the same name from two different profiles (domains). With this release, the Active User Sessions tab now shows the authorization provider name for each user.

Previously, there was no authorization information for users in the session management table, so you could not distinguish between two users with the same name from two different profiles (domains). With this release, the Active User Sessions tab now shows the authorization provider name for each user.

This release improves the user experience of guest OS installations. When using an installation CD and, after finishing with the OS installation, the CD is not used anymore and should be ejected, the suggested way is to use the Run Once dialog and attach the installation CD, then use "Start in paused mode" and/or "Enable boot menu" to select the boot media (CD) once. For this purpose the layout was changed so that these options are now right next to the Attach CD drop-down list.

This release improves the user experience of guest OS installations. When using an installation CD and, after finishing with the OS installation, the CD is not used anymore and should be ejected, the suggested way is to use the Run Once dialog and attach the installation CD, then use "Start in paused mode" and/or "Enable boot menu" to select the boot media (CD) once. For this purpose the layout was changed so that these options are now right next to the Attach CD drop-down list.

Previously, Red Hat Virtualization only allowed hostdev passthrough of USB and PCI devices. To assign storage cards directly to a virtual machine users had to assign the whole adapter as PCI device. The problem with this approach is that PCI passthrough has specific hardware requirements.

This feature allows administrators to passthrough a LUN directly to a virtual machine, allowing for full set of SG commands. This means tapes, changers, and anything speaking SCSI protocol can be assigned directly without specific hardware requirements with the exception of assigned device itself.

Previously, Red Hat Virtualization only allowed hostdev passthrough of USB and PCI devices. To assign storage cards directly to a virtual machine users had to assign the whole adapter as PCI device. The problem with this approach is that PCI passthrough has specific hardware requirements.

This feature allows administrators to passthrough a LUN directly to a virtual machine, allowing for full set of SG commands. This means tapes, changers, and anything speaking SCSI protocol can be assigned directly without specific hardware requirements with the exception of assigned device itself.

With this release, the Administration Portal reports the ID, image, executed command, state, and name of Docker containers running on virtual machines.

With this release, the Administration Portal reports the ID, image, executed command, state, and name of Docker containers running on virtual machines.

With this update, the upgrade of the ovirt-windows-guest-tools has been simplified.

With this update, the upgrade of the ovirt-windows-guest-tools has been simplified.

When one or more bricks are down on a started volume, you can now force start the brick(s) through the Administration Portal.

When one or more bricks are down on a started volume, you can now force start the brick(s) through the Administration Portal.

This update supports the self-hosted engine upgrade path from Red Hat Enterprise Virtualization 3.4 to Red Hat Virtualization 4.0 by migrating filebase metadata and lockspace.

This update supports the self-hosted engine upgrade path from Red Hat Enterprise Virtualization 3.4 to Red Hat Virtualization 4.0 by migrating filebase metadata and lockspace.

With this update, a new Source IP column was added to the Active Users Sessions tab. This allows the user to identify which host a user is using to connect to the Red Hat Virtualization Manager.

With this update, a new Source IP column was added to the Active Users Sessions tab. This allows the user to identify which host a user is using to connect to the Red Hat Virtualization Manager.

This release introduces Red Hat Virtualization Host, a major upgrade of RHEV-H. RHVH is now based on the Red Hat Enterprise Linux installer and Cockpit. This provides better hardware support, easier usage, modernization, and better configuration management integration.

This release introduces Red Hat Virtualization Host, a major upgrade of RHEV-H. RHVH is now based on the Red Hat Enterprise Linux installer and Cockpit. This provides better hardware support, easier usage, modernization, and better configuration management integration.

Previously, if a user password expired, it needed to be reset on the LDAP server. Now there is a new capability added to the LDAP and JDBC extensions to enable changing passwords from the front end in a new change password screen.

Previously, if a user password expired, it needed to be reset on the LDAP server. Now there is a new capability added to the LDAP and JDBC extensions to enable changing passwords from the front end in a new change password screen.

With this release, errors raised during user authentication are transferred to the login page and displayed to the end user.

With this release, errors raised during user authentication are transferred to the login page and displayed to the end user.

Previously, an auto-generated snapshot was created during live storage migration and had to be manually removed afterwards. With this release, the auto-generated snapshot is automatically deleted after live storage migration.

Previously, an auto-generated snapshot was created during live storage migration and had to be manually removed afterwards. With this release, the auto-generated snapshot is automatically deleted after live storage migration.

With the update, the order in which MAC addresses are obtained from the MAC address pool has been altered. Previously, the leftmost available MAC address was returned from the MAC address pool when requested. This caused issues in certain environments when MAC addresses returned to MAC address pool were immediately queried from the MAC address pool by another process and confused some devices on the network as a device now has the MAC address that had been recently used by a different device. Now, the MAC address pool remembers that last returned MAC address for each address in its MAC address range and will return the first available MAC address following the most recently returned. If there is no further addresses left in the range the search starts from the beginning of the range. If there are multiple MAC address ranges with available MAC addresses they take turns in serving incoming requests in the same way available MAC addresses are selected.

With the update, the order in which MAC addresses are obtained from the MAC address pool has been altered. Previously, the leftmost available MAC address was returned from the MAC address pool when requested. This caused issues in certain environments when MAC addresses returned to MAC address pool were immediately queried from the MAC address pool by another process and confused some devices on the network as a device now has the MAC address that had been recently used by a different device. Now, the MAC address pool remembers that last returned MAC address for each address in its MAC address range and will return the first available MAC address following the most recently returned. If there is no further addresses left in the range the search starts from the beginning of the range. If there are multiple MAC address ranges with available MAC addresses they take turns in serving incoming requests in the same way available MAC addresses are selected.

Previously, Red Hat Virtualization only allowed hostdev passthrough of USB and PCI devices. With this update, administrators can connect FibreChannel tape devices to guest systems using hostdev passthrough.

Previously, Red Hat Virtualization only allowed hostdev passthrough of USB and PCI devices. With this update, administrators can connect FibreChannel tape devices to guest systems using hostdev passthrough.

With this update, a regular file system has been added for /etc on Red Hat Virtualization Hosts. This allows better alignment with Red Hat Enterprise Linux hosts and means the same set of tools can be used for both Red Hat Virtualization Hosts and Red Hat Enterprise Linux hosts.

With this update, a regular file system has been added for /etc on Red Hat Virtualization Hosts. This allows better alignment with Red Hat Enterprise Linux hosts and means the same set of tools can be used for both Red Hat Virtualization Hosts and Red Hat Enterprise Linux hosts.

With this release, users can use engine-config to set whether console windows open in full screen by default. The value can be set independently for the Administration Portal, Basic User Portal, and Extended User Portal. Consoles retrieved via REST share settings with the Administration Portal. The default can be set via engine-config by setting FullScreenWebadminDefault, FullScreenUserportalBasicDefault, and FullScreenUserportalExtendedDefault options.

With this release, users can use engine-config to set whether console windows open in full screen by default. The value can be set independently for the Administration Portal, Basic User Portal, and Extended User Portal. Consoles retrieved via REST share settings with the Administration Portal. The default can be set via engine-config by setting FullScreenWebadminDefault, FullScreenUserportalBasicDefault, and FullScreenUserportalExtendedDefault options.

With this update, the network filter has been enhanced to allow the administrator the ability to manage the network packet traffic to and from virtual machines. The required filter can now be specified on the vNIC profile via the web interface or the REST API. If no filter is specified and the 'EnableMACAntiSpoofingFilterRules' is enabled via engine-config tool the vNIC profile will use 'Enable MAC Anti Spoofing' as the default filter

With this update, the network filter has been enhanced to allow the administrator the ability to manage the network packet traffic to and from virtual machines. The required filter can now be specified on the vNIC profile via the web interface or the REST API. If no filter is specified and the 'EnableMACAntiSpoofingFilterRules' is enabled via engine-config tool the vNIC profile will use 'Enable MAC Anti Spoofing' as the default filter

When a cluster is set to hyper-converged mode (with both Virt and Gluster services enabled), for Gluster storage, only replica 3 volumes are supported.

When a cluster is set to hyper-converged mode (with both Virt and Gluster services enabled), for Gluster storage, only replica 3 volumes are supported.

The SAM user format of profile\user is no longer supported.

The SAM user format of profile\user is no longer supported.

Virtual machines from a stateful virtual machine pool are now always started in stateful mode. The state of the virtual machine is preserved even when the virtual machine is passed to a different user.

Virtual machines from a stateful virtual machine pool are now always started in stateful mode. The state of the virtual machine is preserved even when the virtual machine is passed to a different user.

This update ensures that only supported volume types are displayed when managing volumes in the Manager.

This update ensures that only supported volume types are displayed when managing volumes in the Manager.

With this update, a Cluster Compatibility Version field has been added. This field displays the cluster version supported by the host. This field was added to the Hosts tab in the Details pane under the General tab in the Info sub-tab.

With this update, a Cluster Compatibility Version field has been added. This field displays the cluster version supported by the host. This field was added to the Hosts tab in the Details pane under the General tab in the Info sub-tab.

To provide a way to configure gssapi using ticket cache for authz pool, a new security domain called 'oVirtKerbAAA' was added to JBoss configuration, which can be customized by using the following variables:

AAA_KRB5_CONF_FILE=path_to_krb5_conf
Specify the custom krb5.conf file. The default is /etc/ovirt-engine/krb5.conf
Java supports only one krb5 configuration, if the user changes this property, then manage-domains will stop working because its configuration is managed in /etc/ovirt-engine/krb5.conf.

AAA_JAAS_USE_TICKET_CACHE=true/false
Enable or disable using the ticket cache file for authentication.

AAA_JAAS_TICKET_CACHE_FILE=path_to_ticket_cache
Specify the custom ticket cache file. The default is /tmp/krb5cc_${UID}, where UID is the ID of the ovirt user.

AAA_JAAS_USE_KEYTAB=false/true
Enable or disable using the keytab file for authentication.

AAA_JAAS_KEYTAB_FILE=path_to_keytab_file
Specify the custom keytab file. The default is ${OVIRT_HOME}/krb5.keytab where OVIRT_HOME is home directory of ovirt user.

To use one of the features, the user has to create a new configuration file and specify the correct values for those variables, for example: /etc/ovirt-engine/engine.conf.d/99-jaas.conf.

To use the new security domain configuration from aaa-ldap, the user has to specify the correct JAASClientName (default is oVirtKerb). Therefore, to use this new configuration for authz pool, the user has to add following line to aaa-ldap authz configuration:

pool.authz.auth.gssapi.jAASClientName = oVirtKerbAAA

To use it for both authn and authz, the user has to add the following line to aaa-ldap configuration:

pool.default.auth.gssapi.jAASClientName = oVirtKerbAAA

To provide a way to configure gssapi using ticket cache for authz pool, a new security domain called 'oVirtKerbAAA' was added to JBoss configuration, which can be customized by using the following variables:

AAA_KRB5_CONF_FILE=path_to_krb5_conf
Specify the custom krb5.conf file. The default is /etc/ovirt-engine/krb5.conf
Java supports only one krb5 configuration, if the user changes this property, then manage-domains will stop working because its configuration is managed in /etc/ovirt-engine/krb5.conf.

AAA_JAAS_USE_TICKET_CACHE=true/false
Enable or disable using the ticket cache file for authentication.

AAA_JAAS_TICKET_CACHE_FILE=path_to_ticket_cache
Specify the custom ticket cache file. The default is /tmp/krb5cc_${UID}, where UID is the ID of the ovirt user.

AAA_JAAS_USE_KEYTAB=false/true
Enable or disable using the keytab file for authentication.

AAA_JAAS_KEYTAB_FILE=path_to_keytab_file
Specify the custom keytab file. The default is ${OVIRT_HOME}/krb5.keytab where OVIRT_HOME is home directory of ovirt user.

To use one of the features, the user has to create a new configuration file and specify the correct values for those variables, for example: /etc/ovirt-engine/engine.conf.d/99-jaas.conf.

To use the new security domain configuration from aaa-ldap, the user has to specify the correct JAASClientName (default is oVirtKerb). Therefore, to use this new configuration for authz pool, the user has to add following line to aaa-ldap authz configuration:

pool.authz.auth.gssapi.jAASClientName = oVirtKerbAAA

To use it for both authn and authz, the user has to add the following line to aaa-ldap configuration:

pool.default.auth.gssapi.jAASClientName = oVirtKerbAAA

This release adds the ability to register unregistered floating disks through the GUI. Previously, because floating disks are not part of any virtual machine or template, the user could only register floating disks from the REST API, not from the GUI. Now there is a subtab in the GUI called "Import Disk" which allows the user to register a floating disk into the setup. Storage domains also support a functionality called "Scan Disks", which scans the storage domain for unregistered floating disks that are not reflected in the setup. This can be helpful for managing disks from external storage domains.

This release adds the ability to register unregistered floating disks through the GUI. Previously, because floating disks are not part of any virtual machine or template, the user could only register floating disks from the REST API, not from the GUI. Now there is a subtab in the GUI called "Import Disk" which allows the user to register a floating disk into the setup. Storage domains also support a functionality called "Scan Disks", which scans the storage domain for unregistered floating disks that are not reflected in the setup. This can be helpful for managing disks from external storage domains.

With this update, the ability to import Red Hat Enterprise Linux KVM guest images managed by libvirt directly to Red Hat Virtualization has been added. To import KVM virtual machines from libvirt the libvirt uri, username and password are required. The libvirt uri when using QEMU and TCP is qemu+tcp://[USER]@[HOST]/system. QEMU and ssh is also supported but requires that the VDSM user is enabled and public/private keys must be generated for the VDSM user and exhanged with the libvirt server.

With this update, the ability to import Red Hat Enterprise Linux KVM guest images managed by libvirt directly to Red Hat Virtualization has been added. To import KVM virtual machines from libvirt the libvirt uri, username and password are required. The libvirt uri when using QEMU and TCP is qemu+tcp://[USER]@[HOST]/system. QEMU and ssh is also supported but requires that the VDSM user is enabled and public/private keys must be generated for the VDSM user and exhanged with the libvirt server.

This enhancement provides support for guest agents on Red Hat Enterprise Linux Atomic Host virtual machines.

This enhancement provides support for guest agents on Red Hat Enterprise Linux Atomic Host virtual machines.

Previously, it was only possible to remove a base template if there was no template sub-version based upon it. This update allows the removal of a base template, even if there are template sub-versions based upon it. The sub-version with lowest version number becomes the next base template for all other sub-versions. Version numbers are not affected meaning that the version number of the base template no longer needs to be 1.

Previously, it was only possible to remove a base template if there was no template sub-version based upon it. This update allows the removal of a base template, even if there are template sub-versions based upon it. The sub-version with lowest version number becomes the next base template for all other sub-versions. Version numbers are not affected meaning that the version number of the base template no longer needs to be 1.

With this update, a new configuration variable, ovirt.engine.aaa.authn.default.profile, has been added to the authn configuration file. Setting this variable ensures that the profile drop-down menu on the login page defaults to the selected profile. To configure this feature, add ovirt.engine.aaa.authn.default.profile to the authn configuration file for a selected profile and set the value to true then restart the ovirt-engine service. If the ovirt.engine.aaa.authn.default.profile variable is not defined in the authn configuration file the drop-down menu defaults to internal.

With this update, a new configuration variable, ovirt.engine.aaa.authn.default.profile, has been added to the authn configuration file. Setting this variable ensures that the profile drop-down menu on the login page defaults to the selected profile. To configure this feature, add ovirt.engine.aaa.authn.default.profile to the authn configuration file for a selected profile and set the value to true then restart the ovirt-engine service. If the ovirt.engine.aaa.authn.default.profile variable is not defined in the authn configuration file the drop-down menu defaults to internal.

With this update, Red Hat Virtualization can now handle FCoE block storage. Depending on the FCoE card on the hosts, special configuration may be needed as described in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/fcoe-config.html 

To configure FCoE block storage, run engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*$' on the Red Hat Virtualization Manager then restart the Manager. Ensure that the required host has vdsm-hook-fcoe installed then enable FCoE on a NIC. 

To enable FCoE on a NIC, attach a network then set the FCoE network custom property to enable=yes[,dcb=yes][,auto_vlan=yes].

With this update, Red Hat Virtualization can now handle FCoE block storage. Depending on the FCoE card on the hosts, special configuration may be needed as described in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/fcoe-config.html 

To configure FCoE block storage, run engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*$' on the Red Hat Virtualization Manager then restart the Manager. Ensure that the required host has vdsm-hook-fcoe installed then enable FCoE on a NIC. 

To enable FCoE on a NIC, attach a network then set the FCoE network custom property to enable=yes[,dcb=yes][,auto_vlan=yes].

Previously, an auto-generated snapshot was created during live storage migration and had to be manually removed afterwards. With this release, the auto-generated snapshot is automatically deleted after live storage migration.

Previously, an auto-generated snapshot was created during live storage migration and had to be manually removed afterwards. With this release, the auto-generated snapshot is automatically deleted after live storage migration.

This update ensures that the auto-generated snapshot that is created during live storage migration (LSM) is automatically deleted if LSM fails.

This update ensures that the auto-generated snapshot that is created during live storage migration (LSM) is automatically deleted if LSM fails.

With this enhancement, the Disk Tab in the Administration Portal now displays the template version next to the template name. It is now easier for users to check the template version the disk belongs to.

With this enhancement, the Disk Tab in the Administration Portal now displays the template version next to the template name. It is now easier for users to check the template version the disk belongs to.

Cloud-Init and Sysprep settings can now be modified using REST APIs.

Cloud-Init and Sysprep settings can now be modified using REST APIs.

You can now use the REST API to assign affinity labels to hosts and virtual machines. A virtual machine can be scheduled on a host as long as the host has all the affinity labels the virtual machine has. It is also supported if the host has additional affinity labels that the virtual machine does not have.

You can now use the REST API to assign affinity labels to hosts and virtual machines. A virtual machine can be scheduled on a host as long as the host has all the affinity labels the virtual machine has. It is also supported if the host has additional affinity labels that the virtual machine does not have.

With this enhancement, support for SNMP v3 traps was added. RHV-M is now able to provide SNMP v2c and v3 traps. New SNMP related options which can be set along with the default values can be found at: /usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf.

With this enhancement, support for SNMP v3 traps was added. RHV-M is now able to provide SNMP v2c and v3 traps. New SNMP related options which can be set along with the default values can be found at: /usr/share/ovirt-engine/services/ovirt-engine-notifier/ovirt-engine-notifier.conf.

Previously, when the number of logical volumes in a storage domain reached the recommended maximum it was logged and a message was shown in the events pane. Now, a user can register to the event notifier and receive an email when the number of logical volumes in a storage domain reached the recommended maximum.

Previously, when the number of logical volumes in a storage domain reached the recommended maximum it was logged and a message was shown in the events pane. Now, a user can register to the event notifier and receive an email when the number of logical volumes in a storage domain reached the recommended maximum.

Previously, in the User Portal, all roles were displayed. With this enhancement, only the roles that can be assigned are listed to avoid confusion.

Previously, in the User Portal, all roles were displayed. With this enhancement, only the roles that can be assigned are listed to avoid confusion.

When creating a new virtual machine, if you enable Cloud-Init or Sysprep, the host name is automatically set to the virtual machine name provided. Previously, a user had to manually set the host name. Changing or deleting the host name is still allowed if required.

When creating a new virtual machine, if you enable Cloud-Init or Sysprep, the host name is automatically set to the virtual machine name provided. Previously, a user had to manually set the host name. Changing or deleting the host name is still allowed if required.

With this update, the ability to trigger activity inside of a virtual guest during live migration has been added. Examples of events that can be used as a trigger are before migration, after migration, before hibernation, or after hibernation. The hooks configuration base directory is located in the /etc/ovirt-guest-agent/hooks.d directory on Linux systems and in Red Hat Virtualization Agent directory on Windows systems. Each event has a corresponding subdirectory and all files or symlinks in that directory will be executed. The executing user on Linux systems is 'ovirtagent'. If the script needs root permissions, the elevation must be executed by the creator of the hook script. The executing user on Windows systems is the System Service user.

With this update, the ability to trigger activity inside of a virtual guest during live migration has been added. Examples of events that can be used as a trigger are before migration, after migration, before hibernation, or after hibernation. The hooks configuration base directory is located in the /etc/ovirt-guest-agent/hooks.d directory on Linux systems and in Red Hat Virtualization Agent directory on Windows systems. Each event has a corresponding subdirectory and all files or symlinks in that directory will be executed. The executing user on Linux systems is 'ovirtagent'. If the script needs root permissions, the elevation must be executed by the creator of the hook script. The executing user on Windows systems is the System Service user.

A visual indicator has been added to the Hosts tab of the Administration Portal to identify the host running the self-hosted engine Manager virtual machine in self-hosted engine installations.

A visual indicator has been added to the Hosts tab of the Administration Portal to identify the host running the self-hosted engine Manager virtual machine in self-hosted engine installations.

This update enables you to configure multiple NICs on a Red Hat Virtualization host to enable you to reach multiple networks at the same time.

This update enables you to configure multiple NICs on a Red Hat Virtualization host to enable you to reach multiple networks at the same time.

This release enforces a minimum version of remote-viewer: 2.0-128 for Windows, 2.0-6 for RHEL 7, and 2.0-14 for RHEL 6. If the remote-viewer version is older than the enforced one, remote-viewer will show a link to documentation describing how to update.

This release enforces a minimum version of remote-viewer: 2.0-128 for Windows, 2.0-6 for RHEL 7, and 2.0-14 for RHEL 6. If the remote-viewer version is older than the enforced one, remote-viewer will show a link to documentation describing how to update.

Previously, to use external network providers, only OpenStack Networking (Neutron) is supported. With this update, any external network provider that implements the OpenStack Neutron REST API can be added to Red Hat Virtualization. The external network provider does not use the Neutron agent as the virtual interface driver implementation on the host. Instead, the virtual interface driver should be provided by the implementer of the external network provider. A read-only feature is also available to prevent users from modifying the external network provider from the Manager.

Previously, to use external network providers, only OpenStack Networking (Neutron) is supported. With this update, any external network provider that implements the OpenStack Neutron REST API can be added to Red Hat Virtualization. The external network provider does not use the Neutron agent as the virtual interface driver implementation on the host. Instead, the virtual interface driver should be provided by the implementer of the external network provider. A read-only feature is also available to prevent users from modifying the external network provider from the Manager.

For a bond in mode 4 (link aggregation mode), all slaves must be configured properly on the switch side. If none of them are configured on the switch, the host side kernel reports the ad_partner_mac as 00:00:00:00:00:00.

This update retrieves the partner mac address and warns the Manager user if the bond is configured incorrectly. No warning is given if only one of the slaves are up and running.

For a bond in mode 4 (link aggregation mode), all slaves must be configured properly on the switch side. If none of them are configured on the switch, the host side kernel reports the ad_partner_mac as 00:00:00:00:00:00.

This update retrieves the partner mac address and warns the Manager user if the bond is configured incorrectly. No warning is given if only one of the slaves are up and running.

When creating a virtual machine from a template, the user is able to choose the format of the disks: either RAW or QCOW2. The Allocation Policy section is now hidden. If the Template Provisioning is Thin, the format of the disks will be marked as QCOW2 and the user won't be able to change it. If the Template Provisioning is Clone, the user will be able to select either QCOW2 or RAW.

When creating a virtual machine from a template, the user is able to choose the format of the disks: either RAW or QCOW2. The Allocation Policy section is now hidden. If the Template Provisioning is Thin, the format of the disks will be marked as QCOW2 and the user won't be able to change it. If the Template Provisioning is Clone, the user will be able to select either QCOW2 or RAW.

Previously, when the number of logical volumes in a storage domain reached the recommended maximum it was logged and a message was shown in the events pane. Now, a user can register to the event notifier and receive an email when the number of logical volumes in a storage domain reached the recommended maximum.

Previously, when the number of logical volumes in a storage domain reached the recommended maximum it was logged and a message was shown in the events pane. Now, a user can register to the event notifier and receive an email when the number of logical volumes in a storage domain reached the recommended maximum.

It is now possible to specify a custom name for the template when importing a Glance disk through the Administration Portal.

It is now possible to specify a custom name for the template when importing a Glance disk through the Administration Portal.

With this release, the "Edit" button under the Storage tab has been renamed "Manage Domain" to comply to the product's standard.

With this release, the "Edit" button under the Storage tab has been renamed "Manage Domain" to comply to the product's standard.

Previously, any modification to the kernel command line had to be executed and maintained by administrators. This process was more complex in the Red Hat Enterprise Virtualization Hypervisor as the file system had to be manually remounted as writable to make the required changes. 

Now, a new UI selection has been added when adding or editing a host that allows for kernel line modifications directly from the web administration portal. These changes are then maintained by Red Hat Virtualization. Supported modifications are displayed as checkboxes but more complex modifications are also allowed as free text entry.

Previously, any modification to the kernel command line had to be executed and maintained by administrators. This process was more complex in the Red Hat Enterprise Virtualization Hypervisor as the file system had to be manually remounted as writable to make the required changes. 

Now, a new UI selection has been added when adding or editing a host that allows for kernel line modifications directly from the web administration portal. These changes are then maintained by Red Hat Virtualization. Supported modifications are displayed as checkboxes but more complex modifications are also allowed as free text entry.

With this update, support for Red Hat Enterprise Linux Atomic Host as a configurable system has been added to the Red Hat Virtualization Manager.

With this update, support for Red Hat Enterprise Linux Atomic Host as a configurable system has been added to the Red Hat Virtualization Manager.

Previously, if ovirt-log-collector was called without filters in large scale environments hours of logs were collected and the output was large. Now, ovirt-log-collector shows a warning if called without any filters.

Previously, if ovirt-log-collector was called without filters in large scale environments hours of logs were collected and the output was large. Now, ovirt-log-collector shows a warning if called without any filters.

With this update, support has been added for skipping the LUN status check in the REST API as checking the status of the LUN is a heavyweight operation and this data is not always required. To enable this feature set report_status to false. The default for report_status is true to allow for backward compatibility. The report_status parameter is available when getting a list of storage devices visible to a host or when getting a specific storage device via a host, GET /hosts/{host:id}/storage or GET /hosts/{host:id}/storage/{storage:id}. For example: 

GET /hosts/{host:id}/storage/{storage:id};report_status=false

<host_storage id="360014051136c20574f743bdbd28177fd">
  <logical_units>
    <logical_unit id="360014051136c20574f743bdbd28177fd">
      <lun_mapping>0</lun_mapping>
      <paths>1</paths>
      <product_id>lun0</product_id>
      <serial>SLIO-ORG_lun0_1136c205-74f7-43bd6993</serial>
      <size>10737418240</size>
      <vendor_id>LIO-ORG</vendor_id>
      <volume_group_id>O9Du7I-RahN</volume_group_id>
    </logical_unit>
  </logical_units>
  <type>iscsi</type>
  <host id="8bb5ade5-e988-4000-8b93-dbfc6717fe50"/>
</host_storage>

With this update, support has been added for skipping the LUN status check in the REST API as checking the status of the LUN is a heavyweight operation and this data is not always required. To enable this feature set report_status to false. The default for report_status is true to allow for backward compatibility. The report_status parameter is available when getting a list of storage devices visible to a host or when getting a specific storage device via a host, GET /hosts/{host:id}/storage or GET /hosts/{host:id}/storage/{storage:id}. For example: 

GET /hosts/{host:id}/storage/{storage:id};report_status=false

<host_storage id="360014051136c20574f743bdbd28177fd">
  <logical_units>
    <logical_unit id="360014051136c20574f743bdbd28177fd">
      <lun_mapping>0</lun_mapping>
      <paths>1</paths>
      <product_id>lun0</product_id>
      <serial>SLIO-ORG_lun0_1136c205-74f7-43bd6993</serial>
      <size>10737418240</size>
      <vendor_id>LIO-ORG</vendor_id>
      <volume_group_id>O9Du7I-RahN</volume_group_id>
    </logical_unit>
  </logical_units>
  <type>iscsi</type>
  <host id="8bb5ade5-e988-4000-8b93-dbfc6717fe50"/>
</host_storage>

A new system dashboard is available in the Administration portal. The dashboard provides an overview of the system status, and provides the ability to analyze system issues.

A new system dashboard is available in the Administration portal. The dashboard provides an overview of the system status, and provides the ability to analyze system issues.

With this release, you can use the Admininistration Portal to upload virtual disk images and attach them to virtual machines. The uploaded image must be a QEMU-compatible image file that can be connected to QEMU virtual machines. Note that ovirt-imageio-proxy needs to be installed on the Manager for this feature to work.

With this release, you can use the Admininistration Portal to upload virtual disk images and attach them to virtual machines. The uploaded image must be a QEMU-compatible image file that can be connected to QEMU virtual machines. Note that ovirt-imageio-proxy needs to be installed on the Manager for this feature to work.

You can preserve disk content, including the local storage domain, during a reinstallation of RHVH. Additional configuration during the setup is required.

You can preserve disk content, including the local storage domain, during a reinstallation of RHVH. Additional configuration during the setup is required.

When creating a virtual machine from a template, the user is able to choose the format of the disks: either RAW or QCOW2. The Allocation Policy section is now hidden. If the Template Provisioning is Thin, the format of the disks will be marked as QCOW2 and the user won't be able to change it. If the Template Provisioning is Clone, the user will be able to select either QCOW2 or RAW.

When creating a virtual machine from a template, the user is able to choose the format of the disks: either RAW or QCOW2. The Allocation Policy section is now hidden. If the Template Provisioning is Thin, the format of the disks will be marked as QCOW2 and the user won't be able to change it. If the Template Provisioning is Clone, the user will be able to select either QCOW2 or RAW.

The Import Virtual Machine(s) window now lists virtual machines in alphabetical order, even after dragging virtual machines between lists.

The Import Virtual Machine(s) window now lists virtual machines in alphabetical order, even after dragging virtual machines between lists.

Added a DEBUG mode to log sampling, hourly, and daily job times in the ovirt-engine-dwhd.log file.

To enable DEBUG mode, add a configuration file, for example /etc/ovirt-engine-dwhd/logging.conf, and add the value DWH_AGGREGATION_DEBUG=true in the file.

Added a DEBUG mode to log sampling, hourly, and daily job times in the ovirt-engine-dwhd.log file.

To enable DEBUG mode, add a configuration file, for example /etc/ovirt-engine-dwhd/logging.conf, and add the value DWH_AGGREGATION_DEBUG=true in the file.

The instance type field was missing in the REST API virtual machine pool resource. This update adds the ability to pick one when creating the virtual machine pool, and to report the currently configured instance type.

The instance type field was missing in the REST API virtual machine pool resource. This update adds the ability to pick one when creating the virtual machine pool, and to report the currently configured instance type.

With this update, new fields have been added to the session tab in Red Hat Virtualization to show the the client ip address, the session start time, and last access time.

With this update, new fields have been added to the session tab in Red Hat Virtualization to show the the client ip address, the session start time, and last access time.

You can now deploy or undeploy additional self-hosted engine hosts from the Administration Portal or using the REST API. Running 'hosted-engine --deploy' on additional self-hosted engine hosts is no longer required.

You can now deploy or undeploy additional self-hosted engine hosts from the Administration Portal or using the REST API. Running 'hosted-engine --deploy' on additional self-hosted engine hosts is no longer required.

With this update, OpenStack Platform 8 has been certified as a supported external network provider for Red Hat Virtualization 4.0. Install hosts with OpenStack Platform 8's Neutron agent, either manually or via packstack, then add OpenStack Platform 8's Neutron service as an external network provider then add hosts to the Red Hat Virtualization 4.0 data center.

With this update, OpenStack Platform 8 has been certified as a supported external network provider for Red Hat Virtualization 4.0. Install hosts with OpenStack Platform 8's Neutron agent, either manually or via packstack, then add OpenStack Platform 8's Neutron service as an external network provider then add hosts to the Red Hat Virtualization 4.0 data center.

The Import Virtual Machine(s) window contains a tooltip question mark (?) next to the Data Center field when importing a VMWare source. When hovered over, the tooltip explains that folders can also be added to the Data Center field in the format <folder>/<Datacenter>.

The Import Virtual Machine(s) window contains a tooltip question mark (?) next to the Data Center field when importing a VMWare source. When hovered over, the tooltip explains that folders can also be added to the Data Center field in the format <folder>/<Datacenter>.

With this update, the virtual machine name is now included in the title of both noVNC and SPICE HTML5 windows. This means that it is now easier to know which virtual machine each console is connected to.

With this update, the virtual machine name is now included in the title of both noVNC and SPICE HTML5 windows. This means that it is now easier to know which virtual machine each console is connected to.

With this update, RPM-based firmware updates can now be installed.

With this update, RPM-based firmware updates can now be installed.

This update prevents UI exceptions from repeatedly spamming the remote /var/log/ovirt-engine/ui.log after subsequent occurrences of the same error. Each remote operation is an HTTP request and consumes network resources.

Any uncaught exception in the Administration Portal or User Portal is compared to the last one, and only logged remotely if it's not the same. All occurrences are still logged on the web browser.

This update prevents UI exceptions from repeatedly spamming the remote /var/log/ovirt-engine/ui.log after subsequent occurrences of the same error. Each remote operation is an HTTP request and consumes network resources.

Any uncaught exception in the Administration Portal or User Portal is compared to the last one, and only logged remotely if it's not the same. All occurrences are still logged on the web browser.

With this update, python-cheetah was replaced with python-jinja2 as the template-engine for services configuration files. This update was required as python-cheetah stopped receiving updates in 2012 and is not available in Red Hat Enterprise Linux 7.2.

With this update, python-cheetah was replaced with python-jinja2 as the template-engine for services configuration files. This update was required as python-cheetah stopped receiving updates in 2012 and is not available in Red Hat Enterprise Linux 7.2.

This release adds hooks to enable custom actions on several system events, such as before or after migration and hibernation.

This release adds hooks to enable custom actions on several system events, such as before or after migration and hibernation.

The new web UI called Cockpit is available to fine-tune and troubleshoot Red Hat Virtualization Hosts. Cockpit is integrated into the Administration Portal, and can be accessed via the Cockpit sub-tab of the Hosts tab.

Cockpit is installed by default on Red Hat Virtualization Hosts. To use the feature on Red Hat Enterprise Linux-based hosts, install the following packages:
- cockpit-ovirt-uiplugin package on the Red Hat Virtualization Manager
- cockpit and optional cockpit-ovirt-dashboard packages on each host.

The new web UI called Cockpit is available to fine-tune and troubleshoot Red Hat Virtualization Hosts. Cockpit is integrated into the Administration Portal, and can be accessed via the Cockpit sub-tab of the Hosts tab.

Cockpit is installed by default on Red Hat Virtualization Hosts. To use the feature on Red Hat Enterprise Linux-based hosts, install the following packages:
- cockpit-ovirt-uiplugin package on the Red Hat Virtualization Manager
- cockpit and optional cockpit-ovirt-dashboard packages on each host.

With this release, the Administration Portal displays the operating system pretty name for all hosts that have an /etc/os-release file with the PRETTY_NAME entry. When you select a host, you can see an "OS Description" field in the "Software" section of the "General" sub-tab. This field can be used to tell the difference between Red Hat Virtualization Hosts (RHVH) and RHEL hosts. Note: this enhancement is not accessible to the REST API.

With this release, the Administration Portal displays the operating system pretty name for all hosts that have an /etc/os-release file with the PRETTY_NAME entry. When you select a host, you can see an "OS Description" field in the "Software" section of the "General" sub-tab. This field can be used to tell the difference between Red Hat Virtualization Hosts (RHVH) and RHEL hosts. Note: this enhancement is not accessible to the REST API.

A progress bar has been introduced to view the progress of file transfers when dragging and dropping files from a client machine to a guest machine.

A progress bar has been introduced to view the progress of file transfers when dragging and dropping files from a client machine to a guest machine.

The virt-viewer and libgovirt packages have been updated to adjust to authentication changes in Red Hat Virtualization 4.0. This ensures that the foreign menu continues working correctly on Red Hat Virtualization 4.0 when starting the remote-viewer utility using the web portal interface. Note, however, that the menu does not work when starting remote-viewer from the command line.

The virt-viewer and libgovirt packages have been updated to adjust to authentication changes in Red Hat Virtualization 4.0. This ensures that the foreign menu continues working correctly on Red Hat Virtualization 4.0 when starting the remote-viewer utility using the web portal interface. Note, however, that the menu does not work when starting remote-viewer from the command line.

A virtual machine can now override the cluster compatibility version, meaning that within a cluster with a 4.0 compatibility level, there can be virtual machines with 3.6 compatibility, retaining the configuration and behavior of 3.6. That is 4.0 features are not applied to them.

A virtual machine can now override the cluster compatibility version, meaning that within a cluster with a 4.0 compatibility level, there can be virtual machines with 3.6 compatibility, retaining the configuration and behavior of 3.6. That is 4.0 features are not applied to them.

The Virt Viewers .vv file's 'versions=' row requires a remote-viewer that supports the 'sso-token=' row. The minimum versions are:
- Windows (64-bit and 32-bit): 2.0-160
- Red Hat Enterprise Linux 7: 2.0-8
- Red Hat Enterprise Linux 6: No supporting sso-token planned.

The Virt Viewers .vv file's 'versions=' row requires a remote-viewer that supports the 'sso-token=' row. The minimum versions are:
- Windows (64-bit and 32-bit): 2.0-160
- Red Hat Enterprise Linux 7: 2.0-8
- Red Hat Enterprise Linux 6: No supporting sso-token planned.

In version 4 of the API, the top level /capabilities collection has been replaced with /clusterlevels, which contains information about the supported cluster levels (such as the available CPU types). The legal values for enumerated types, previously found in /capabilities, can now be found in /ovirt-engine/api/model.xml or /ovirt-engine/api/model.json.

In version 4 of the API, the top level /capabilities collection has been replaced with /clusterlevels, which contains information about the supported cluster levels (such as the available CPU types). The legal values for enumerated types, previously found in /capabilities, can now be found in /ovirt-engine/api/model.xml or /ovirt-engine/api/model.json.

With this update, a log message with the data warehouse application settings has been added to the log file each time the data warehouse is started. This message was added because the user can update the application settings and it provides a better way to debug and monitor the data warehouse settings.

With this update, a log message with the data warehouse application settings has been added to the log file each time the data warehouse is started. This message was added because the user can update the application settings and it provides a better way to debug and monitor the data warehouse settings.

With this update, the Red Hat Enterprise Virtualization Hypervisor (RHEV-H) has been renamed to the Red Hat Virtualization Host (RHVH) and the RPM names have been updated to reflect the name change.

With this update, the Red Hat Enterprise Virtualization Hypervisor (RHEV-H) has been renamed to the Red Hat Virtualization Host (RHVH) and the RPM names have been updated to reflect the name change.

Added Red Hat Virtualization Host support to Red Hat Virtualization to ensure that a Red Hat Enteprise Linux host and Red Hat Virtualization Host behave the same for all relevant host lifecycle flows, for example installations and upgrades.

Added Red Hat Virtualization Host support to Red Hat Virtualization to ensure that a Red Hat Enteprise Linux host and Red Hat Virtualization Host behave the same for all relevant host lifecycle flows, for example installations and upgrades.

The REST API now includes CORS support. The support depends on a filter developed by eBay. The ebay-cors-filter package is available in the standard RHV-M channel.

The REST API now includes CORS support. The support depends on a filter developed by eBay. The ebay-cors-filter package is available in the standard RHV-M channel.

Removed foreign keys from the history database to provide better sampling scale performance.

Removed foreign keys from the history database to provide better sampling scale performance.

When creating a virtual machine using the template name or Blank and not specifying the template version in the REST API, the latest template version is used. Prior to this enhancement, the template version, if not specified, was randomly selected.

When creating a virtual machine using the template name or Blank and not specifying the template version in the REST API, the latest template version is used. Prior to this enhancement, the template version, if not specified, was randomly selected.

The sampling interval default time has been decreased from 1 minute to 20 seconds to provide more accurate calculations for the new dashboards.

The sampling interval default time has been decreased from 1 minute to 20 seconds to provide more accurate calculations for the new dashboards.

With this update, a new option been added to the options for a virtual machine pool for disk storage. This option allows the user to select Auto Select Disk Target, instead of a specific domain. This means that every new virtual machine in the pool will use the storage domain with the most available space.

With this update, a new option been added to the options for a virtual machine pool for disk storage. This option allows the user to select Auto Select Disk Target, instead of a specific domain. This means that every new virtual machine in the pool will use the storage domain with the most available space.

The API HTML documentation is now automatically generated and available from any live Manager from the /ovirt-engine/api/model URL.

The API HTML documentation is now automatically generated and available from any live Manager from the /ovirt-engine/api/model URL.

Added the ability to configure different bus interfaces (IDE, SCSI, and SATA) for different virtual machine chipsets. By default, the SATA interface is used for the Q35 chipset.

Added the ability to configure different bus interfaces (IDE, SCSI, and SATA) for different virtual machine chipsets. By default, the SATA interface is used for the Q35 chipset.

With this update, Red Hat Virtualization 4.0 can now restore backups taken of Red Hat Enterprise Virtualization 3.6. Red Hat Virtualization 4.0 does not support Red Hat Enterprise Linux 6 and, previously, this meant that users could not upgrade from Red Hat Enterprise Virtualization 3.6. Now, users can back up their Red Hat Enterprise Virtualization 3.6 and restore it on Red Hat Virtualization 4.0. 

To backup Red Hat Enterprise Virtualization 3.6 run, engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log. Other options for engine-backup, including remote databases, can be found in the engine-backup documentation, https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html-single/Administration_Guide/index.html#sect-Backing_Up_and_Restoring_the_Red_Hat_Enterprise_Virtualization_Manager

To migrate to Red Hat Virtualization 4.0, install Red Hat Virtualization 4.0 then copy engine-3.6.bck to the Red Hat Enterprise Linux machine. Run engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions to restore the backup then run engine-setup.

With this update, Red Hat Virtualization 4.0 can now restore backups taken of Red Hat Enterprise Virtualization 3.6. Red Hat Virtualization 4.0 does not support Red Hat Enterprise Linux 6 and, previously, this meant that users could not upgrade from Red Hat Enterprise Virtualization 3.6. Now, users can back up their Red Hat Enterprise Virtualization 3.6 and restore it on Red Hat Virtualization 4.0. 

To backup Red Hat Enterprise Virtualization 3.6 run, engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log. Other options for engine-backup, including remote databases, can be found in the engine-backup documentation, https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html-single/Administration_Guide/index.html#sect-Backing_Up_and_Restoring_the_Red_Hat_Enterprise_Virtualization_Manager

To migrate to Red Hat Virtualization 4.0, install Red Hat Virtualization 4.0 then copy engine-3.6.bck to the Red Hat Enterprise Linux machine. Run engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions to restore the backup then run engine-setup.

Previously, cluster compatibility version upgrades were blocked if there was a running virtual machine in the cluster. Now, the user is informed about running/suspended virtual machines in a cluster when changing the cluster version. All such virtual machines are marked with a Next Run Configuration symbol to denote the requirement for rebooting them as soon as possible after the cluster version upgrade.

Previously, cluster compatibility version upgrades were blocked if there was a running virtual machine in the cluster. Now, the user is informed about running/suspended virtual machines in a cluster when changing the cluster version. All such virtual machines are marked with a Next Run Configuration symbol to denote the requirement for rebooting them as soon as possible after the cluster version upgrade.

With this release, Red Hat Virtualization can consume FCoE block storage. Depending on the FCoE card on the hosts, special configuration may be needed as described in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/fcoe-config.html. To enable FCoe on a NIC, attach a network to it, and set the "fcoe" network custom property to enable=yes[,dcb=yes][,auto_vlan=yes].

With this release, Red Hat Virtualization can consume FCoE block storage. Depending on the FCoE card on the hosts, special configuration may be needed as described in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/fcoe-config.html. To enable FCoe on a NIC, attach a network to it, and set the "fcoe" network custom property to enable=yes[,dcb=yes][,auto_vlan=yes].

Virtual machine monitoring and basic tuning and troubleshooting of hypervisors can be done through the Cockpit user interface. The cockpit package is installed by default for Red Hat Virtualization Host (RHVH) and is a technology preview feature and requires an optional installation for standard Red Hat Enterprise Linux hosts. The cockpit-ovirt RPM is available in the standard Red Hat Enterprise Linux host repositories.

Virtual machine monitoring and basic tuning and troubleshooting of hypervisors can be done through the Cockpit user interface. The cockpit package is installed by default for Red Hat Virtualization Host (RHVH) and is a technology preview feature and requires an optional installation for standard Red Hat Enterprise Linux hosts. The cockpit-ovirt RPM is available in the standard Red Hat Enterprise Linux host repositories.

To simplify Data Warehouse database views for the user, this update adds a view for each time period (sample, hourly, and daily). The views join the configuration views with statistics views of the entities it relates to, for example network interface and disks. This means three new views have been added for virtual machines, and three for hosts.

To simplify Data Warehouse database views for the user, this update adds a view for each time period (sample, hourly, and daily). The views join the configuration views with statistics views of the entities it relates to, for example network interface and disks. This means three new views have been added for virtual machines, and three for hosts.

This update improves the error message received when Cockpit cannot be displayed in the Administration portal's Host's sub-tab. The error now includes SSL certificate information and a link to the Cockpit ping page.

This update improves the error message received when Cockpit cannot be displayed in the Administration portal's Host's sub-tab. The error now includes SSL certificate information and a link to the Cockpit ping page.

With this update, when logging into the Administration Portal, the browser password setting is used so users do not need to re-enter their user name and password. 

Note: For Google Chrome, the Manager CA needs to be imported first. Use the following steps:
1. Open Chrome Settings > Show advanced settings > HTTPS/SSL > Manage certificates.
2. Click the Authorities tab and click import.
3. Select the Manager CA, click ok, and check all boxes in the Edit trust settings in the subsequent dialog.
4. Restart your browser and now Google Chrome will prompt you to save passwords.

With this update, when logging into the Administration Portal, the browser password setting is used so users do not need to re-enter their user name and password. 

Note: For Google Chrome, the Manager CA needs to be imported first. Use the following steps:
1. Open Chrome Settings > Show advanced settings > HTTPS/SSL > Manage certificates.
2. Click the Authorities tab and click import.
3. Select the Manager CA, click ok, and check all boxes in the Edit trust settings in the subsequent dialog.
4. Restart your browser and now Google Chrome will prompt you to save passwords.

This release adds support for fencing of ilo3 and ilo4 via SSH.

This release adds support for fencing of ilo3 and ilo4 via SSH.

With this update, virtual disks can now be uploaded to a Red Hat Virtualization storage domain from the Administration Portal. To upload a virtual disk from the Administration Portal, go to the Storage tab, then the Disks sub-tab, and click Upload. Select the required file, enter the disk's virtual size, then click OK. Note that ovirt-imageio-proxy needs to be installed on the Manager for this feature to work.

With this update, virtual disks can now be uploaded to a Red Hat Virtualization storage domain from the Administration Portal. To upload a virtual disk from the Administration Portal, go to the Storage tab, then the Disks sub-tab, and click Upload. Select the required file, enter the disk's virtual size, then click OK. Note that ovirt-imageio-proxy needs to be installed on the Manager for this feature to work.

With this update, the new Anaconda installer has added the ability to identify individual disks. This change was required to ensure the correct installation decisions are made.

With this update, the new Anaconda installer has added the ability to identify individual disks. This change was required to ensure the correct installation decisions are made.

Red Hat Virtualization Manager runs on Red Hat Enterprise Linux 7 with Red Hat JBoss Enterprise Application Platform 7.0.

Red Hat Virtualization Manager runs on Red Hat Enterprise Linux 7 with Red Hat JBoss Enterprise Application Platform 7.0.

With this update, the swap partition can be placed on a separate device. This allows a user to put the swap partition on a device suitable for this specific load, which differs from the load on the root filesystem.

With this update, the swap partition can be placed on a separate device. This allows a user to put the swap partition on a device suitable for this specific load, which differs from the load on the root filesystem.

This is to help avoid the problem of MAC collision in the user's LAN. Such a problem could appear immediately or later, when two active NICs with the same problematic MAC could appear in the user's LAN, one on the imported virtual machine, and another one on any other network appliance that isn't managed by the this Red Hat Virtualization instance.

This is to help avoid the problem of MAC collision in the user's LAN. Such a problem could appear immediately or later, when two active NICs with the same problematic MAC could appear in the user's LAN, one on the imported virtual machine, and another one on any other network appliance that isn't managed by the this Red Hat Virtualization instance.

With this release, the user's browser setting for saving user names and passwords will be used for the User Portal login screen.

With this release, the user's browser setting for saving user names and passwords will be used for the User Portal login screen.

This update provides support for the Q35-based machine type supported by QEMU, it is an alternative to older i440fx chipset. Compared to i440fx, Q35 allows for better support of PCI-e passthrough as it has a proper PCI-e bus[1]. One of the differences is also that the Q35 does not use IDE cdrom, but prefers SATA bus. The reason for that is the lack of IDE.

[1] http://wiki.qemu.org/Features/Q35

This update provides support for the Q35-based machine type supported by QEMU, it is an alternative to older i440fx chipset. Compared to i440fx, Q35 allows for better support of PCI-e passthrough as it has a proper PCI-e bus[1]. One of the differences is also that the Q35 does not use IDE cdrom, but prefers SATA bus. The reason for that is the lack of IDE.

[1] http://wiki.qemu.org/Features/Q35

A mobile client for Red Hat Enterprise Virtualization which is compatible Red Hat Enterprise Virtualization 3.5 onwards, is available for Android devices.

A mobile client for Red Hat Enterprise Virtualization which is compatible Red Hat Enterprise Virtualization 3.5 onwards, is available for Android devices.

A new UI plugin API function `showAlert` allows UI plugins to display global alert boxes in the top-center of the Administration portal.

This is useful to inform users of important events. The `showAlert` function supports different alert types (danger, warning, success, info), and can auto-hide after given time period.

A new UI plugin API function `showAlert` allows UI plugins to display global alert boxes in the top-center of the Administration portal.

This is useful to inform users of important events. The `showAlert` function supports different alert types (danger, warning, success, info), and can auto-hide after given time period.

Previously, the Manager's CA certificate could be downloaded from: http://[engine-fqdn]/ca.crt. With this update, the URL to download the CA certificate has changed to: http://[engine-fqdn]/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA. Existing clients that use the old URL must be updated to use the new one.

Previously, the Manager's CA certificate could be downloaded from: http://[engine-fqdn]/ca.crt. With this update, the URL to download the CA certificate has changed to: http://[engine-fqdn]/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA. Existing clients that use the old URL must be updated to use the new one.

A disk label may still appear on a disk after removing the disk partitions. This can cause empty disks without any partitions to be shown as locked in the Storage Devices sub-tab under Hosts. This prevents users from creating a gluster brick from this disk.

To workaround this issue, use the 'dd' command to clear the disks:

dd if=/dev/zero of=<disk> bs=512 count=1

A disk label may still appear on a disk after removing the disk partitions. This can cause empty disks without any partitions to be shown as locked in the Storage Devices sub-tab under Hosts. This prevents users from creating a gluster brick from this disk.

To workaround this issue, use the 'dd' command to clear the disks:

dd if=/dev/zero of=<disk> bs=512 count=1

If a user configures Red Hat Virtualization Host (RHVH) networking using Cockpit and leaves the Cockpit browser tab open then adds RHVH to the Red Hat Virtualization Manager the DNS configuration of the host is reset. The user must ensure that they log out and close the Cockpit browser tab before adding RHVH to the Red Hat Virtualization Manager. This means that the DNS configuration will be configured as it was previously through RHVH.

If a user configures Red Hat Virtualization Host (RHVH) networking using Cockpit and leaves the Cockpit browser tab open then adds RHVH to the Red Hat Virtualization Manager the DNS configuration of the host is reset. The user must ensure that they log out and close the Cockpit browser tab before adding RHVH to the Red Hat Virtualization Manager. This means that the DNS configuration will be configured as it was previously through RHVH.

Networking support is disabled in Cockpit and networking can not be configured through Cockpit. Users can drop to the shell and manually write ifcfg files to configure networking.

Networking support is disabled in Cockpit and networking can not be configured through Cockpit. Users can drop to the shell and manually write ifcfg files to configure networking.

The ovirt-host-deploy-offline package will no longer be available in Red Hat Virtualization 4.0

The ovirt-host-deploy-offline package will no longer be available in Red Hat Virtualization 4.0

The user interface (UI) code is now aligned with the Manager's SSO infrastructure by dropping reliance on the REST webapp's HTTP session mechanism in favor of using SSO tokens.

This impacts, and potentially breaks all UI plugins because the "RestApiSessionAcquired" callback has been removed.

From now on, UI plugins should use the new "api.ssoToken" function when authenticating Manager (e.g. REST API) requests:

  var xhr = new XMLHttpRequest();
  xhr.open('GET', 'http://example.com/ovirt-engine/api');
  xhr.setRequestHeader('Authorization', 'Bearer ' + api.ssoToken());
  xhr.setRequestHeader('Accept', 'application/json');
  xhr.addEventListener('load', function () {
    // response loaded OK, parse JSON data
    var data = JSON.parse(this.responseText);
  });
  xhr.send();

The UI plugins no longer need to use session-specific request headers like "Prefer:persistent-auth" and "JSESSIONID:xxx", which simplifies their code.

The user interface (UI) code is now aligned with the Manager's SSO infrastructure by dropping reliance on the REST webapp's HTTP session mechanism in favor of using SSO tokens.

This impacts, and potentially breaks all UI plugins because the "RestApiSessionAcquired" callback has been removed.

From now on, UI plugins should use the new "api.ssoToken" function when authenticating Manager (e.g. REST API) requests:

  var xhr = new XMLHttpRequest();
  xhr.open('GET', 'http://example.com/ovirt-engine/api');
  xhr.setRequestHeader('Authorization', 'Bearer ' + api.ssoToken());
  xhr.setRequestHeader('Accept', 'application/json');
  xhr.addEventListener('load', function () {
    // response loaded OK, parse JSON data
    var data = JSON.parse(this.responseText);
  });
  xhr.send();

The UI plugins no longer need to use session-specific request headers like "Prefer:persistent-auth" and "JSESSIONID:xxx", which simplifies their code.

The Red Hat Access plugin for Red Hat Enterprise Virtualization has been deprecated and converted to a page that points to the product documentation. The questions regarding proxy configuration for the plugin when running engine-setup has been removed.

The Red Hat Access plugin for Red Hat Enterprise Virtualization has been deprecated and converted to a page that points to the product documentation. The questions regarding proxy configuration for the plugin when running engine-setup has been removed.

The "/vms/<vmid>/move" API has been removed after being deprecated in Red Hat Enterprise Virtualization 3.1.

The "/vms/<vmid>/move" API has been removed after being deprecated in Red Hat Enterprise Virtualization 3.1.

The ovirt-image-uploader tool has been deprecated in Red Hat Virtualization 4.0, and will be removed in Red Hat Virtualization 4.1.

The ovirt-image-uploader tool has been deprecated in Red Hat Virtualization 4.0, and will be removed in Red Hat Virtualization 4.1.

Removed data center statistic tables and views which provided meaningless status statistics.

Removed data center statistic tables and views which provided meaningless status statistics.

Additional self-hosted engine hosts can only be added via the Administration Portal, and can no longer be added by running 'hosted-engine --deploy' on the host.

Additional self-hosted engine hosts can only be added via the Administration Portal, and can no longer be added by running 'hosted-engine --deploy' on the host.

The Spice plug-in is not supported in Red Hat Virtualization 4.0. The 'Native' spice connection should be used as a replacement.

If 'Plugin' is set as the default for Spice connections by user (via engine-config), it is automatically switched to 'Native' by calling engine-setup during upgrade.

The Spice plug-in is not supported in Red Hat Virtualization 4.0. The 'Native' spice connection should be used as a replacement.

If 'Plugin' is set as the default for Spice connections by user (via engine-config), it is automatically switched to 'Native' by calling engine-setup during upgrade.

The Legacy USB option has been deprecated and will be removed in the next Red Hat Enterprise Virtualization version. The functionality has been superseded by "Native" with the UsbDk drivers (available since Red Hat Enterprise Virtualization 3.6).

The Legacy USB option has been deprecated and will be removed in the next Red Hat Enterprise Virtualization version. The functionality has been superseded by "Native" with the UsbDk drivers (available since Red Hat Enterprise Virtualization 3.6).

The Spice Internet Explorer plug-in is not supported in Red Hat Virtualization 4.0.
The 'Native' spice connection is suggested as a replacement. Installation on the client machine is done via MSI installers, and will not be available via CAB files.

It is recommended that users of the Spice plug-in uninstall the virt-viewer and the Spice Internet Explorer plug-in before installing via MSI.

The Spice Internet Explorer plug-in is not supported in Red Hat Virtualization 4.0.
The 'Native' spice connection is suggested as a replacement. Installation on the client machine is done via MSI installers, and will not be available via CAB files.

It is recommended that users of the Spice plug-in uninstall the virt-viewer and the Spice Internet Explorer plug-in before installing via MSI.

The collection from the Manager view dwh_disk_vm_map_history_view was replaced by the collection from dwh_vm_device_history_view on Red Hat Enterprise Virtualization 3.1,  but was not removed to ensure legacy compatibility.

In Red Hat Virtualization 4.0, legacy compatibility will be for Red Hat Enterprise Virtualization 3.6 only. Therefore, the following has now been removed:
- The collection of disks_vm_map.
- disks_vm_map table from the history database.
- dwh_vm_disk_configuration_history_view from the Manager database.

The collection from the Manager view dwh_disk_vm_map_history_view was replaced by the collection from dwh_vm_device_history_view on Red Hat Enterprise Virtualization 3.1,  but was not removed to ensure legacy compatibility.

In Red Hat Virtualization 4.0, legacy compatibility will be for Red Hat Enterprise Virtualization 3.6 only. Therefore, the following has now been removed:
- The collection of disks_vm_map.
- disks_vm_map table from the history database.
- dwh_vm_disk_configuration_history_view from the Manager database.

Red Hat Virtualization Manager 4.0 does not support data center or cluster compatibility levels 3.5 or lower. A data center or cluster compatibility version of 3.5 or lower will prevent an upgrade to Red Hat Virtualization 4.0.

Red Hat Virtualization Manager 4.0 does not support data center or cluster compatibility levels 3.5 or lower. A data center or cluster compatibility version of 3.5 or lower will prevent an upgrade to Red Hat Virtualization 4.0.

Hosts in Red Hat Virtualization 4.0 are only supported with SELinux enabled.

Hosts in Red Hat Virtualization 4.0 are only supported with SELinux enabled.

The usbclerk service has been dropped from this release. The usbdk driver is now supported instead, and it supports more devices than WinUSB, which was installed by usbclerk. The usbdk driver is installed via the MSI installer.

The usbclerk service has been dropped from this release. The usbdk driver is now supported instead, and it supports more devices than WinUSB, which was installed by usbclerk. The usbdk driver is installed via the MSI installer.