3.6. Red Hat Virtualization Batch Update 5 (ovirt-4.1.6)

When configuring Active Directory (AD) with the ovirt-engine-extension-aaa-ldap-setup tool, regardless of whether you are defining a multiple or single domain forest, you can only configure the name of the forest - you cannot define the name of a specific domain or a specific server.

This release provides examples for common advanced AD configuration which users can copy to their local environment and adapt as required. These examples are bundled within the ovirt-engine-extension-aaa-ldap package and after installing the package, a description of these examples can be found in /usr/share/ovirt-engine-extension-aaa-ldap/examples/README.md

In addition, the following improvements have been made to the ovirt-engine-extension-aaa-ldap-setup tool:

1. A more detailed error reporting for various AD forest configuration steps.
2. A mandatory login test that checks the configuration (previously this test was optional).

When configuring Active Directory (AD) with the ovirt-engine-extension-aaa-ldap-setup tool, regardless of whether you are defining a multiple or single domain forest, you can only configure the name of the forest - you cannot define the name of a specific domain or a specific server.

This release provides examples for common advanced AD configuration which users can copy to their local environment and adapt as required. These examples are bundled within the ovirt-engine-extension-aaa-ldap package and after installing the package, a description of these examples can be found in /usr/share/ovirt-engine-extension-aaa-ldap/examples/README.md

In addition, the following improvements have been made to the ovirt-engine-extension-aaa-ldap-setup tool:

1. A more detailed error reporting for various AD forest configuration steps.
2. A mandatory login test that checks the configuration (previously this test was optional).

The ovirt-ansible-roles package contains Ansible roles, which can help administrators with common Red Hat Virtualization administration tasks. All roles can be executed from the command line using Ansible, but some of those roles can also be executed directly from the Red Hat Virtualization Manager. More details about the roles can be found in README.md included in the package (/usr/share/doc/ovirt-ansible-roles/README.md), or directly in the source code repository (https://github.com/ovirt/ovirt-ansible).

The ovirt-ansible-roles package contains Ansible roles, which can help administrators with common Red Hat Virtualization administration tasks. All roles can be executed from the command line using Ansible, but some of those roles can also be executed directly from the Red Hat Virtualization Manager. More details about the roles can be found in README.md included in the package (/usr/share/doc/ovirt-ansible-roles/README.md), or directly in the source code repository (https://github.com/ovirt/ovirt-ansible).

This update lists the additional features available for a cluster level, and allows you to enable or disable additional cluster features using an API.

This update lists the additional features available for a cluster level, and allows you to enable or disable additional cluster features using an API.

This update adds support for Link Layer Discovery Protocol (LLDP) in Red Hat Virtualization.

To support the integration of Red Hat Virtualization with other software, the information gathered by LLDP on each host will be provided by the Manager's REST API. Information such as the switch port number the host's network interface is connected to, will be shown in the GUI.

Known Issue BZ#1487930:
Cisco switches might send VLAN tagged 802.1Q LLDP frames. These LLDP frames are ignored if the NIC of the Red Hat Virtualization host is not attached to the corresponding Red Hat Virtualization logical network.

This update adds support for Link Layer Discovery Protocol (LLDP) in Red Hat Virtualization.

To support the integration of Red Hat Virtualization with other software, the information gathered by LLDP on each host will be provided by the Manager's REST API. Information such as the switch port number the host's network interface is connected to, will be shown in the GUI.

Known Issue BZ#1487930:
Cisco switches might send VLAN tagged 802.1Q LLDP frames. These LLDP frames are ignored if the NIC of the Red Hat Virtualization host is not attached to the corresponding Red Hat Virtualization logical network.

The user now has the option of specifying a path to the appliance OVF, as an alternative to installing the appliance RPM.

The user now has the option of specifying a path to the appliance OVF, as an alternative to installing the appliance RPM.

The ovirt-ansible-roles package contains Ansible roles, which can help administrators with common Red Hat Virtualization administration tasks. All roles can be executed from the command line using Ansible, but some of those roles can also be executed directly from the Red Hat Virtualization Manager. More details about the roles can be found in README.md included in the package (/usr/share/doc/ovirt-ansible-roles/README.md), or directly in the source code repository (https://github.com/ovirt/ovirt-ansible).

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

The ovirt-ansible-roles package contains Ansible roles, which can help administrators with common Red Hat Virtualization administration tasks. All roles can be executed from the command line using Ansible, but some of those roles can also be executed directly from the Red Hat Virtualization Manager. More details about the roles can be found in README.md included in the package (/usr/share/doc/ovirt-ansible-roles/README.md), or directly in the source code repository (https://github.com/ovirt/ovirt-ansible).

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate upgrading the whole cluster to a higher version. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-cluster-upgrade/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate upgrading the whole cluster to a higher version. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-cluster-upgrade/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate data center setup. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-infra/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate data center setup. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-infra/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate creating a VM template from an external image. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-image-template/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate creating a VM template from an external image. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-image-template/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to download a ManageIQ qcow2 image, create a VM from it, and register a provider within the ManageIQ installation. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-manageiq/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to download a ManageIQ qcow2 image, create a VM from it, and register a provider within the ManageIQ installation. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-manageiq/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate creating a virtual machine. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-vm-infra/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This Ansible role can be used to automate creating a virtual machine. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-vm-infra/README.md

Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).

This release includes a new Spice QXL WDDM DOD driver (Display-only driver for QXL virtual devices) for Windows 10 guests.

This release includes a new Spice QXL WDDM DOD driver (Display-only driver for QXL virtual devices) for Windows 10 guests.

The batik package is no longer required by the Red Hat Virtualization Manager. Red Hat recommends removing it after upgrading to Red Hat Virtualization 4.1.

The batik package is no longer required by the Red Hat Virtualization Manager. Red Hat recommends removing it after upgrading to Red Hat Virtualization 4.1.

The fop package is no longer required by the Red Hat Virtualization Manager. Red Hat recommends removing it after upgrading to Red Hat Virtualization 4.1.

The fop package is no longer required by the Red Hat Virtualization Manager. Red Hat recommends removing it after upgrading to Red Hat Virtualization 4.1.

A new VDSM hook that configures the nested virtualization feature in Red Hat Enterprise Linux 7 is now available as a tech preview. Nested virtualization allows a virtual machine to serve as a hypervisor. VDSM hooks are a means to insert code, commands, or scripts into a point in the lifecycle of a virtual machine, as well as the lifecycle of the VDSM daemon.

Packages and features released under tech preview are not fully supported under Red Hat Subscription Level Agreements, and may not be functionally complete, and are not intended for production use.

A new VDSM hook that configures the nested virtualization feature in Red Hat Enterprise Linux 7 is now available as a tech preview. Nested virtualization allows a virtual machine to serve as a hypervisor. VDSM hooks are a means to insert code, commands, or scripts into a point in the lifecycle of a virtual machine, as well as the lifecycle of the VDSM daemon.

Packages and features released under tech preview are not fully supported under Red Hat Subscription Level Agreements, and may not be functionally complete, and are not intended for production use.

Added the following changes to the GUI in this update:

- Ability to change the virtual machine's CD-ROM ISO.
- Infinite scroller for VMS list added to decrease response time.
- Added a hyperlink on "Runs on Host" to the host the running the particular virtual machine.
- Added "Loading ..." indicator during background activity.
- "Pending Changes" tag rendered when NEXT_RUN configuration exists.
- "VM Type" field added.
- Improved error messages.
- Added a "usb-filter" in the .vv file for remote-viewer.
- The setting of the Virtual Machine icon has been fixed.
- Added multiple additional functional and user interface fixes.
- Application supports branding.
- Basic support for internationalization, but translation not yet provided.
- Built as a "noarch" RPM.

Added the following changes to the GUI in this update:

- Ability to change the virtual machine's CD-ROM ISO.
- Infinite scroller for VMS list added to decrease response time.
- Added a hyperlink on "Runs on Host" to the host the running the particular virtual machine.
- Added "Loading ..." indicator during background activity.
- "Pending Changes" tag rendered when NEXT_RUN configuration exists.
- "VM Type" field added.
- Improved error messages.
- Added a "usb-filter" in the .vv file for remote-viewer.
- The setting of the Virtual Machine icon has been fixed.
- Added multiple additional functional and user interface fixes.
- Application supports branding.
- Basic support for internationalization, but translation not yet provided.
- Built as a "noarch" RPM.

On Red Hat Enterprise Linux, consistent network device naming [1] is used to generate consistent names for network devices. On some systems, the generated name is too long, limiting automated tail additions to be applied (the classic example is to create a VLAN interface over such an interface).

In cases where the long-name interface is used as a base of a VLAN, the total VLAN interface name may exceed the kernel name limit (15). As a result, the creation of the vlan fails. For example, len(<base-name> + 1(for the dot) + len<vlan-id> + 1 <= 15

The simplest workaround is to disable the new name mechanism. Alternatively, add a static udev rule to manipulate the name of the interfaces:

ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:50:56:8e:12:34", NAME="eth123"

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html

On Red Hat Enterprise Linux, consistent network device naming [1] is used to generate consistent names for network devices. On some systems, the generated name is too long, limiting automated tail additions to be applied (the classic example is to create a VLAN interface over such an interface).

In cases where the long-name interface is used as a base of a VLAN, the total VLAN interface name may exceed the kernel name limit (15). As a result, the creation of the vlan fails. For example, len(<base-name> + 1(for the dot) + len<vlan-id> + 1 <= 15

The simplest workaround is to disable the new name mechanism. Alternatively, add a static udev rule to manipulate the name of the interfaces:

ACTION=="add", SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:50:56:8e:12:34", NAME="eth123"

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html