Red Hat Enterprise Virtualization 3.2
Release notes for Red Hat Enterprise Virtualization Manager 3.2
Edition 2
Legal Notice
Copyright © 2013 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
Abstract
The Release Notes provide high-level coverage of the improvements and additions that have been implemented in Red Hat Enterprise Virtualization 3.2.
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later include the Liberation Fonts set by default.
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
Mono-spaced Bold
Used to highlight system input, including shell commands, file names and paths. Also used to highlight keys and key combinations. For example:
To see the contents of the filemy_next_bestselling_novelin your current working directory, enter thecat my_next_bestselling_novelcommand at the shell prompt and press Enter to execute the command.
The above includes a file name, a shell command and a key, all presented in mono-spaced bold and all distinguishable thanks to context.
Key combinations can be distinguished from an individual key by the plus sign that connects each part of a key combination. For example:
Press Enter to execute the command.Press Ctrl+Alt+F2 to switch to a virtual terminal.
The first example highlights a particular key to press. The second example highlights a key combination: a set of three keys pressed simultaneously.
If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in
mono-spaced bold. For example:
File-related classes includefilesystemfor file systems,filefor files, anddirfor directories. Each class has its own associated set of permissions.
Proportional Bold
This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
Choose → → from the main menu bar to launch Mouse Preferences. In the Buttons tab, select the Left-handed mouse check box and click to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).To insert a special character into a gedit file, choose → → from the main menu bar. Next, choose → from the Character Map menu bar, type the name of the character in the Search field and click . The character you sought will be highlighted in the Character Table. Double-click this highlighted character to place it in the Text to copy field and then click the button. Now switch back to your document and choose → from the gedit menu bar.
The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
Mono-spaced Bold Italic or Proportional Bold Italic
Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
To connect to a remote machine using ssh, typesshat a shell prompt. If the remote machine isusername@domain.nameexample.comand your username on that machine is john, typessh john@example.com.Themount -o remountcommand remounts the named file system. For example, to remount thefile-system/homefile system, the command ismount -o remount /home.To see the version of a currently installed package, use therpm -qcommand. It will return a result as follows:package.package-version-release
Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
Publican is a DocBook publishing system.
Terminal output and source code listings are set off visually from the surrounding text.
Output sent to a terminal is set in
mono-spaced roman and presented thus:
books Desktop documentation drafts mss photos stuff svn books_tests Desktop1 downloads images notes scripts svgs
Source-code listings are also set in
mono-spaced roman but add syntax highlighting as follows:
static int kvm_vm_ioctl_deassign_device(struct kvm *kvm,
struct kvm_assigned_pci_dev *assigned_dev)
{
int r = 0;
struct kvm_assigned_dev_kernel *match;
mutex_lock(&kvm->lock);
match = kvm_find_assigned_dev(&kvm->arch.assigned_dev_head,
assigned_dev->assigned_dev_id);
if (!match) {
printk(KERN_INFO "%s: device hasn't been assigned before, "
"so cannot be deassigned\n", __func__);
r = -EINVAL;
goto out;
}
kvm_deassign_device(kvm, match);
kvm_free_assigned_device(kvm, match);
out:
mutex_unlock(&kvm->lock);
return r;
}
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at http://access.redhat.com. Through the customer portal, you can:
- search or browse through a knowledgebase of technical support articles about Red Hat products.
- submit a support case to Red Hat Global Support Services (GSS).
- access other product documentation.
Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.com/mailman/listinfo. Click on the name of any mailing list to subscribe to that list or to access the list archives.
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product Red Hat Enterprise Virtualization Manager.
When submitting a bug report, be sure to mention the manual's identifier: Guides
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
Red Hat Enterprise Virtualization is a feature-rich server and desktop virtualization management system. It provides advanced capabilities for managing virtualization hosts and virtualized guests.
To install Red Hat Enterprise Virtualization Manager and virtualization hosts, your systems must be registered either to Red Hat Network Classic (RHN) or Red Hat Subscription Management (RHSM). RHN and RHSM cannot be used concurrently.
The Red Hat Network (RHN) provides packages necessary for installing Red Hat Enterprise Virtualization Manager and virtualization hosts. If you are using Red Hat Network Classic, you cannot use Red Hat Subscription Manager (RHSM). Ensure that your system is subscribed to the following channels before proceeding with installation:
Table 1.1. Required Channels for Red Hat Enterprise Virtualization Manager
|
Channel name
|
Channel label
|
Details
|
|---|---|---|
Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64)
|
rhel-x86_64-server-6
|
Provides the Red Hat Enterprise Linux 6 Server.
|
RHEL Server Supplementary (v. 6 64-bit x86_64)
|
rhel-x86_64-server-supplementary-6
|
Provides the virtio-win package, which provides the Windows VirtIO drivers for use in virtual machines.
|
Red Hat Enterprise Virtualization Manager (v. 3.2 x86_64)
|
rhel-x86_64-server-6-rhevm-3.2
|
Provides the Red Hat Enterprise Virtualization Manager.
|
JBoss Application Platform (v 6) for 6Server x86_64
|
jbappplatform-6-x86_64-server-6-rpm
| Provides the supported release of the JBoss application platform on which the Manager runs. |
Table 1.2. Required Channels for Red Hat Enterprise Virtualization Hypervisor
|
Channel name
|
Channel label
|
Details
|
|---|---|---|
Red Hat Enterprise Virtualization Hypervisor (v.6 x86_64)
|
rhel-x86_64-server-6-rhevh
|
Provides the rhev-hypervisor package, which includes the image required to install the hypervisor.
|
Table 1.3. Required Channels for Red Hat Enterprise Linux Host
|
Channel name
|
Channel label
|
Details
|
|---|---|---|
Red Hat Enterprise Linux Server (v. 6 for 64-bit x86_64)
|
rhel-x86_64-server-6
|
Provides the Red Hat Enterprise Linux 6 Server.
|
Red Hat Enterprise Virt Management Agent (v 6 x86_64)
|
rhel-x86_64-rhev-mgmt-agent-6
|
Provides the QEMU and KVM packages required for using Red Hat Enterprise Linux servers as virtualization hosts.
|
Important
It is recommended that you also subscribe to the beta versions of all the channels listed above. yum will notify you when there are updated packages available in either the general availability or beta versions of the channels in between major releases. The labels of the beta channels are as below:
- rhel-x86_64-server-6-beta
- rhel-x86_64-server-supplementary-6-beta
- jbappplatform-6-x86_64-server-6-rpm-beta
- rhel-x86_64-server-6-rhevh-beta
- rhel-x86_64-rhev-mgmt-agent-6-beta
The exception to this rule is the
rhel-x86_64-server-6-rhevm-3.x channel, which is newly created upon each release, and will not contain any beta packages.
The packages provided in the following channels are not strictly required to install and configure a functioning Red Hat Enterprise Virtualization environment, however they provide additional capabilities to enhance the user experience.
Table 1.4. Recommended Channels for Red Hat Enterprise Virtualization
|
Channel name
|
Channel label
|
Details
|
|---|---|---|
Red Hat Enterprise Virtualization Manager (v.3.2 x86_64)
|
rhel-x86_64-server-6-rhevm-3
|
Provides the rhevm-sdk package and ovirt-sdk Python library.
|
RHEL Server Supplementary (v. 6 64-bit x86_64)
|
rhel-x86_64-server-supplementary-6
|
Provides the spice-usb-share and kmod-kspiceusb-rhel60 for Red Hat Enterprise Linux 6, which enables USB redirection (legacy mode) on Red Hat Enterprise Linux 6 clients.
|
RHEL Supplementary EUS (v. 5.9.z for 64-bit x86_64)
|
rhel-x86_64-server-supplementary-5.9.z
|
Provides the spice-usb-share and kmod-kspiceusb-rhel5u6 for Red Hat Enterprise Linux 5, which enables USB redirection (legacy mode) on Red Hat Enterprise Linux 5 clients.
|
Red Hat Enterprise Virt Agent (v.6 Server for x86_64)
|
rhel-x86_64-rhev-agent-6-server
| Provides the rhev-guest-agent, which allows you to monitor virtual machine resources. |
The Red Hat Subscription Manager (RHSM) provides packages necessary for installing Red Hat Enterprise Virtualization Manager and virtualization hosts. If you are using RHSM, you cannot use Red Hat Network Classic (RHN).
Table 1.5. Required Repositories for Red Hat Enterprise Virtualization Manager
|
Subscription pool
|
Repository name
|
Details
|
|---|---|---|
Red Hat Enterprise Linux Server
|
rhel-6-server-supplementary-rpms
|
Provides the Red Hat Enterprise Linux 6 Server.
|
Red Hat Enterprise Virtualization
|
rhel-6-server-rhevm-3.2-rpms
|
Provides the Red Hat Enterprise Virtualization Manager.
|
JBoss Enterprise Application Platform
|
jb-eap-6-for-rhel-6-server-rpms
| Provides the supported release of the JBoss application platform on which the Manager runs. |
Table 1.6. Required Pools for Red Hat Enterprise Virtualization Hypervisor
|
Subscription pool
|
Details
|
|---|---|
Red Hat Enterprise Virtualization
|
Provides the rhev-hypervisor package, which includes the image required to install the hypervisor.
|
Table 1.7. Required Pools for Red Hat Enterprise Linux Host
|
Subscription pool
|
Details
|
|---|---|
Red Hat Enterprise Linux Server
|
Provides the Red Hat Enterprise Linux 6 Server.
|
Red Hat Enterprise Virtualization Management Agents
|
Provides the QEMU and KVM packages required for using Red Hat Enterprise Linux servers as virtualization hosts.
|
Procedure 1.1. Subscribing to Red Hat Subscription Manager Pools
- To identify available subscription pools, run the command:
# subscription-manager list --available | grep -A8 "
subscription_pool"Use the subscription pool names listed in the three tables above to find the pool identifiers for Red Hat Enterprise Virtualization Manager, Red Hat Enterprise Virtualization Hypervisor, and Red Hat Enterprise Linux hosts respectively. - Using the pool identifiers provided from previous command, subscribe your systems to their respective entitlement pools.
# subscription-manager subscribe --pool=
subscription_pool_id - For Red Hat Enterprise Virtualization Manager only:Enable the software repositories listed in the "Required Repositories for Red Hat Enterprise Virtualization Manager" table.
# yum-config-manager --enable
repository_name
These administration portal features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- Pool virtual machine management, BZ#867308
- It is now possible to edit the name of a virtual machine that is part of a pool, overriding the automatic name given to the virtual machine when the pool was created.
- Editing shared disk interface, BZ#919683
- It is now possible to modify the interface type (IDE/VirtIO) of a shared disk that is attached to more than one virtual machine. Note that the change will apply for all virtual machines to which the disk is attached.
- Firefox 17 support, BZ#891877
- Mozilla Firefox 17 is now the only supported browser for accessing the administration and user portals on Red Hat Enterprise Linux clients.
- Improved disk search, BZ#855144
- It is now possible to search for disks by storage domain name using the following search string:
Disks: Storage.name =
storage_name - Internationalization, BZ#884825
- The Administration Portal has been localized. It is available in English, French, German, Spanish, Japanese, Simplified Chinese, and Brazilian Portuguese.
These infrastructure features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- Improved fencing proxy selection algorithm, BZ#747305
- Previously, the proxy for fencing operations was randomly selected from the available hosts in the data center. Now, users can set the priority for any host within the same cluster or data center to act as a fencing proxy. By default, a non-operational host will search for a proxy within its own cluster, and then within its data center.
- Multiple tier fencing, BZ#773108
- Two fencing devices can now be configured each host. Fencing devices can be of different types, as long as they are supported. Fencing agents can be used sequentially, meaning if the first agent fails the second is used; or concurrently, meaning that both devices must respond for the fencing operation to succeed.
- Virtual machine delete protection, BZ#871371
- A delete protection entity has been added for virtual machines and templates. When it is enabled in the web administration portal or REST API, the virtual machine or template cannot be deleted.
- Domain selection sequence, BZ#731763
- Previously options for domain selection in the user interfaces listed domains in the reverse of the order they were added with the most recently added domain was listed first. Now the domains are listed in natural sort order based on the name of the domain.
These developer features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- User application event logging, BZ#866123
- The REST API and SDK now include a set of API that allows users to inject events into the Red Hat Enterprise Virtualization Manager event log. This feature can be used by the API user to sync the logging of external events triggered by user applications into the event log.
- Simultaneous server connections, BZ#853947
- Scripts are now able to communicate with multiple Red Hat Enterprise Virtualization Managers by creating and manipulating separate instances of the ovirtsdk.API Python class.
- User Interface Plugins, BZ#885391
- Support has been added for extending the administration portal user interface with custom plugins. This includes a dedicated API for discovering and loading plugins, and providing notification of the plugin's key events to the administration portal.
These networking features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- Dynamically editing networks, BZ#604646
- Previously a logical network's properties could not be changed when its cluster was attached to a data center. In particular, this prevented users from changing the properties of the
rhevmmanagement network in the default data center, where the default cluster is always attached. Now, it is possible to edit networks when they are attached to clusters, and when there are hosts in the cluster, as long as the network is not in use by any host in the cluster. - Dynamically editing networks, BZ#909820
- It is now possible to edit networks when they are assigned to hosts, and then re-sync the networks with their attached hosts after the network properties have been updated.
- Network linking, BZ#840692
- Red Hat Enterprise Virtualization now supports network linking, which allows users to make changes to a virtual network interface without unplugging it, thus maintaining its PCI address. Users can now dynamically change the logical network for a running virtual machine, and disconnect the network interface from the logical network while the network interface is still plugged to the virtual machine.
- New network tab, BZ#858742
- A new Network tab has been added to the main resource tabs, and a Networks entry has been added to the Tree pane in the administration portal. This provides a central location for users to perform network-related operations and search for networks based on each network's property or association with other resources.
- Enhanced IP address display, BZ#668239
- Previously, the IP addresses of virtual machines were displayed, but they were not directly mapped to each individual network interface. Now, when the Guest Agent is installed on a virtual machine, its IP addresses are displayed per network interface on the virtual machine's Network Interfaces tab.
- Enhanced IPv6 address display, BZ#800286
- IPv6 addresses within a virtual machine are now reported per virtual network interface, which is the same behaviour for reporting IPv4 addresses. IP addresses are reported when the Guest Agent is installed on the virtual machine.
These storage features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- Storage live migration
- Storage live migration, which was offered as a technology preview in version 3.1, is now officially supported. This feature allows the migration of running virtual machines and disks from one storage domain to another.
- Automated clone virtual machine from snapshot, BZ#909359
- It is now possible to clone virtual machines from snapshots using the rhevm-shell. You can now use an automated procedure to create copies of a virtual machine as it was when the snapshot was taken.
- Removing virtual machines without removing disks, BZ#881024
- It is now possible to remove a virtual machine without removing its disk. This replaces the previous behavior where removing a virtual machine forced the removal of its disk, or detaching the disk in a separate action if the disk was to be retained.
- Finding and registering storage disks, BZ#886133
- The REST API can be used to check a storage domain for disk images that exist on it and are not registered to the Red Hat Enterprise Virtualization Manager's database.These disk images can be found by issuing the following GET request:
http://
<rhevm-engine>:8700/api/storagedomains/<storage domain id>/disks;unregisteredThese disk images can also be registered by issuing a POST request:http://
<rhevm-engine>:8700/api/storagedomains/<storage domain id>/disks;unregistered <disk id="..."> <alias>myAlias</alias> </disk> - New Disks tab, BZ#881024
- A new Disks tab has been added under the Storage resource tab. This tab lists the disks associated with each storage domain, and simplifies disk management operations such as storage domain detachment.
- Concurrent disk live migration, BZ#874080
- It is now possible to live migrate multiple disks concurrently. Users can now move multiple disks between storage domains while the virtual machine is running.
- Support for names with special characters, BZ#876575
- The LVM filter implemented in VDSM now supports device names with udev special characters, including hyphens (-), underscores (_), and spaces ( ). Users can now create storage domains and LUNs with unicode characters in their names.
- Integrated Red Hat Storage Management (Technology Preview)
- Initial support for managing Red Hat Storage volumes and bricks using Red Hat Enterprise Virtualization Manager is offered as a technology preview.
These user portal features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- Quota Management Support, BZ#876903
- Quota information has been added to the Resources pane in the power user portal, so users can monitor vCPU, memory, and storage consumption, and available resources. This function is offered as a technology preview.
- Internationalization, BZ#884825
- The User Portal has been localized. It is available in English, French, German, Spanish, Japanese, Simplified Chinese, and Brazilian Portuguese.
These VDI features have been added for the release of Red Hat Enterprise Virtualization 3.2:
- SPICE arbitrary resolution, BZ#894345
- SPICE arbitrary resolution support has been added for Red Hat Enterprise Linux 6.4 guests and Windows guests running on Red Hat Enterprise Linux hosts. This feature allows users to adjust the SPICE display window to fit exactly to the client window of any size.
- SPICE seamless migration support, BZ#894020
- Seamless migration of SPICE sessions is now supported for virtual machines when both the source and target hosts are based on Red Hat Enterprise Linux 6.4. This feature allows ongoing USB, virtual desktop agent, and smartcard data transfers between the server and the client to be continued smoothly after migration, with no data loss.
- Proxy support for SPICE client, BZ#893090
- HTTP proxy support is now available for SPICE clients connecting to virtual machines from outside the host's network. The SPICE client can establish a connection to a remote host through the proxy specified by the environment variable SPICE_PROXY=host:port, or via the controller.
You must take these recommended practices into account to ensure the best possible outcomes for your Red Hat Enterprise Virtualization environment.
- BZ#837665
Previously, VDSM only reported physical cores by default. An update allowed users to manually force VDSM to report threads instead of physical cores. Now, clusters can be configured to treat host CPU threads as cores for the purposes of virtual machine resource allocation and migration. Users who had previously forced VDSM to report threads should revert to the configuration of reporting physical cores. If VDSM only reports physical cores, Red Hat Enterprise Virtualization Manager will assume hyperthreading is disabled on the hosts in the cluster, and thus not allow host memory optimization.
- BZ#844429
When making configuration changes using the rhevm-config tool it is necessary to restart the ovirt-engine service before they will take effect. Additionally changes to values that are cached on the client side require a restart of the client browser to clear cached values before they will take effect.
- BZ#919857
The Force Remove data center option should only be used after the storage is no longer needed or has been destroyed. If you have leftover data on the storage, manually remove any files under
/rhev/data-center, and unmount any mount points that exist there.- BZ#922358
Internet Explorer 8 treats the
<iframe src="javascript:''" ...>tag as a non-secure item, which causes a Mixed Content pop-up warning, and a delay in installing SPICE ActiveX plugins on the user portal. To prevent this behavior, configure Internet Explorer 8 to suppress mixed content warnings using the → . See http://msdn.microsoft.com/en-us/library/ee264315(v=vs.85).aspx for details.- BZ#960581
If you are using the JBoss Application Server from JBoss Enterprise Application Platform 6.0.1, upgrading the Red Hat Enterprise Virtualization Manager will not automatically update the application server to EAP 6.1. Although Red Hat Enterprise Virtualization Manager supports EAP 6.0.1, it is recommended to update to the latest supported JBoss version. To upgrade to JBoss EAP 6.1, see https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html/Installation_Guide/Upgrade_the_JBoss_Enterprise_Application_Platform_6_RPM_Installation.html.
These known issues exist in Red Hat Enterprise Virtualization 3.2 at this time:
Administration Portal
- BZ#868694
Due to the performance constraints imposed by the JavaScript engine included in Internet Explorer 8 it is not a supported client for the new Administration Portal user interface. Later versions of Internet Explorer remain supported.
- BZ#881392
The Always use the cursor keys to navigate within pages Firefox option does not work as expected for keyboard-triggered functions in the administration portal, for example when using arrow keys to select items in the Search bar. This option is disabled by default, and it is recommended to keep it that way. More information on this Firefox option can be found at http://support.mozilla.org/en-US/kb/accessibility-features-firefox-make-firefox-and-we#w_always-use-the-cursor-keys-to-navigate-within-webpages.
Hypervisor
- BZ#920671
After a Red Hat Enterprise Virtualization Hypervisor is attached to the Red Hat Enterprise Virtualization Manager and then successfully upgraded, it may erroneously appear in the administration portal with the status of Install Failed. Click on the button, and the hypervisor will change to an Up status and be ready for use.
Infrastructure
- BZ#877737
Importing diskless virtual machines or templates will fail, or be imported without peripheral device such as network devices. To work around this issue, redefine diskless virtual machines or templates in the destination. Do not use the export and import process.
- BZ#967861
Previously, the time zone for a Red Hat Enterprise Linux virtual machine could be set in the Initial Run tab of the New or Edit Virtual Machine window. Now, the default time zone which is Etc/GMT is used, and it cannot be changed via the administration portal. After an upgrade, the time zones of all Red Hat Enterprise Linux virtual machines are reset to Etc/GMT. If you are using a Linux virtual machine with a non-default time zone, adjust the machine's hardware clock to your desired time zone.
Quota
- BZ#917387
When moving a disk between two storage domains with different quotas (or the same quota set for each specific storage domain) the source quota resources are released while the destination quota resources are consumed. If the quota is refreshed or edited, or if the engine is restarted, the quota accounting is rolled back until the move operation is done. This function is offered as a technology preview.
Reporting
- BZ#913384
Upgrading the rhevm-dwh package produces an error which prevents the database warehouse service from starting. To work around this issue, turn off the rhevm-dwhd service before upgrading, then start it after the upgrade has completed.
REST API
- BZ#961229
The
--storage_formatoption is an accepted argument for theadd storagedomaincommand, even though it does not appear in the list of available options.- BZ#961371
The
--parent-tag-idand--parent-tag-nameoptions are accepted arguments for theadd tagcommand, even though they do not appear in the list of available options.- BZ#962276
The
--formatoption must be passed for the storage domain to be removed, however theremove storagedomaincommand does not list the--formatoption as a required argument.
Storage
- BZ#920575
A Red Hat Enterprise Virtualization 3.1 data center containing both Gluster-enabled clusters and virtualization host clusters cannot be upgraded to Red Hat Enterprise Virtualization 3.2. Currently, Red Hat Enterprise Virtualization 3.2 is not compatible with Red Hat Storage 2.0, so Gluster clusters can only be used with 3.1-compatible data centers.
User Portal
- BZ#905898
A new native multiple monitor feature using a single QXL device for Red Hat Enterprise Linux virtual machines is included in the latest version of mingw-virt-viewer available in Red Hat Enterprise Virtualization 3.2. However, on Red Hat Enterprise Linux virtual machines multiple QXL devices are still created with not enough memory for a single QXL device, which can cause the multi-monitor feature to misbehave. To work around this issue, do not enable native multi-monitor support on your Linux virtual machines until this issue is fixed. Instead, use the Xinerama Xorg extension to manage Red Hat Enterprise Linux virtual machines with multi-monitor enabled.
These issues are now resolved in Red Hat Enterprise Virtualization 3.2:
- BZ#856605
Previously, when using the new Native USB Policy mode, connected USB devices were always shared regardless of whether the Enable USB Auto-Share option was selected. This issue has been resolved, and USB devices are correctly shared according to their setting in the Enable USB Auto-Share field.
- BZ#854972
Previously when VDSM attempted to run getFloppyList on an NFSv4 storage domain an error was returned if the permissions of the NFS export were not set correctly, or if the VDSM host was in a different NFS domain to the storage server. This has now been fixed, and the getFloppyList command succeeds as expected.
- BZ#865021
Previously, it was possible to move a virtual machine disk with a snapshot in preview mode, which caused a vdsm error, so the virtual machine could not run until the preview was reverted. An additional validation has been added to MoveDisksCommand to prevent such action.
- BZ#871481
Previously, the vdsmd service could be restarted by the spmprotect script, which triggered an attempt to restore the host network configuration to its last known safe state. If the host lost its Storage Pool Manager role, it would lose its current network connectivity. Now, the host network configuration is only restored on boot time, not when the vdsmd service is restarted. As a result, the
service vdsmd restartcommand does not adversely affect host networking.- BZ#856737
Previously, VDSM did not report errors to the Manager if the
ifupscript failed, for example when another host on the LAN has the same IP address. Now,ifuphas to execute successfully for thesetupNetworkcommand to succeed, otherwise VDSM reports the failure to the Manager.- BZ#873338
If a virtual machine had a different number of network interfaces in normal mode and in snapshot preview mode, unused MAC addresses in either mode would be released to the pool. This meant that the same MAC address could potentially be assigned to network interfaces belonging to different virtual machines. With this update, a check is performed when a network interface is being plugged to ensure that it is not assigned an already used MAC address.
- BZ#872506
Disk alias are mandatory on Red Hat Enterprise Virtualization Manager in order to run virtual machines, but they are not mandatory in the OVF format. Now, aliases are auto-generated for disks imported from an OVF that does not contain aliases, so virtual machines imported from other sources can successfully run on Red Hat Enterprise Virtualization Manager.
- BZ#882616
Aliases for disks imported from OVFs were not generated correctly, as the disks were given identical names. Now, each disk is given a name and a number in ascending order. For example, the aliases generated for three disks belonging to virtual machine
VmNameareVmName_Disk1,VmName_Disk2, andVmName_Disk3.- BZ#848806
Previously, the administration portal took several seconds to reflect changes to a virtual machine's disk properties. Now, the virtual machine's Disks tab is refreshed immediately the disk's properties are edited.- BZ#885452
Previously, virtual machine which contained shareable disks could not be exported because the export command did not recognise shared disks. The export command now accounts for shared disks, so virtual machines with shared disks are exported successfully.
- BZ#808998
To create a Fibre Channel storage domain on a CCISS device, a scsi_disk path was used to retrieve Host, Bus, Target, Lun (HBTL) values which did not exist on CCISS devices. Consequently, the storage domain could not be created. Now, the HBTL value is not required for non-SCSI devices, so creating a storage domain on a CCISS device succeeds.
- BZ#883390
When a Fibre Channel storage domain was created from a host that was not the Storage Pool Manager (SPM), the SPM failed to recognise the storage domain and could not attach it. Now, when the domain cannot be attached, the SPM scans for new domains and retries to attach the domain until it succeeds.
- BZ#748386
Previously,
ddwas used to export virtual machines with snapshots, so the image size on the export domain was larger than the original image. Now,qemu-imgconvert is used to copy a RAW volume from the source domain to the destination domain, therefore the exported image remains sparse.- BZ#907255
Previously, when an ISO domain lost SPM connectivity, the connection to the ISO domain could not be restored even though the mount point was available. A patch to VDSM ensures that the ISO domains are autorecovered after their connectivity is restored.
- BZ#886842
Previously, removing a file storage domain did not remove its lease files, so the virtual machines on the storage domain could not be deleted. Now, VDSM renames the lease files when a storage domain is removed, so its virtual machines can be deleted.
- BZ#905831
Previously, users could set the Do Not Migrate parameter on a virtual machine without defining a specific host to run the virtual machine, so the virtual machine could still be migrated. Now, when these conditions are met, the virtual machine's CPU will be pinned on the first host on which it runs. The virtual machine will not be migrated to other hosts.- BZ#894687
Previously the web browser sent HTTP Authorization headers for all requests to a given origin after the header has already been set for the initial request. This meant the user interface plugin infrastructure acquired a REST API session using web administration portal user credentials including domain and password information, and the session was kept alive until the user signed out of the administration portal. To work around this issue, all user interface plugins now receive a single shared session ID based on the web administration portal user login credentials. This session times out after six hours, and the administration portal will not attempt to keep this session alive using periodic heartbeat requests. The plugin is in charge of keeping its session alive, and if no plugin interacts with the REST API session via the provided ID for more than six hours, the session will time out.
Administrators can receive the latest security advisories from the Red Hat Enterprise Virtualization watch list. Subscribe to the Red Hat Enterprise Virtualization watch list to receive new security advisories for Red Hat Enterprise Virtualization products by email. Subscribe by completing this form: http://www.redhat.com/mailman/listinfo/rhev-watch-list/.
| Revision History | |||
|---|---|---|---|
| Revision 3.0.0-4.400 | 2013-10-31 | ||
| |||
| Revision 3.0.0-4 | Tue 6 Aug 2013 | ||
| |||
| Revision 3.0.0-3 | Tue 25 June 2013 | ||
| |||
| Revision 3.0.0-2 | Mon 24 June 2013 | ||
| |||
| Revision 3.0.0-1 | Fri 7 June 2013 | ||
| |||
| Revision 2.0.0-3 | Tue 23 Apr 2013 | ||
| |||
| Revision 1.0.0-7 | Tue 26 Mar 2013 | ||
| |||