Virtual Machine Issues
Snapshots of KVM Guests Using TPM Fail if Save Memory Option is Enabled
If you have virtual machines with UEFI and TPM (Trusted Platform Module) enabled and attempt to create snapshots using the Save Memory option enabled, you get an error:
Cannot create Snapshot. VM has a TPM device attached.
Solution: If you don't need the TPM functionality for the snapshot, consider temporarily disabling the TPM device before creating the snapshot or do not use the Save Memory option.
Bug: 37603737
Virtual Machine Does Not Boot with Allow Privileged SCSI I/O Option Enabled
If you have configured a virtual machine on Oracle Linux 7.7 with a physical LUN and the Allow Privileged SCSI I/O option enabled, the virtual machine does not boot and reports an error:
libvirtError: Requested operation is not valid: unpriv_sgio is not supported
by this kernel
Solution: Do not use the Allow Privileged SCSI I/O option if your virtual machine has access to a physical LUN.
Bug: 31021044
Virtual Machines Not Migrated As Expected Through Virtual Machine Affinity and Host Affinity Rules Set to Active and Enforcing
In a 2-host cluster where 4 virtual machines are running on one of the hosts, a Vm Affinity Rule and a Host Affinity Rule are set on the Manager to Active and Enforcing. These rules, however, are not applied correctly because the virtual machines defined in the affinity group should have migrated to the other host; instead, the other KVM host is filtered out in this scenario.
Solution: Enabling the VM Affinity Rule or the Host Affinity Rule Enforcing option imposes strict limits on whether virtual machines can start or be migrated. With VM Affinity Rule Enforcing enabled (shown as Hard in the list of Affinity Groups), the system does not migrate a virtual machine to a host different from where the other virtual machines in its affinity group are running, even if attempting to satisfy a Host Affinity Rule that only permits the virtual machines to run on a host other than where they are presently running.
The workaround for both VM and Host affinity rules is to not enable enforcing unless all scenarios including migration scenarios are understood. The rules are not disabled if you do not select the Enforcing option; it changes the enforcement from Hard to Soft, permitting the system to temporarily break the rule as adjustments in virtual machine placement are made.
Bug: 29190112
Changing Watchdog Actions on a Running Virtual Machine Requires a Virtual Machine Restart for New Attribute to Take Effect
action
attribute to reset
, the virtual machine is restarted. Changing the watchdog action
to a different attribute, such as poweroff
, causes the Pending Virtual Machine Changes window to open with the following message: Changes that require Virtual Machine restart: watchdog. The VM is then restarted.
The issue is that even though watchdog action
is changed to poweroff
, the attribute value did not take effect immediately. The virtual machine must first be restarted before the new attribute takes effect.
Solution: There is no workaround for this behavior. If a watchdog action is changed on a running virtual machine, you must restart the virtual machine for the attribute changes to take effect.
Bug: 29213956
Guest Agent Hooks Do Not Work If a Migration Policy Is Set to Legacy
The guest agent hooks do not work for migration policies that are set to Legacy.
Solution:This behavior is expected, as the guest hooks are enabled depending on the migration policy that is configured, and the guest agent hook mechanism is disabled for migration policies set to Legacy. To use guest agent hooks, you must use one of the other available migration policy types.
Bug: 29261746
Importing Several OVA Files Resulted in Only One Virtual Machine Being Imported
When importing virtual machines, multiple OVA files can be selected, but only one virtual machine is actually imported. If there is a limitation, the Manager should block attempts to import multiple OVA files.
Solution: There is no workaround for this behavior.
Bug: 29373795
High-Availability Virtual Machines Fail to Restart After Restarting KVM Host
High-availability virtual machines fail to restart after the KVM host is restarted on the Manager.
Solution: There is no workaround for this behavior. The KVM host eventually starts up several minutes later.
Bug: 29393228
Migration Mode Greyed Out When Setting Pinning-to-Host Setting for a Virtual Machine
This issue is observed in a 2-host cluster. The steps to reproduce the issue are as follows:
- Edit a virtual machine by selecting the Highly Available checkbox on the High Availability tab, and click OK.
-
Edit the virtual machine and update the pinning-to-host settings by selecting Specific Hosts and adding the two hosts from the drop-down list on the Host tab, and click OK.
After doing completing these steps, the Migration Mode drop-down list is greyed out. This option should be available in this scenario.
Solution: Try changing the pinning-to-host option to Any Host in Cluster and then change the setting back to Specific Hosts again.
Bug: 29374044
Cannot Assign Virtual Machine from a Virtual Machine Pool: Manager Claims That the Virtual Machine Is Attached When It Is Not
10
, and granting permissions to a user, the user correctly attaches some virtual machines. Later the user tries to attach more virtual machines, but the Manager generates the following error, indicating that virtual machines are already attached when they are not: PoolName:
Cannot attach VM to VM-Pool. VM-Pool is already attached to a User.
Cannot allocate and run VM from VM-Pool. There are no available VMs in the VM-Pool.
Solution: A known issue in the upstream oVirt release. There is no workaround for this behavior.
Bug: 29379502
Manager Does Not Generate a Warning Message to Prevent OVA Export from a Virtual Machine Whose Guest OS Is Installed on a Direct LUN Disk
The Manager does not generate an warning message that prevents OVA export from a virtual machine whose guest OS is installed on a direct LUN disk.
Solution: There is no workaround for this behavior.
Bug: 29432214
Manager Allows OVA Export from a Virtual Machine Whose Guest OS Is Installed on a Direct LUN Disk
The Manager allows OVA export from a virtual machine whose guest OS is installed on a direct LUN disk. The Manager should prevent attempts to export an OVA from a virtual machine whose guest OS is installed on a direct LUN disk image.
Solution: There is no workaround for this behavior.
Bug: 29432323
Manager Does Not Prevent Virtual Machine Shutdown When Creating a Snapshot
The Manager does not prevent a virtual machine from being shutdown when creating a snapshot, thereby causing the snapshot to hang. In this situation, the virtual machine cannot be started or removed and the creation of the snapshot cannon be stopped.
When inspecting the Manager log, the follow message is seen repeatedly:
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback]
(EE-ManagedThreadFactory-engineScheduled-Thread-34)
[7363ae20-1f20-451c-8318-215f122fcc15] Command 'CreateSnapshotForVm' (id:
'b50fee33-204b-4fc0-a8e6-d40c7f58d485') waiting on child command id:
'3c843771-8b8f-4c07-9230-822bd2892481' type:'AddDisk' to complete
2019-03-08 03:55:22,992Z INFO
Solution: There is no workaround for this behavior.
Bug: 29457750
Engine Exception When Unplugging a NIC Connected to a Virtual Machine Network on a Running Virtual Machine
Unplugging a NIC that is connected to a VM network on a running virtual machine may fail on the Manager with the following Operation Canceled message:
Error while executing action Edit VM Interface properties: Failed to deactivate
VM Network Interface.
When inspecting the Manager log, you may see the following EngineException:
EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException:
VDSGenericException: VDSErrorException: Failed to HotUnplugNicVDS, error =
Timeout detaching <Interface name=vnet3, type=bridge, mac=00:21:f6:00:04:6b
at 0x7f6d30377868>, code = 50 (Failed with error DEACTIVATE_NIC_FAILED and
code 50)
Solution: Try unplugging the NIC again.
Bug: 29460927
Highly Available Virtual Machine Not Started on Other Host When Source Host Dies Unexpectedly
Highly available virtual machines are not started on the other host when the source host is powered off or dies unexpectedly.
Solution: If a host that has running highly available virtual machines is powered off or dies unexpectedly and the virtual machines do not have additional split-brain prevention mechanisms in place (such as Sanlock, VM leases, or VM resume), you may be required to use the Confirm 'Host has been Rebooted' option from the More Actions drop-down list on the Hosts pane before the Manager allows the highly available virtual machines on the host to be restarted on the other host.
Bug: 29491043
VNC Console Session for a Running Virtual Machine Closes During Virtual Machine Migration
If you have an VNC console open for an active virtual machine during virtual machine migration, the session closes. This behavior occurs when using either the native client or noVNC.
Solution: There is no workaround for this behavior.
Bug: 29491251
Migrate VM Dialog Box Cannot Be Closed While a Virtual Machine Is Being Started
The Migrate VM dialog box cannot be closed while a virtual machine is being started in the Manager.
Solution: Refresh the browser page.
Bug: 29498386
Unable to Perform CPU Hot Unplug with Default Machine Type (pc-i440fx-2.6) for Oracle Linux Virtual Machine
The CPU hot unplug feature on the Manager is not working with the default emulated machine type for Oracle Linux virtual machines (pc-i440fx-2.6
).
Solution: To enable CPU hot unplug feature for a particular Oracle Linux virtual machine, you must perform the following steps:
- Shutdown the virtual machine.
-
Change the Custom Emulated Machine to
pc-i440fx-2.7
by performing the following steps in the Administration Portal:- Go to Compute and click Virtual Machines.
- Select the Oracle Linux virtual machine and click Edit Virtual Machine.
- Click the System tab on the sidebar.
- Click Advanced Parameters to expand the menu.
- On the Custom Emulated Machine drop-down menu, select
pc-i440fx-2.7
. - Click OK to save your changes.
- Restart the virtual machine.
Bug: 29517731
Cannot Import OVA Files That Contain More Than 1 Virtual Machine
If an Open Virtualization Appliance file contains more than one virtual machine, then the virtual machines in the file cannot be imported. The import begins and appears to import the first virtual machine, but then the import fails and no virtual machine are installed successfully.
Solution: Restrict Open Virtualization Appliance files to one virtual machine.
Bug: 30771759