2.5. Backend

BZ#583430
The metadata structure of storage domains changed during the upgrade from Red Hat Enterprise Virtualization 2.2 to 3.0. To be backwards compatible, storage changes have to be reflected on the data center level. Now, when the user changes the data center compatibility level, VDSM is updated with the new data center format, and the compatibility levels of active storage domains are updated.
BZ#695307
Previously, Red Hat Enterprise Virtualization required that initrd (initial ramdisk) files reside on the host. Now, Red Hat Enterprise Virtualization allows loading initrd files from the ISO domain. This allows you to set boot options in the initrd file stored in the ISO domain.
BZ#702939
Previously, when you try to change a CD in a running virtual machine while the ISO domain is inactive, you would receive an unclear error message: "Driver image file could not be found". Now, if you attempt the same action, you are presented with an error message which clearly pinpoints the inactive ISO domain as the problem.
BZ#590767
Red Hat Enterprise Virtualization Manager will now display warnings on the hosts' audit logs when storage devices are slow in responding.
BZ#695602
When a data center could not reach its master storage domain, it could not be recovered and reassigned a new master domain. Now, when a data center is non-responsive, it can be forcefully removed. All data domains attached to the data center are also detached.
BZ#595610
Red Hat Enterprise Virtualization now includes database service verification on the status webpage, and the backend functionality is now supported.
BZ#688600
The new ISO uploader tool provides an ISO cache mechanism, which refreshes active ISO storage domains and displays the available images in the administration portal.
BZ#630904
Previously, when you restarted a set of highly available virtual machines after fencing the original hosts, one of the virtual machines in the set would fail to start. This happened only in heavily loaded environments (for instance, environments comprising ten hosts and 300 to 350 virtual machines). The virtual machine which failed to start would not be put in a "down" state, so you could not manually restart it. Now, hosts receive a CPU check after you fence them, and Red Hat Enterprise Virtualization Manager properly reports the status of virtual machines. If one of the machines cannot be restarted, Red Hat Enterprise Virtualization Manager puts that virtual machine into a "down" state and allows you to restart it manually.
BZ#665295
Previously, the custom property "sndbuf" was set to an unacceptably high value, causing communication failure between hosts and unresponsive guests. The sndbuf value is now set to 0, and passed to VDSM and qemu-kvm. Setting this parameter to the lowest possible value significantly mitigates the risk of communication failure when hosts attempt to communicate with unresponsive guests.
BZ#670013
When a detached host was reattached to a new cluster, the UpdateVdsCommand did not update the domain changes in the database. Consequently, the SetNonOperationalVdsCommand was executed, so the host became non-responsive. Now, the UpdateVdsCommand reflects the changes made in the administration portal, so reattaching hosts works as expected.
BZ#630661
Previously, hosts would not return to an active status after a network failure. Instead, they remained "unassigned" without a way to change the status, and VDSM did not record this error. You are now provided with means of changing the host status in the event of a network failure, and the VDSM log now records this error.
BZ#588233
Previously, agent tools were not shared, which meant that ISO images were not attached to virtual machines during boot. Metadata about agent tools is now stored in a database that is local to the Red Hat Enterprise Virtualization Manager. On an ISO domain that is shared between multiple Red Hat Enterprise Virtualization Manager environments, the agent tools are available only on the manager that is used to upload the tools until the list of ISO images is updated. To update the list of ISO images, either click the refresh button or wait the amount of time that is specified for the "AutoRepoDomainRefreshTime" option in vds_options.
BZ#506710
The Search option in the administration portal can now retrieve users according to role (for example, "Users : role = PowerUserRole") and permissions on objects (for example, "Users : Vm = rhelserver").
BZ#606076
Using the rhevm-config tool, you can now use the SANWipeAfterDelete option to configure a default option for wiping SAN disks after virtual machines are deleted.
BZ#601857
Red Hat Enterprise Virtualization supports the creation of virtual machines with minimum 512 MB RAM, but it is also possible to create a virtual machine with less RAM using the rhev-config tool. Note, however, that it is not supported.
BZ#674698
Red Hat Enterprise Virtualization now supports fencing Cisco UCS blades with slot, options and secure (SSL) arguments.
BZ#618606
When a running virtual machine was paused then restarted through vdsClient, Red Hat Enterprise Virtualization would throw a System.NullReferenceException, which caused a VDSNetworkException to be logged. With this update, a paused virtual machine can be resumed with no error messages.
BZ#621067
Red Hat Enterprise Virtualization Manager's VDSM now supports Transparent Huge Pages (THP), which is active by default.
BZ#733552
Previously in Red Hat Enterprise Virtualization Manager, when setting the timezone during the setup of a virtual Windows machine, the Australian timezones appeared twice. This issue has been corrected, and the four Australian timezones appear only once during setup.
BZ#657282
Previously, the REST API did not indicate which network had been set as the display network. It now offers representations of networks that include <display> tags, which can have their values modified.
BZ#515404
Previously, the prefix of host iSCSI initiator names was not displayed by default. The absence of iSCSI initiator names made it difficult for ACL (fraud detection) purposes such as audit analytics and continuous monitoring. Red Hat Enterprise Virtulization Manager now generates a unique random iSCSI initiator name during installation, and displays this name in the administration portal.
BZ#529554
Previously, some hosts could not detect domains after the domains had been attached to a data center. An error message should have alerted users to this, but no error message was generated. The hosts that could not detect the domain would change to a non-operational state after five minutes. Although this behavior was expected, it was not favorable in all cases. The migrateOnError option has been added so that you can select a preferred behavior:
    (NO) do nothing with the virtual machines on the host
    (YES) migrate all virtual machines from host
    (HA_ONLY) migrate only high-availability virtual machines
The default behavior is for the option to be set to YES, so all virtual machines are migrated from the host if they cannot detect the domain.
BZ#657248
Red Hat Enterprise Virtualization now displays the IP address and secure port in REST API's representation of a virtual machine.
BZ#633046
Previously, a non-operational host would become non-operational without a coherent reason, so it was difficult to troubleshoot the error and return the host to a running state. Red Hat Enterprise Virtualization now provides the reason why a non-operational host becomes non-operational under the Events log in the administration portal.
BZ#554126
You can now create a user who has administrator abilities to a virtual machine, but no access to the console.
BZ#657264
Red Hat Enterprise Virtualization now warns you when a host's physical memory drops below a threshold. By default, this value is set to 1024MB, but it can be changed. When the threshold is reached, a warning displays every five (5) hours in the Events tab of the administration portal.
BZ#626369
When using a multipath fibre channel LUN, the multipath column in the administration portal displayed the number of available paths as 0, suggesting that multiple paths were not supported. VDSM now returns the size and status for each path, and properly displays the number of available paths in the administration portal.
BZ#581928
Red Hat Enterprise Virtualization 2.1 hosts, clusters and data centers are not supported for 3.0. The installer will validate the version compatibility before upgrading, and if the Red Hat Enterprise Virtualization environment still contains 2.1 elements, the upgrade will fail.
BZ#646144
Previously, Red Hat Enterprise Virtualization Manager did not save and persist the bonding options configured on a host, which caused networking to fail, or revert to basic defaults when the host was rebooted. Now, the bonding options are saved under vds_interface in the database, and persisted upon startup.
BZ#663604
Red Hat Enterprise Virtualization Manager now properly configures Windows 7 virtual machines to use Intel HDA (High Definition Audio) sound cards.
BZ#642635
Red Hat Enterprise Virtualization Manager now supports the ilo3 fence agent, which is implemented by ipmilan with timeout=4,lanplus as the default implicit parameters. These implicit parameters can be overriden if you specify further options when configuring power management for your host in the administration portal.
BZ#618224
Previously, a host's CPU model was detected based on the CPU flags set on it. This enabled compatibility checks with host clusters. Now, Red Hat Enterprise Virtualization Manager uses pre-defined qemu-kvm CPU models for hosts. This improves the accuracy of host CPU detection, so the hosts can be correctly attached to clusters with compatible CPU settings.
BZ#611314
Red Hat Enterprise Virtualization supports Active Directory as a standalone directory running on the Red Hat Enterprise Virtualization Manager, or as remote forests. Active Directory enables administrators to authenticate and manage users, and also manage virtual machines.
BZ#666712
A previous version of Red Hat Enterprise Virtualization requested far too many objects during refresh, and Active Directory was unable to handle more than 1000 objects per refresh. This also put an unacceptably heavy load on the server. Now, the AdGetAdUsersByUserdListCommand query only permits 1000 or less object requests per refresh. This prevents Active Directory from being overloaded with requests, and prevents the LDAP server from being overloaded.
BZ#622267
Previously, Red Hat Enterprise Virtualization did not lock virtual machines to specific hosts. Now, a virtual machine can be configured to run on only one host, with live migration and system scheduler disabled.
BZ#667659
Previously, the MaxRerunVmOnVdsCount variable was set to 1000 by default, which caused failed virtual machines to be unresponsive and impossible to stop until they had completed the loop of 1000 trials. The default MaxRerunVmOnVdsCount is now set to 3, providing improved responsiveness if virtual machines fail.
BZ#617979
Previously, the objectClass filter was used to search for users in the Active Directory. Now, the filter used is sAMAccountType. Performing a search for users from the administration portal is now faster.
BZ#669401
Red Hat Enterprise Virtualization now supports the Westmere family of Intel processors.
BZ#669421
Previously, when a template was removed, it was simultaenously deleted from all storage domains and databases. You can now delete a template from one domain, but retain it in another, by using the Storage sub tab under the Template tab.
BZ#616991
Red Hat Enterprise Virtualization Manager now supports the fencing of Dell blades using the drac5 power management type. In the administration portal, the 'Slot' field enables specification of strings which are diverted to the port parameter of the drac5 fence agent script.
BZ#598082
Previously, Red Hat Enterprise Virtualization Manager did not properly select another host as storage pool manager (SPM) for the data center when an old SPM was down or in a non-operational state. Red Hat Enterprise Virtualization 3.0 has changed the basic storage flows in the backend, and this issue no longer arises.
BZ#641935
Previously, Red Hat Enterprise Virtualization Manager did not save and persist the bonding options configured on a host, which caused networking to fail, or revert to basic defaults when the host was rebooted. Now, the bonding options are saved under vds_interface in the database, and persisted upon startup.
BZ#614921
Previously, Red Hat Enterprise Virtualization Manager did not support custom virtual machine boot options. Now, when creating or running a virtual machine from the administration portal, users can specify three Linux boot options: kernel path, initrd path and kernel parameters.
BZ#613885
Previously, the cluster compatibility version could not be changed if there were running virtual machines present in the cluster. Now, after a cluster CPU level change, virtual machines that were started before the change will continue to run with the pre-change CPU flags. This does not have an effect on their operation, but prevents the suspension of those virtual machine until they are powered off and then back on.
BZ#613058
Red Hat Enterprise Virtualization now supports virtual machines running Red Hat Enterprise Linux 3, 4, 5 and 6.
BZ#641881
Previously, VSDM detected users connected to a virtual machine from a guest agent. Now, when a user connects to a virtual machine via the SPICE or VNC console, the Red Hat Enterprise Virtualization backend is automatically updated with the user's information. It also cleans the client IP record when a user disconnects from the virtual machine.
BZ#613026
Previously, the Red Hat Enterprise Virtualization Manager event log only recorded actions performed in the administration portal and API. It did not elaborate on the changes made to the system. Now, the logs display more meaningful messages, including configuration changes, the user responsible for each action, severity levels and error numbers.
BZ#638548
Previously, Red Hat Enterprise Virtualization did not prevent hosts from being fenced until after a certain amount of time had elapsed. This effectively caused the host to shut down while it was still initializing. Red Hat Enterprise Virtualization now implements DisableFenceAtStartupInSec with a default of 300 seconds, which prevents hosts from being fenced while starting up.
BZ#607493
Previously, you could input a network name with a dash, which initiated an attempt to load the parent configuration. Dashes have now been disallowed when assigning network names.
BZ#611186
Red Hat Enterprise Virtualization now provides a multi-level administration (MLA) system, which provides a hierachical model for assigning levels of permissions on virtual resources for users.
BZ#612480
Red Hat Enterprise Virtualization now supports non-migratable virtual machines. These machines are permanently associated with one host, and will not be migrated when the host is set to non-operational, but they are automatically restarted when the host is powered up after maintenance.
BZ#687888
Previously, you could edit and rename the Blank virtual machine template, which made it possible to lose the Blank template. Red Hat Enterprise Virtualization now prohibits editing of the Blank Template. If you try to edit the Blank template, an error message informs you not to do so.
BZ#612478
Red Hat Enterprise Virtualization now supports all Intel and AMD chipsets, including X2APIC architecture.
BZ#612477
Previously, the Red Hat Enterprise Virtualization Manager determined the host on which a guest should run based on the CPU flags set on the host. Now, the hosts are selected based on their CPU model as detected by qemu-kvm.
BZ#611325
Red Hat Enterprise Virtualization 3.0 supports SQL Server 2005 SP4.
BZ#611203
With the new multi-level administration system, only Super Users can assign administrative permissions on objects to other users. Conversely, Power Users can assign user permissions on objects to other users.
BZ#611306
Red Hat Enterprise Virtualization now has Java backend support.
BZ#617982
Previously, the Red Hat Enterprise Virtualization Hypervisor supported a maximum number of 8 NICs per virtual machine. Now, the number of NICs is no longer a limit, because there can be as many NICs as PCI devices per virtual machine. Each virtual machine supports 32 virtualized PCI devices, with 4 slots taken up by mandatory system devices.
BZ#695300
Red Hat Enterprise Virtualization now provides a Linux daemon for event notification services.
BZ#695301
Red Hat Enterprise Virtualization now supports Identity, Policy and Audit (IPA) as a directory service for user authentication.
BZ#695297
Red Hat Enterprise Linux Virtualiztion now provides the rhevm-config tool, which is a command line utility to replace a deprecated configuration editor.
BZ#736334
Red Hat Enterprise Virtualization Manager now has an internal administrator, admin@internal. This internal administrator is created during installation and has super user privileges.
BZ#734032
A previous version of Red Hat Enterprise Virtualization Manager had VNC set as the Blank template's default display protocol. The Blank template's default display protocol in Red Hat Enterprise Virtualization Manager is now set to SPICE.
BZ#720444
The history database has changed in Red Hat Enterprise Virtualization Manager. guest_disk_size_mb and guest_used_disk_size_mb have been removed from all views. A new column of type text has been added to the vm samples\hourly\daily history section. It contains JSON pattern type text that lists all the virtual machines' disk size properties.
BZ#680159
Previously, the names of data centers did not display in the event log, instead they were replaced with the names of storage domains. Now, data centers' names are accurately recorded in the event log and the audit log.
BZ#681211
Previously, Red Hat Enterprise Virtualization did not provide cluster information in the Events log. Now, cluster information displays in the Advanced view of the Events log.
BZ#683375
Previously, the Red Hat Enterprise Virtualization Manager supported dual NICs, which allowed the same MAC address to be assigned to two NICs (a PV NIC and an RTL NIC) and were represented by the rtl_pv NIC type. The rtl_pv NIC type was used to circumvent the problem of attaching networks to the initial boot of a virtual machine when it did not contain the PV drivers by default. Red Hat Enterprise Virtualization 3.0 no longer requires the rtl_pv NIC type, hence the NIC type is no longer available.