Red hat virtio scsi controller driver windows

1.4.1. Installing Console Components

2.2.1. Starting a Virtual Machine

Procedure

1. Click → and select a virtual machine with a status of Down.
2. Click Run.

A virtual machine will not start on a host with an overloaded CPU. By default, a host’s CPU is considered overloaded if it has a load of more than 80% for 5 minutes, but these values can be changed using scheduling policies. See Scheduling Policies in the Administration Guide for more information.

Troubleshooting

Scenario — the virtual machine fails to boot with the following error message:

• Make sure that hard disk is selected in the boot sequence, and the disk that the virtual machine is booting from must be set as Bootable.
• Create a Cloned Virtual Machine Based on a Template.
• Create a new virtual machine with a local boot disk managed by RHV that contains the OS and application binaries.
• Install the OS by booting from the Network (PXE) boot option.

1. Create or edit the /var/lib/obmc/cfam_overrides on the BMC.

2. Set the firmware risk level to 0:

   # Control speculative execution mode
   0 0x283a 0x00000000  # bits 28:31 are used for init level -- in this case 0 Kernel and User protection (safest, default)
   0 0x283F 0x20000000  # Indicate override register is valid

3. Reboot the host system for the changes to take affect.

Overriding the risk level can cause unexpected behavior when running virtual machines.

2.2.2. Opening a console to a virtual machine

To allow other users to connect to the VM, make sure you shutdown and restart the virtual machine when you are finished using the console. Alternatively, the administrator can Disable strict user checking to eliminate the need for reboot between users. See Virtual Machine Console Settings Explained for more information.

Procedure

1. Install Remote Viewer if it is not already installed. See Installing Console Components.
2. Click → and select a virtual machine.
3. Click Console. By default, the browser prompts you to download a file named console.vv. When you click to open the file, a console window opens for the virtual machine. You can configure your browser to automatically open these files, such that clicking Console simply opens the console.

console.vv expires after 120 seconds. If more than 120 seconds elapse between the time the file is downloaded and the time that you open the file, click Console again.

2.2.3. Opening a Serial Console to a Virtual Machine

To access the serial console of a virtual machine, the user must have UserVmManager, SuperUser, or UserInstanceManager permission on that virtual machine. These permissions must be explicitly defined for each user. It is not enough to assign these permissions to Everyone.

• Rule «M3» for the Manager firewall
• Rule «H2» for the host firewall

1. On the virtual machine whose serial console you are accessing, add the following lines to /etc/default/grub:

   GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200n8"
   GRUB_TERMINAL="console serial"
   GRUB_SERIAL_COMMAND="serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1"

   GRUB_CMDLINE_LINUX_DEFAULT applies this configuration only to the default menu entry. Use GRUB_CMDLINE_LINUX to apply the configuration to all the menu entries.

   If these lines already exist in /etc/default/grub, update them. Do not duplicate them.

2. Rebuild /boot/grub2/grub.cfg:

   • BIOS-based machines:

     # grub2-mkconfig -o /boot/grub2/grub.cfg

   • UEFI-based machines:

     # grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg

     See GRUB 2 over a Serial Console in the Red Hat Enterprise Linux 7 System Administrator’s Guide for details.

3. On the client machine from which you are accessing the virtual machine serial console, generate an SSH key pair. The Manager supports standard SSH key types, for example, an RSA key:

   # ssh-keygen -t rsa -b 2048 -f .ssh/serialconsolekey

   This command generates a public key and a private key.

4. In the Administration Portal or the VM Portal, click the name of the signed-in user on the header bar and click Options. This opens the Edit Options window.
5. In the User’s Public Key text field, paste the public key of the client machine that will be used to access the serial console.
6. Click → and select a virtual machine.
7. Click Edit.
8. In the Console tab of the Edit Virtual Machine window, select the Enable VirtIO serial console check box.

• If a single virtual machine is available, this command connects the user to that virtual machine:

  # ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN -i .ssh/serialconsolekey
  Red Hat Enterprise Linux Server release 6.7 (Santiago)
  Kernel 2.6.32-573.3.1.el6.x86_64 on an x86_64
  USER login:

• If more than one virtual machine is available, this command lists the available virtual machines and their IDs:

  # ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN -i .ssh/serialconsolekey list
  1. vm1 [vmid1]
  2. vm2 [vmid2]
  3. vm3 [vmid3]
  > 2
  Red Hat Enterprise Linux Server release 6.7 (Santiago)
  Kernel 2.6.32-573.3.1.el6.x86_64 on an x86_64
  USER login:

  Enter the number of the machine to which you want to connect, and press Enter.

• Alternatively, connect directly to a virtual machine using its unique identifier or its name:

  # ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN connect --vm-id vmid1

  # ssh -t -p 2222 ovirt-vmconsole@Manager_FQDN connect --vm-name vm1

2.2.4. Automatically Connecting to a Virtual Machine

Procedure

1. In the Virtual Machines page, click the name of the virtual machine to go to the details view.
2. Click the pencil icon beside Console and set Connect automatically to ON.

2.4.1. Red Hat Virtualization Guest agents, tools, and drivers

• Resource usage
• IP addresses

Table 2.1. Red Hat Virtualization Guest drivers

Table 2.2. Red Hat Virtualization Guest agents and tools

2.4.2. Installing the Guest Agents and Drivers on Red Hat Enterprise Linux

Red Hat Enterprise Linux 8 virtual machines use the qemu-guest-agent service, which is installed and enabled by default, instead of the ovirt-guest-agent service. If you need to manually install the guest agent on RHEL 8, follow the procedure below.

Procedure

1. Log in to the Red Hat Enterprise Linux virtual machine.

2. Enable the Red Hat Virtualization Agent repository:

   • For Red Hat Enterprise Linux 6

     # subscription-manager repos --enable=rhel-6-server-rhv-4-agent-rpms

   • For Red Hat Enterprise Linux 7

     # subscription-manager repos --enable=rhel-7-server-rh-common-rpms

   • For Red Hat Enterprise Linux 8

     # subscription-manager repos --enable=rhel-8-for-x86_64-appstream-rpms

3. Install the guest agent and dependencies:

   • For Red Hat Enterprise Linux 6 or 7, install the ovirt guest agent:

     # yum install ovirt-guest-agent-common

   • For Red Hat Enterprise Linux 8 and 9, install the qemu guest agent:

     # yum install qemu-guest-agent

4. Start and enable the ovirt-guest-agent service:

   • For Red Hat Enterprise Linux 6

     # service ovirt-guest-agent start
     # chkconfig ovirt-guest-agent on

   • For Red Hat Enterprise Linux 7

     # systemctl start ovirt-guest-agent
     # systemctl enable ovirt-guest-agent

5. Start and enable the qemu-guest-agent service:

   • For Red Hat Enterprise Linux 6

     # service qemu-ga start
     # chkconfig qemu-ga on

   • For Red Hat Enterprise Linux 7, 8 or 9

     # systemctl start qemu-guest-agent
     # systemctl enable qemu-guest-agent

3.2.1. Installing Windows on VirtIO-optimized hardware

Prerequisites

The following items have been added to the virtual machine:

• a Red Hat VirtIO network interface.
• a disk that uses the VirtIO interface. This disk can be on a

Red Hat recommends uploading ISO images to the data domain with the Administration Portal or with the REST API. For more information, see Uploading Images to a Data Storage Domain in the Administration Guide.

If necessary, you can upload the virtio-win ISO file to an ISO storage domain that is hosted on the Manager. The ISO storage domain type is deprecated. For more information, see Uploading images to an ISO domain in the Administration Guide.

Procedure

To install the virtio-win drivers when installing Windows, complete the following steps:

1. Click → and select a virtual machine.
2. Click → .
3. Expand the Boot Options menu.
4. Select the Attach CD check box, and select a Windows ISO from the drop-down list.
5. Select the Attach Windows guest tools CD check box.
6. Move CD-ROM to the top of the Boot Sequence field.
7. Configure other Run Once options as required. See Virtual Machine Run Once settings explained for more details.

8. Click OK. The status of the virtual machine changes to Up, and the operating system installation begins.

   Open a console to the virtual machine if one does not open automatically during the Windows installation.

9. When prompted to select a drive onto which you want to install Windows, click Load driver and OK.
10. Under Select the driver to install, select the appropriate driver for the version of Windows. For example, for Windows Server 2019, select Red Hat VirtIO SCSI controller (E:amd642k19viostor.inf)
11. Click Next.

3.2.2. Opening a console to a virtual machine

To allow other users to connect to the VM, make sure you shutdown and restart the virtual machine when you are finished using the console. Alternatively, the administrator can Disable strict user checking to eliminate the need for reboot between users. See Virtual Machine Console Settings Explained for more information.

Procedure

1. Install Remote Viewer if it is not already installed. See Installing Console Components.
2. Click → and select a virtual machine.
3. Click Console. By default, the browser prompts you to download a file named console.vv. When you click to open the file, a console window opens for the virtual machine. You can configure your browser to automatically open these files, such that clicking Console simply opens the console.

console.vv expires after 120 seconds. If more than 120 seconds elapse between the time the file is downloaded and the time that you open the file, click Console again.

3.3.1. Red Hat Virtualization Guest agents, tools, and drivers

• Resource usage
• IP addresses

Table 3.1. Red Hat Virtualization Guest drivers

Table 3.2. Red Hat Virtualization Guest agents and tools

3.3.2. Installing the guest agents, tools, and drivers on Windows

Procedure

To install the guest agents, tools, and drivers on a Windows virtual machine, complete the following steps:

1. On the Manager machine, install the virtio-win package:

   # dnf install virtio-win*

   After you install the package, the ISO file is located in /usr/share/virtio-win/virtio-win_version.iso on the Manager machine.

2. Upload virtio-win_version.iso to a data storage domain. See Uploading Images to a Data Storage Domain in the Administration Guide for details.
3. In the Administration or VM Portal, if the virtual machine is running, use the Change CD button to attach the virtio-win_version.iso file to each of your virtual machines. If the virtual machine is powered off, click the Run Once button and attach the ISO as a CD.
4. Log in to the virtual machine.
5. Select the CD Drive containing the virtio-win_version.iso file. You can complete the installation with either the GUI or the command line.

6. Run the installer.

   To install with the GUI, complete the following steps

   1. Double-click virtio-win-guest-tools.exe.
   2. Click Next at the welcome screen.
   3. Follow the prompts in the installation wizard.
   4. When installation is complete, select Yes, I want to restart my computer now and click Finish to apply the changes.

   To install silently with the command line, complete the following steps

   1. Open a command prompt with Administrator privileges.

   2. Enter the msiexec command:

      D: msiexec /i "PATH_TO_MSI" /qn [/l*v "PATH_TO_LOG"][/norestart] ADDLOCAL=ALL

      Other possible values for ADDLOCAL are listed below.

      For example, to run the installation when virtio-win-gt-x64.msi is on the D: drive, without saving the log, and then immediately restart the virtual machine, enter the following command:

      D: msiexec /i "virtio-win-gt-x64.msi" /qn ADDLOCAL=ALL

3.3.3. Values for ADDLOCAL to customize virtio-win command-line installation

Table 3.3. Possible values for ADDLOCAL to install drivers

Table 3.4. Possible values for ADDLOCAL to install agents and required corresponding drivers

Examples

The following command installs only the VirtIO SCSI pass-through controller, the VirtIO Serial device driver, and the VirtIO Block driver:

• Windows Installer
• Command-Line Options for the Windows installer
• Property Reference for the Windows installer

4.2.1. Configuring Single Sign-On for Red Hat Enterprise Linux Virtual Machines Using IPA (IdM)

The following procedure assumes that you have a working IPA configuration and that the IPA domain is already joined to the Manager. You must also ensure that the clocks on the Manager, the virtual machine and the system on which IPA (IdM) is hosted are synchronized using NTP.

Single sign-on with IPA (IdM) is deprecated for virtual machines running Red Hat Enterprise Linux version 7 or earlier and unsupported for virtual machines running Red Hat Enterprise Linux 8 or Windows operating systems.

1. Log in to the Red Hat Enterprise Linux virtual machine.

2. Enable the repository:

   • For Red Hat Enterprise Linux 6:

     # subscription-manager repos --enable=rhel-6-server-rhv-4-agent-rpms

   • For Red Hat Enterprise Linux 7:

     # subscription-manager repos --enable=rhel-7-server-rh-common-rpms

3. Download and install the guest agent, single sign-on, and IPA packages:

   # yum install ovirt-guest-agent-common ovirt-guest-agent-pam-module ovirt-guest-agent-gdm-plugin ipa-client

4. Run the following command and follow the prompts to configure ipa-client and join the virtual machine to the domain:

   # ipa-client-install --permit --mkhomedir

   In environments that use DNS obfuscation, this command should be:

   # ipa-client-install --domain=FQDN --server=FQDN

5. For Red Hat Enterprise Linux 7.2 and later:

   # authconfig --enablenis --update

   Red Hat Enterprise Linux 7.2 has a new version of the System Security Services Daemon (SSSD), which introduces configuration that is incompatible with the Red Hat Virtualization Manager guest agent single sign-on implementation. This command ensures that single sign-on works.

6. Fetch the details of an IPA user:

   # getent passwd ipa-user

7. Record the IPA user’s UID and GID:

   ipa-user:*:936600010:936600001::/home/ipa-user:/bin/sh

8. Create a home directory for the IPA user:

   # mkdir /home/ipa-user

9. Assign ownership of the directory to the IPA user:

   # chown 936600010:936600001 /home/ipa-user

4.2.2. Configuring single sign-on for Windows virtual machines

Procedure

1. Select the Windows virtual machine. Ensure the machine is powered up.
2. On the virtual machine, locate the CD drive and open the CD.
3. Launch virtio-win-guest-tools.
4. Click Options
5. Select Install oVirt Guest Agent.
6. Click OK.
7. Click Install.
8. When the installation completes, you are prompted to restart the machine to apply the changes.

4.2.3. Disabling Single Sign-on for Virtual Machines

1. Select a virtual machine and click Edit.
2. Click the Console tab.
3. Select the Disable Single Sign On check box.
4. Click OK.

4.3.1. Using USB Devices on a Windows Client

USB redirection is only supported when you open the virtual machine from the VM Portal.

Procedure

1. When the usbdk driver is installed, click → and select a virtual machine that is configured to use the SPICE protocol.
2. Click the Console tab.
3. Select the USB enabled checkbox and click OK.
4. Click → .
5. Select the Enable USB Auto-Share check box and click OK.
6. Start the virtual machine from the VM Portal and click Console to connect to that virtual machine.
7. Plug your USB device into the client machine to make it appear automatically on the guest machine.

4.3.2. Using USB Devices on a Red Hat Enterprise Linux Client

USB redirection is only supported when you open the virtual machine from the VM Portal.

Procedure

1. Click → .
2. Select a virtual machine that has been configured to use the SPICE protocol and click Edit. This opens the Edit Virtual Machine window.
3. Click the Console tab.
4. Select the USB enabled checkbox and click OK.
5. Click → .
6. Select the Enable USB Auto-Share check box and click OK.
7. Start the virtual machine from the VM Portal and click Console to connect to that virtual machine.
8. Plug your USB device into the client machine to make it appear automatically on the guest machine.

4.4.1. Configuring Multiple Displays for Red Hat Enterprise Linux Virtual Machines

1. Start a SPICE session with the virtual machine.
2. Open the View drop-down menu at the top of the SPICE client window.
3. Open the Display menu.
4. Click the name of a display to enable or disable that display.

By default, Display 1 is the only display that is enabled on starting a SPICE session with a virtual machine. If no other displays are enabled, disabling this display will close the session.

4.4.2. Configuring Multiple Displays for Windows Virtual Machines

1. Click → and select a virtual machine.
2. With the virtual machine in a powered-down state, click Edit.
3. Click the Console tab.

4. Select the number of displays from the Monitors drop-down list.

   This setting controls the maximum number of displays that can be enabled for the virtual machine. While the virtual machine is running, additional displays can be enabled up to this number.

5. Click OK.
6. Start a SPICE session with the virtual machine.
7. Open the View drop-down menu at the top of the SPICE client window.
8. Open the Display menu.

9. Click the name of a display to enable or disable that display.

   By default, Display 1 is the only display that is enabled on starting a SPICE session with a virtual machine. If no other displays are enabled, disabling this display will close the session.

4.5.1. Console Options

SPICE is not supported on virtual machines running Windows 8 or Windows 8.1. If a virtual machine running one of these operating systems is configured to use the SPICE protocol, it detects the absence of the required SPICE drivers and runs in VGA compatibility mode.

4.5.2. Accessing Console Options

Procedure

1. Click → and select a running virtual machine.
2. Click → .

You can configure the connection protocols and video type in the Console tab of the Edit Virtual Machine window in the Administration Portal. Additional options specific to each of the connection protocols, such as the keyboard layout when using the VNC connection protocol, can be configured. See Virtual Machine Console settings explained for more information.

4.5.3. SPICE Console Options

• Map control-alt-del shortcut to ctrl+alt+end: Select this check box to map the Ctrl + Alt + Del key combination to Ctrl + Alt + End inside the virtual machine.
• Enable USB Auto-Share: Select this check box to automatically redirect USB devices to the virtual machine. If this option is not selected, USB devices will connect to the client machine instead of the guest virtual machine. To use the USB device on the guest machine, manually enable it in the SPICE client menu.
• Open in Full Screen: Select this check box for the virtual machine console to automatically open in full screen when you connect to the virtual machine. Press SHIFT + F11 to toggle full screen mode on or off.
• Enable SPICE Proxy: Select this check box to enable the SPICE proxy.

4.5.4. VNC Console Options

• Native Client: When you connect to the console of the virtual machine, a file download dialog provides you with a file that opens a console to the virtual machine via Remote Viewer.
• noVNC: When you connect to the console of the virtual machine, a browser tab is opened that acts as the console.

• Map control-alt-delete shortcut to ctrl+alt+end: Select this check box to map the Ctrl + Alt + Del key combination to Ctrl + Alt + End inside the virtual machine.

4.5.5. RDP Console Options

• Auto: The Manager automatically selects the method for invoking the console.
• Native client: When you connect to the console of the virtual machine, a file download dialog provides you with a file that opens a console to the virtual machine via Remote Desktop.

• Use Local Drives: Select this check box to make the drives on the client machine accessible on the guest virtual machine.

4.5.6. Remote Viewer Options

4.6.1. Adding a Watchdog Card to a Virtual Machine

Procedure

1. Click → and select a virtual machine.
2. Click Edit.
3. Click the High Availability tab.
4. Select the watchdog model to use from the Watchdog Model drop-down list.
5. Select an action from the Watchdog Action drop-down list. This is the action that the virtual machine takes when the watchdog is triggered.
6. Click OK.

4.6.2. Installing a Watchdog

1. Log in to the virtual machine on which the watchdog card is attached.

2. Install the watchdog package and dependencies:

   # yum install watchdog

3. Edit the /etc/watchdog.conf file and uncomment the following line:

   watchdog-device = /dev/watchdog

4. Save the changes.

5. Start the watchdog service and ensure this service starts on boot:

   • Red Hat Enterprise Linux 6:

     # service watchdog start
     # chkconfig watchdog on

   • Red Hat Enterprise Linux 7:

     # systemctl start watchdog.service
     # systemctl enable watchdog.service

4.6.3. Confirming Watchdog Functionality

This procedure is provided for testing the functionality of watchdogs only and must not be run on production machines.

1. Log in to the virtual machine on which the watchdog card is attached.

2. Confirm that the watchdog card has been identified by the virtual machine:

   # lspci | grep watchdog -i

3. Run one of the following commands to confirm that the watchdog is active:

   • Trigger a kernel panic:

     # echo c > /proc/sysrq-trigger

   • Terminate the watchdog service:

     # kill -9 pgrep watchdog

4.6.4. Parameters for Watchdogs in watchdog.conf

For a more detailed explanation of options for configuring the watchdog service and using the watchdog command, see the watchdog man page.

Table 4.2. watchdog.conf variables

4.10.1. Creating a High Performance Virtual Machine, Template, or Pool

1. In the New or Edit window, select High Performance from the Optimized for drop-down menu.

   Selecting this option automatically performs certain configuration changes to this virtual machine, which you can view by clicking different tabs. You can change them back to their original settings or override them. (See Automatic High Performance Configuration Settings for details.) If you change a setting, its latest value is saved.

2. Click OK.

   If you have not set any manual configurations, the High Performance Virtual Machine/Pool Settings screen describing the recommended manual configurations appears.

   If you have set some of the manual configurations, the High Performance Virtual Machine/Pool Settings screen displays the settings you have not made.

   If you have set all the recommended manual configurations, the High Performance Virtual Machine/Pool Settings screen does not appear.

3. If the High Performance Virtual Machine/Pool Settings screen appears, click Cancel to return to the New or Edit window to perform the manual configurations. See Configuring the Recommended Manual Settings for details.

   Alternatively, click OK to ignore the recommendations. The result may be a drop in the level of performance.

4. Click OK.

   You can view the optimization type in the General tab of the details view of the virtual machine, pool, or template.

Certain configurations can override the high performance settings. For example, if you select an instance type for a virtual machine before selecting High Performance from the Optimized for drop-down menu and performing the manual configuration, the instance type configuration will not affect the high performance configuration. If, however, you select the instance type after the high performance configurations, you should verify the final configuration in the different tabs to ensure that the high performance configurations have not been overridden by the instance type.

The last-saved configuration usually takes priority.

Support for instance types is now deprecated, and will be removed in a future release.

4.10.2. Configuring the Recommended Manual Settings

• Pinning CPUs
• Setting the NUMA Pinning Policy
• Configuring Huge Pages
• Disabling KSM

5.2.1. Adding a New Network Interface

You can create an overlay network for your virtual machines, isolated from the hosts, by defining a logical network that is not attached to the physical interfaces of the host. For example, you can create a DMZ environment, in which the virtual machines communicate among themselves over the bridge created in the host.

The overlay network uses OVN, which must be installed as an external network provider. See the Administration Guide for more information

Procedure

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Network Interfaces tab.
4. Click New.
5. Enter the Name of the network interface.
6. Select the Profile and the Type of network interface from the drop-down lists. The Profile and Type drop-down lists are populated in accordance with the profiles and network types available to the cluster and the network interface cards available to the virtual machine.
7. Select the Custom MAC address check box and enter a MAC address for the network interface card as required.
8. Click OK.

5.2.2. Editing a Network Interface

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Network Interfaces tab and select the network interface to edit.
4. Click Edit.
5. Change settings as required. You can specify the Name, Profile, Type, and Custom MAC address. See Adding a Network Interface.
6. Click OK.

5.2.3. Hot Plugging a Network Interface

The guest operating system must support hot plugging network interfaces.

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Network Interfaces tab and select the network interface to hot plug.
4. Click Edit.
5. Set the Card Status to Plugged to enable the network interface, or set it to Unplugged to disable the network interface.
6. Click OK.

5.2.4. Removing a Network Interface

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Network Interfaces tab and select the network interface to remove.
4. Click Remove.
5. Click OK.

5.2.5. Configuring a virtual machine to ignore NICs

Procedure

1. In the /etc/ovirt-guest-agent.conf configuration file on the virtual machine, insert the following line, with the NICs to be ignored separated by spaces:

   ignored_nics = first_NIC_to_ignore second_NIC_to_ignore

2. Start the agent:

   # systemctl start ovirt-guest-agent

Some virtual machine operating systems automatically start the guest agent during installation.

If your virtual machine’s operating system automatically starts the guest agent or if you need to configure the denylist on many virtual machines, use the configured virtual machine as a template for creating additional virtual machines. See Creating a template from an existing virtual machine for details.

5.3.1. Adding a New Virtual Disk

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Disks tab.
4. Click New.
5. Use the appropriate radio buttons to switch between Image and Direct LUN.
6. Enter a Size(GB), Alias, and Description for the new disk.
7. Use the drop-down lists and check boxes to configure the disk. See Add Virtual Disk dialogue entries for more details on the fields for all disk types.
8. Click OK.

5.3.2. Attaching an Existing Disk to a Virtual Machine

Procedure

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Disks tab.
4. Click Attach.
5. Select one or more virtual disks from the list of available disks and select the required interface from the Interface drop-down.
6. Click OK.

No Quota resources are consumed by attaching virtual disks to, or detaching virtual disks from, virtual machines.

5.3.3. Extending the Available Size of a Virtual Disk

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Disks tab and select the disk to edit.
4. Click Edit.
5. Enter a value in the Extend size by(GB) field.
6. Click OK.

5.3.4. Hot Plugging a Virtual Disk

The guest operating system must support hot plugging virtual disks.

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Disks tab and select the virtual disk to hot plug.
4. Click More Actions (
   
   ), then click Activate to enable the disk, or Deactivate to disable the disk.
5. Click OK.

5.3.5. Removing a Virtual Disk from a Virtual Machine

1. Click → .
2. Click a virtual machine name to go to the details view.
3. Click the Disks tab and select the virtual disk to remove.
4. Click More Actions (
   
   ), then click Deactivate.
5. Click OK.
6. Click Remove.
7. Optionally, select the Remove Permanently check box to completely remove the virtual disk from the environment. If you do not select this option — for example, because the disk is a shared disk — the virtual disk will remain in → .
8. Click OK.

5.3.6. Importing a Disk Image from an Imported Storage Domain

Only QEMU-compatible disks can be imported into the Manager.

1. Click → .
2. Click an imported storage domain to go to the details view.
3. Click Disk Import.
4. Select one or more disk images and click Import. This opens the Import Disk(s) window.
5. Select the appropriate Disk Profile for each disk.
6. Click OK to import the selected disks.

5.3.7. Importing an Unregistered Disk Image from an Imported Storage Domain

Only QEMU-compatible disks can be imported into the Manager.

1. Click → .
2. Click More Actions (
   
   ), then click Scan Disks so that the Manager can identify unregistered disks.
3. Select an unregistered disk name and click Disk Import.
4. Select one or more disk images and click Import. This opens the Import Disk(s) window.
5. Select the appropriate Disk Profile for each disk.
6. Click OK to import the selected disks.

5.4.1. Hot Plugging Virtual Memory

This feature is currently not supported for the self-hosted engine Manager virtual machine.

Procedure

1. Click → and select a running virtual machine.
2. Click Edit.
3. Click the System tab.
4. Increase the Memory Size by entering the total amount required. Memory can be added in multiples of 256 MB. By default, the maximum memory allowed for the virtual machine is set to 4x the memory size specified. Though the value is changed in the user interface, the maximum value is not hot plugged, and you will see the pending changes icon (
   
   ). To avoid that, you can change the maximum memory back to the original value.

5. Click OK.

   This action opens the Pending Virtual Machine changes window, as some values such as maxMemorySizeMb and minAllocatedMem will not change until the virtual machine is restarted. However, the hot plug action is triggered by the change to the Memory Size value, which can be applied immediately.

6. Click OK.

5.4.2. Hot Unplugging Virtual Memory

Prerequisites

• Only memory added with hot plugging can be hot unplugged.
• The virtual machine’s operating system must support memory hot unplugging.
• The virtual machine must not have a memory balloon device enabled. This feature is disabled by default.
• All blocks of the hot-plugged memory must be set to online_movable in the virtual machine’s device management rules. In virtual machines running up-to-date versions of Red Hat Enterprise Linux or CoreOS, this rule is set by default. For information on device management rules, consult the documentation for the virtual machine’s operating system.

• To ensure that hot plugged memory can be hot unplugged later, add the movable_node option to the kernel command line of the virtual machine as follows and reboot the virtual machine:

  # grubby --update-kernel=ALL --args="movable_node"

Procedure

1. Click → and select a running virtual machine.
2. Click the Vm Devices tab.
3. In the Hot Unplug column, click Hot Unplug beside the memory device to be removed.

4. Click OK in the Memory Hot Unplug window.

   The Physical Memory Guaranteed value for the virtual machine is decremented automatically if necessary.

6.6.1. Updating the Guest Agents and Drivers on Red Hat Enterprise Linux

1. Log in to the Red Hat Enterprise Linux virtual machine.

2. Update the ovirt-guest-agent-common package:

   # yum update ovirt-guest-agent-common

3. Restart the service:

   • For Red Hat Enterprise Linux 6

     # service ovirt-guest-agent restart

   • For Red Hat Enterprise Linux 7

     # systemctl restart ovirt-guest-agent.service

6.6.2. Updating Windows drivers with Windows Update

Procedure

1. Log in to the virtual machine.
2. Ensure that Windows Update is enabled so you can get updates.
3. Check Windows Update for updates from Red Hat, Inc.
4. Manually install any updates that have not been automatically installed.

Additional resources

• Updating Windows guest agents and drivers using the command prompt
• See the Microsoft documentation for details on using Windows Update.

6.6.3. Updating Windows guest agents and drivers using the command prompt

Procedure

1. If you are updating the drivers, on the Windows virtual machine, use the netsh utility to save TCP settings before uninstalling the netkvm driver:

   C:WINDOWSsystem32>netsh dump > filename.txt

2. On the Manager machine, update the virtio-win package to the latest version:

   # dnf upgrade -y virtio-win

   The virtio-win_version.iso file is located in /usr/share/virtio-win/ on the Manager machine.

3. Upload the ISO file to a data domain. For more information, see Uploading Images to a Data Storage Domain in the Administration Guide.
4. In the Administration or VM Portal, if the virtual machine is running, use the Change CD drop-down list to attach the virtio-win_version.iso file to each of your virtual machines. If the virtual machine is powered off, click the Run Once button and attach the ISO as a CD.
5. Log in to the virtual machine.
6. Select the CD Drive (D: for this example) containing the virtio-win_version.iso file.

7. Reinstall the guest agents or drivers:

   • To reinstall only the guest agents, use qemu-ga-x86_64.msi:

     C:WINDOWSsystem32>msiexec.exe /i D:guest-agentqemu-ga-x86_64.msi /passive /norestart

   • To reinstall the drivers, use virtio-win-gt-x64.msi:

     C:WINDOWSsystem32>msiexec.exe /i D:virtio-win-gt-x64.msi /passive /norestart

8. If you are updating the drivers, restore the settings you saved using netsh:

   C:WINDOWSsystem32>netsh -f filename.txt

6.8.1. Managing System Permissions for a Virtual Machine

• Create, edit, and remove virtual machines.
• Run, suspend, shutdown, and stop virtual machines.

You can only assign roles and permissions to existing users.

6.8.2. Virtual Machine Administrator Roles Explained

Table 6.1. Red Hat Virtualization System Administrator Roles

6.8.3. Virtual Machine User Roles Explained

Table 6.2. Red Hat Virtualization System User Roles

6.8.4. Assigning Virtual Machines to Users

• A User can connect to and use virtual machines. This role is suitable for desktop end users performing day-to-day tasks.
• A PowerUser can create virtual machines and view virtual resources. This role is suitable if you are an administrator or manager who needs to provide virtual resources for your employees.
• A UserVmManager can edit and remove virtual machines, assign user permissions, use snapshots and use templates. It is suitable if you need to make configuration changes to your virtual environment.

Procedure

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Permissions tab.
4. Click Add.
5. Enter a name, or user name, or part thereof in the Search text box, and click Go. A list of possible matches display in the results list.
6. Select the check box of the user to be assigned the permissions.
7. Select UserRole from the Role to Assign drop-down list.
8. Click OK.

If a user is assigned permissions to only one virtual machine, single sign-on (SSO) can be configured for the virtual machine. With single sign-on enabled, when a user logs in to the VM Portal, and then connects to a virtual machine through, for example, a SPICE console, users are automatically logged in to the virtual machine and do not need to type in the user name and password again. Single sign-on can be enabled or disabled on a per virtual machine basis. See Configuring Single Sign-On for Virtual Machines for more information on how to enable and disable single sign-on for virtual machines.

6.8.5. Removing Access to Virtual Machines from Users

1. Click → .
2. Click the virtual machine’s name to go to the details view.
3. Click Permissions.
4. Click Remove. A warning message displays, asking you to confirm removal of the selected permissions.
5. To proceed, click OK. To abort, click Cancel.

6.9.1. Creating a Snapshot of a Virtual Machine

1. Click → .
2. Click a virtual machine’s name to go to the details view.
3. Click the Snapshots tab and click Create.
4. Enter a description for the snapshot.

5. Select Disks to include using the check boxes.

   If no disks are selected, a partial snapshot of the virtual machine, without a disk, is created. You can preview this snapshot to view the configuration of the virtual machine. Note that committing a partial snapshot will result in a virtual machine without a disk.

6. Select Save Memory to include a running virtual machine’s memory in the snapshot.
7. Click OK.

6.9.2. Using a Snapshot to Restore a Virtual Machine

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Snapshots tab to list the available snapshots.
4. Select a snapshot to restore in the upper pane. The snapshot details display in the lower pane.
5. Click the Preview drop-down menu button and select Custom.

6. Use the check boxes to select the VM Configuration, Memory, and disk(s) you want to restore, then click OK. This allows you to create and restore from a customized snapshot using the configuration and disk(s) from multiple snapshots.

   The status of the snapshot changes to Preview Mode. The status of the virtual machine briefly changes to Image Locked before returning to Down.

7. Shut down the virtual machine.
8. Start the virtual machine; it runs using the disk image of the snapshot.

9. Click Commit to permanently restore the virtual machine to the condition of the snapshot. Any subsequent snapshots are erased.

   Alternatively, click the Undo button to deactivate the snapshot and return the virtual machine to its previous state.

6.9.3. Creating a Virtual Machine from a Snapshot

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Snapshots tab to list the available snapshots.
4. Select a snapshot in the list displayed and click Clone.
5. Enter the Name of the virtual machine.
6. Click OK.

6.9.4. Deleting a Snapshot

1. Click → .
2. Click the virtual machine’s name to go to the details view.
3. Click the Snapshots tab to list the snapshots for that virtual machine.
4. Select the snapshot to delete.
5. Click Delete.
6. Click OK.

If the deletion fails, fix the underlying problem (for example, a failed host, an inaccessible storage device, or a temporary network issue) and try again.

6.10.1. Adding a Host Device to a Virtual Machine

• SCSI tape drives, disks, and changers
• PCI NICs, GPUs, and HBAs
• USB mice, cameras, and disks

When you change the Pinned Host setting, it removes the current host devices. When you save these changes, in the virtual machine’s Host settings, it sets Start Running On to Specific Host(s) and specifies the host you selected earlier using the Pinned Host setting.

Prerequisites

• The state of the host is Up.
• The host is configured for direct device assignment.

Procedure

1. In the Administration Portal, click → .
2. Shut down the virtual machine.
3. Click the name of the virtual machine to go to the details view.
4. Click the Host Devices tab.
5. Click Add device. This opens the Add Host Devices pane.
6. Use Pinned Host to select the host where the virtual machine runs.

7. Use Capability to list pci, scsi, nvdimm, or usb_device devices.

   The nvdimm option is a technical preview feature. For more information, see nvdimm host devices.

8. Use Available Host Devices to select devices.
9. Click the down arrow to move devices to Host Devices to be attached.
10. Click OK to attach these devices to the virtual machine and close the window.

11. Optional: If you attach a SCSI host device, configure the optimal driver.

    1. Click the Edit button. This opens the Edit Virtual Machine pane.
    2. Click the Custom Properties tab.
    3. Click the Please select a key and select scsi_hostdev from the bottom of the drop-down list.
    4. In most cases, select scsi-hd. Otherwise, for tape or CD changer devices, select the scsi_generic option. For more details, see Virtual Machine Custom Properties Settings Explained.
    5. Click the OK button.
12. Run the virtual machine.
13. While the virtual machine starts running, watch for Operation Canceled error messages.

Troubleshooting

If you cannot add a host device to a virtual machine, or a virtual machine cannot start running with the attached host devices, it generates Operation Canceled error messages. For example:

• Respond to a The host <hostname> did not satisfy internal filter HostDevice because it does not support host device passthrough message by configuring the host for device passthrough and restarting the virtual machine.
• Respond to the The host <hostname> did not satisfy internal filter HostDevice because the host does not provide requested host devices message by adding the host device to the host.
• Respond to a Cannot add Host devices because the VM is in Up status message by shutting down the virtual machine before adding a host device.
• Verify that the state of the host is Up.

Additional resources

• Host Devices in the Virtual Machine Management Guide.
• Pinning a Virtual Machine to Multiple Hosts
• Configuring a Host for PCI Passthrough
• Additional Hardware Considerations for Using Device Assignment in Hardware Considerations for Implementing SR-IOV.
• nvdimm host devices

6.10.2. Removing Host Devices from a Virtual Machine

Procedure

1. Click → .
2. Select a virtual machine to go to the details view.
3. Click the Host Devices tab to list the host devices attached to the virtual machine.
4. Select the host device to detach from the virtual machine, or hold Ctrl to select multiple devices, and click Remove device. This opens the Remove Host Device(s) window.
5. Click OK to confirm and detach these devices from the virtual machine.

6.10.3. Pinning a Virtual Machine to Another Host

1. Click a virtual machine name and click the Host Devices tab.
2. Click Pin to another host. This opens the Pin VM to Host window.
3. Use the Host drop-down menu to select a host.
4. Click OK to pin the virtual machine to the selected host.

6.10.4. NVDIMM host devices

NVDIMM devices are Technology Preview features only. Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information, see Red Hat Technology Preview Features Support Scope.

Limitations

• Memory snapshots are disabled when an NVDIMM device is present in a virtual machine. There is no way to make a snapshot of NVDIMM content, and a memory snapshot cannot work correctly without having the corresponding NVDIMM data.
• In RHV, each NVDIMM device passed to a virtual machine has an automatically-assigned label area with a fixed size of 128 KB. IBM POWER hardware, and 128 KB is the minimum label size allowed by QEMU.
• By default, the virtual machine uses the whole NVDIMM device. You cannot configure the size of the NVDIMM from the virtual machine. To configure its size, partition the NVDIMM device on the host and add the partition to the virtual machine.
• The size of the NVDIMM device on the virtual machine may be slightly lower than on the host to comply with libvirt and QEMU alignment and size adjustments. Precise sizing is also needed to make memory hotplug work.
• libvirt and QEMU adjust their size and label placement. If those internal arrangements change, it can cause data loss.
• NVDIMM hotplug is not supported by the platform.
• Virtual machines with NVDIMM devices cannot migrate because they are pinned to a host.
• SELinux currently prevents access to NVDIMM devices in devdax mode, see BZ1855336.

Avoid using NVDIMM on IBM POWER hardware. This combination is currently not expected to be stable until further work is completed.

6.11.1. Affinity Groups

The VM Affinity Rule

When you create an Affinity Group, you select the virtual machines that belong to the group. To define where these virtual machines can run in relation to each other, you enable a VM Affinity Rule: A Positive affinity rule tries to run the virtual machines together on a single host; a Negative affinity rule tries to run the virtual machines on separate hosts. If the rule cannot be fulfilled, the outcome depends on whether the weight or filter module is enabled.

The Host Affinity Rule

Optionally, you can add hosts to the Affinity Group. To define where virtual machines in the group can run in relation to hosts in the group, you enable a Host Affinity Rule: A Positive affinity rule tries to run the virtual machines on hosts in the affinity group; a Negative affinity rule tries to run the virtual machines on hosts that are not in the affinity group. If the rule cannot be fulfilled, the outcome depends on whether the weight or filter module is enabled.

The Default Weight Module

By default, both rules apply the weight module in the cluster’s scheduling policy. With the weight module, the scheduler attempts to fulfill a rule, but allows the virtual machines in the affinity group to run anyway if the rule cannot be fulfilled.

The Enforcing Option and Filter Module

Both rules have an Enforcing option which applies the filter module in the cluster’s scheduling policy. The filter module overrides the weight module. With the filter module enabled, the scheduler requires that a rule be fulfilled. If a rule cannot be fulfilled, the filter module prevents the virtual machines in the affinity group from running.

Examples

To see how these rules and options can be used with one another, see Affinity group examples.

• For affinity labels to work, the filter module section of the scheduling policies must contain Label.
• If an affinity group and affinity label conflict with each other, the affected virtual machines do not run. To help prevent, troubleshoot, and resolve conflicts, see Affinity group troubleshooting.

Each rule is affected by the weight and filter modules in the cluster’s scheduling policy.

For more information, see Scheduling Policies in the Administration Guide.

• Affinity groups apply to virtual machines in a cluster. Moving a virtual machine from one cluster to another removes it from the affinity groups in the original cluster.
• Virtual machines do not have to restart for the affinity group rules to take effect.

6.11.2. Creating an Affinity Group

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Affinity Groups tab.
4. Click New.
5. Enter a Name and Description for the affinity group.
6. From the VM Affinity Rule drop-down, select Positive to apply positive affinity or Negative to apply negative affinity. Select Disable to disable the affinity rule.
7. Select the Enforcing check box to apply hard enforcement, or ensure this check box is cleared to apply soft enforcement.
8. Use the drop-down list to select the virtual machines to be added to the affinity group. Use the + and — buttons to add or remove additional virtual machines.
9. Click OK.

6.11.3. Editing an Affinity Group

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Affinity Groups tab.
4. Click Edit.
5. Change the VM Affinity Rule drop-down and Enforcing check box to the preferred values and use the + and — buttons to add or remove virtual machines to or from the affinity group.
6. Click OK.

6.11.4. Removing an Affinity Group

1. Click → and select a virtual machine.
2. Click the virtual machine’s name to go to the details view.
3. Click the Affinity Groups tab.
4. Click Remove.
5. Click OK.

6.11.5. Affinity Groups Examples

Example 6.1. High Availability

Example 6.2. Performance

Example 6.3. Licensing

6.11.6. Affinity Groups Troubleshooting

To help prevent problems with affinity groups

• Plan and document the scenarios and outcomes you expect when using affinity groups.
• Verify and test the outcomes under a range of conditions.
• Follow change management best practices.
• Only use the Enforcing option if it is required.

For possible conflicts between affinity labels and affinity groups

• If an affinity label and affinity group conflict with each other, the intersecting set of virtual machines do not run.

• To determine whether a conflict is possible:

  • Inspect the filter module section of the cluster’s scheduling policies. These must contain both a Label keyword and a VmAffinityGroups OR VmToHostsAffinityGroups keyword. Otherwise, a conflict is not possible. (The presence of VmAffinityGroups and VmToHostsAffinityGroups in the weight module section does not matter because Label in a filter module section would override them.)
  • Inspect the affinity groups. They must contain a rule that has Enforcing enabled. Otherwise, a conflict is not possible.

• If a conflict is possible, identify the set of virtual machines that might be involved:

  • Inspect the affinity labels and groups. Make a list of virtual machines that are members of both an affinity label and an affinity group with an Enforcing option enabled.
  • For each host and virtual machine in this intersecting set, analyze the conditions under which a potential conflict occurs.
• Determine whether the actual non-running virtual machines match the ones in the analysis.
• Restructure the affinity groups and affinity labels to help avoid unintended conflicts.
• Verify that any changes produce the expected results under a range of conditions.
• If you have overlapping affinity groups and affinity labels, it can be easier to view them in one place as affinity groups. Consider converting an affinity label into an equivalent affinity group, which has a Host affinity rule with Positive selected and Enforcing enabled.

6.12.1. About Affinity Labels

Affinity labels are a subset of affinity groups and can conflict with them. If there is a conflict, the virtual machine will not start.

6.12.2. Creating an Affinity Label

1. Click → and select the appropriate cluster.
2. Click the cluster’s name to go to the details view.
3. Click the Affinity Labels tab.
4. Click New.
5. Enter a Name for the affinity label.
6. Use the drop-down lists to select the virtual machines and hosts to be associated with the label. Use the + button to add additional virtual machines and hosts.
7. Click OK.

6.12.3. Editing an Affinity Label

1. Click → and select the appropriate cluster.
2. Click the cluster’s name to go to the details view.
3. Click the Affinity Labels tab.
4. Select the label you want to edit.
5. Click Edit.
6. Use the + and — buttons to add or remove virtual machines and hosts to or from the affinity label.
7. Click OK.

6.12.4. Deleting an Affinity Label

1. Click → and select the appropriate cluster.
2. Click the cluster’s name to go to the details view.
3. Click the Affinity Labels tab.
4. Select the label you want to remove.
5. Click Edit.
6. Use the — buttons to remove all virtual machines and hosts from the label.
7. Click OK.
8. Click Delete.
9. Click OK.

6.13.1. Exporting a Virtual Machine to the Export Domain

1. Click → and select a virtual machine.
2. Click More Actions (
   
   ), then click Export to Export Domain.

3. Optionally, select the following check boxes in the Export Virtual Machine window:

   • Force Override: overrides existing images of the virtual machine on the export domain.

   • Collapse Snapshots: creates a single export volume per disk. This option removes snapshot restore points and includes the template in a template-based virtual machine, and removes any dependencies a virtual machine has on a template. For a virtual machine that is dependent on a template, either select this option, export the template with the virtual machine, or make sure the template exists in the destination data center.

     When you create a virtual machine from a template by clicking → and clicking New VM, you wll see two storage allocation options in the Storage Allocation section in the Resource Allocation tab:

     • If Clone is selected, the virtual machine is not dependent on the template. The template does not have to exist in the destination data center.
     • If Thin is selected, the virtual machine is dependent on the template, so the template must exist in the destination data center or be exported with the virtual machine. Alternatively, select the Collapse Snapshots check box to collapse the template disk and virtual disk into a single disk.

     To check which option was selected, click a virtual machine’s name and click the General tab in the details view.

4. Click OK.

6.13.2. Exporting a Virtual Machine to a Data Domain

When you create a virtual machine from a template, you can choose from either of two storage allocation options:

To check which option is selected, click a virtual machine’s name and click the General tab in the details view.

Prerequisites

• The data domain is attached to a data center.

• The virtual machine is powered off.

  Procedure

  1. Click → and select a virtual machine.
  2. Click Export.
  3. Specify a name for the exported virtual machine.
  4. Select a target storage domain from the Storage domain pop-up menu.
  5. (Optional) Check Collapse snapshots to export the virtual machine without any snapshots.
  6. Click OK.

When you move a disk from one type of data domain another, the disk format changes accordingly. For example, if the disk is on an NFS data domain, and it is in sparse format, then if you move the disk to an iSCSI domain its format changes to preallocated. This is different from using an export domain, because an export domain is NFS.

6.13.3. Importing a Virtual Machine from the Export Domain

1. Click → and select the export domain. The export domain must have a status of Active.
2. Click the export domain’s name to go to the details view.
3. Click the VM Import tab to list the available virtual machines to import.
4. Select one or more virtual machines to import and click Import.
5. Select the Target Cluster.
6. Select the Collapse Snapshots check box to remove snapshot restore points and include templates in template-based virtual machines.
7. Click the virtual machine to be imported and click the Disks sub-tab. From this tab, you can use the Allocation Policy and Storage Domain drop-down lists to select whether the disk used by the virtual machine will be thinly provisioned or preallocated, and can also select the storage domain on which the disk will be stored. An icon is also displayed to indicate which of the disks to be imported acts as the boot disk for that virtual machine.

8. Click OK to import the virtual machines.

   The Import Virtual Machine Conflict window opens if the virtual machine exists in the virtualized environment.

   Choose one of the following radio buttons:

   • Don’t import
   • Import as cloned and enter a unique name for the virtual machine in the New Name field.
9. Optionally select the Apply to all check box to import all duplicated virtual machines with the same suffix, and then enter a suffix in the Suffix to add to the cloned VMs field.
10. Click OK.

During a single import operation, you can only import virtual machines that share the same architecture. If any of the virtual machines to be imported have a different architecture to that of the other virtual machines to be imported, a warning will display and you will be prompted to change your selection so that only virtual machines with the same architecture will be imported.

6.13.4. Importing a Virtual Machine from a Data Domain

Prerequisite

• If you are importing a virtual machine from an imported data storage domain, the imported storage domain must be attached to a data center and activated.

Procedure

1. Click → .
2. Click the imported storage domain’s name. This opens the details view.
3. Click the VM Import tab.
4. Select one or more virtual machines to import.
5. Click Import.
6. For each virtual machine in the Import Virtual Machine(s) window, ensure the correct target cluster is selected in the Cluster list.

7. Map external virtual machine vNIC profiles to profiles that are present on the target cluster(s):

   1. Click vNic Profiles Mapping.
   2. Select the vNIC profile to use from the Target vNic Profile drop-down list.
   3. If multiple target clusters are selected in the Import Virtual Machine(s) window, select each target cluster in the Target Cluster drop-down list and ensure the mappings are correct.
   4. Click OK.

8. If a MAC address conflict is detected, an exclamation mark appears next to the name of the virtual machine. Mouse over the icon to view a tooltip displaying the type of error that occurred.

   Select the Reassign Bad MACs check box to reassign new MAC addresses to all problematic virtual machines. Alternatively, you can select the Reassign check box per virtual machine.

   If there are no available addresses to assign, the import operation will fail. However, in the case of MAC addresses that are outside the cluster’s MAC address pool range, it is possible to import the virtual machine without reassigning a new MAC address.

9. Click OK.

6.13.5. Importing a Virtual Machine from a VMware Provider

The virt-v2v package is not available on the ppc64le architecture and these hosts cannot be used as proxy hosts.

If the import fails, refer to the relevant log file in /var/log/vdsm/import/ and to /var/log/vdsm/vdsm.log on the proxy host for details.

Prerequisites

• The virt-v2v package must be installed on at least one host, referred to in this procedure as the proxy host. The virt-v2v package is available by default on Red Hat Virtualization Hosts and is installed on Red Hat Enterprise Linux hosts as a dependency of VDSM when added to the Red Hat Virtualization environment.
• Red Hat Enterprise Linux hosts must be Red Hat Enterprise Linux 7.2 or later.

• At least one data and one ISO storage domain are connected to the data center.

  You can only migrate to shared storage, such as NFS, iSCSI, or FCP. Local storage is not supported.

  Although the ISO storage domain has been deprecated, it is required for migration.

• The virtio-win_version.iso image file for Windows virtual machines is uploaded to the ISO storage domain. This image includes the guest tools that are required for migrating Windows virtual machines.
• The virtual machine must be shut down before being imported. Starting the virtual machine through VMware during the import process can result in data corruption.
• An import operation can only include virtual machines that share the same architecture. If any virtual machine to be imported has a different architecture, a warning appears and you are prompted to change your selection to include only virtual machines with the same architecture.

Procedure

1. Click → .
2. Click More Actions (
   
   ) and select Import. This opens the Import Virtual Machine(s) window.
3. Select VMware from the Source list.
4. If you have configured a VMware provider as an external provider, select it from the External Provider list. Verify that the provider credentials are correct. If you did not specify a destination data center or proxy host when configuring the external provider, select those options now.

5. If you have not configured a VMware provider, or want to import from a new VMware provider, provide the following details:

   1. Select from the list the Data Center in which the virtual machine will be available.
   2. Enter the IP address or fully qualified domain name of the VMware vCenter instance in the vCenter field.
   3. Enter the IP address or fully qualified domain name of the host from which the virtual machines will be imported in the ESXi field.
   4. Enter the name of the data center and the cluster in which the specified ESXi host resides in the Data Center field.
   5. If you have exchanged the SSL certificate between the ESXi host and the Manager, leave Verify server’s SSL certificate checked to verify the ESXi host’s certificate. If not, clear the option.
   6. Enter the Username and Password for the VMware vCenter instance. The user must have access to the VMware data center and ESXi host on which the virtual machines reside.
   7. Select a host in the chosen data center with virt-v2v installed to serve as the Proxy Host during virtual machine import operations. This host must also be able to connect to the network of the VMware vCenter external provider.
6. Click Load to list the virtual machines on the VMware provider that can be imported.

7. Select one or more virtual machines from the Virtual Machines on Source list, and use the arrows to move them to the Virtual Machines to Import list. Click Next.

   If a virtual machine’s network device uses the driver type e1000 or rtl8139, the virtual machine will use the same driver type after it has been imported to Red Hat Virtualization.

   If required, you can change the driver type to VirtIO manually after the import. To change the driver type after a virtual machine has been imported, see Editing network interfaces. If the network device uses driver types other than e1000 or rtl8139, the driver type is changed to VirtIO automatically during the import. The Attach VirtIO-drivers option allows the VirtIO drivers to be injected to the imported virtual machine files so that when the driver is changed to VirtIO, the device will be properly detected by the operating system.

8. Select the Cluster in which the virtual machines will reside.
9. Select a CPU Profile for the virtual machines.
10. Select the Collapse Snapshots check box to remove snapshot restore points and include templates in template-based virtual machines.
11. Select the Clone check box to change the virtual machine name and MAC addresses, and clone all disks, removing all snapshots. If a virtual machine appears with a warning symbol beside its name or has a tick in the VM in System column, you must clone the virtual machine and change its name.
12. Click each virtual machine to be imported and click the Disks sub-tab. Use the Allocation Policy and Storage Domain lists to select whether the disk used by the virtual machine will be thinly provisioned or preallocated, and select the storage domain on which the disk will be stored. An icon is also displayed to indicate which of the disks to be imported acts as the boot disk for that virtual machine.
13. If you selected the Clone check box, change the name of the virtual machine in the General sub-tab.
14. Click OK to import the virtual machines.

1. Click → .
2. Select a cluster.
3. Click Edit.
4. Click the General tab.

1. Click → .
2. Select the virtual machine.
3. Click Edit.
4. Click the System tab.
5. Click the Advanced Parameters arrow.
6. Specify the Custom CPU Type and click OK.

6.13.6. Exporting a Virtual Machine to a Host

1. Click → and select a virtual machine.
2. Click More Actions (
   
   ), then click Export to OVA.
3. Select the host from the Host drop-down list.
4. Enter the absolute path to the export directory in the Directory field, including the trailing slash. For example: /images2/ova/
5. Optionally change the default name of the file in the Name field.
6. Click OK

6.13.7. Importing a Virtual Machine from a Host

1. Copy the OVA file to a host in your cluster, in a file system location such as /var/tmp.

   The location can be a local directory or a remote NFS mount, as long as it is not in the`/root` directory or subdirectories. Ensure that it has sufficient space.

2. Ensure that the OVA file has permissions allowing read/write access to the qemu user (UID 36) and the kvm group (GID 36):

   # chown 36:36 path_to_OVA_file/file.OVA

3. Click → .

4. Click More Actions (
   
   ) and select Import. This opens the Import Virtual Machine(s) window.

   1. Select Virtual Appliance (OVA) from the Source list.
   2. Select a host from the Host list.
   3. In the Path field, specify the absolute path of the OVA file.
   4. Click Load to list the virtual machine to be imported.
   5. Select the virtual machine from the Virtual Machines on Source list, and use the arrows to move it to the Virtual Machines to Import list.

5. Click Next.

   1. Select the Storage Domain for the virtual machine.
   2. Select the Target Cluster where the virtual machines will reside.
   3. Select the CPU Profile for the virtual machines.
   4. Select the Allocation Policy for the virtual machines.
   5. Optionally, select the Attach VirtIO-Drivers check box and select the appropriate image on the list to add VirtIO drivers.
   6. Select the Allocation Policy for the virtual machines.
   7. Select the virtual machine, and on the General tab select the Operating System.
   8. On the Network Interfaces tab, select the Network Name and Profile Name.
   9. Click the Disks tab to view the Alias, Virtual Size, and Actual Size of the virtual machine.
6. Click OK to import the virtual machines.

6.13.8. Importing a virtual machine from a RHEL 5 Xen host

If you are importing a Windows virtual machine from a RHEL 5 Xen host and you are using VirtIO devices, install the VirtIO drivers before importing the virtual machine. If the drivers are not installed, the virtual machine may not boot after import.

The VirtIO drivers can be installed from the virtio-win_version.iso or the RHV-toolsSetup_version.iso. See Installing the Guest Agents and Drivers on Windows for details.

If you are not using VirtIO drivers, review the configuration of the virutal machine before first boot to ensure that VirtIO devices are not being used.

The virt-v2v package is not available on the ppc64le architecture and these hosts cannot be used as proxy hosts.

An import operation can only include virtual machines that share the same architecture. If any virtual machine to be imported has a different architecture, a warning appears and you are prompted to change your selection to include only virtual machines with the same architecture.

If the import fails, refer to the relevant log file in /var/log/vdsm/import/ and to /var/log/vdsm/vdsm.log on the proxy host for details.

Procedure

To import a virtual machine from RHEL 5 Xen, follow these steps:

1. Shut down the virtual machine. Starting the virtual machine through Xen during the import process can result in data corruption.

2. Enable public key authentication between the proxy host and the RHEL 5 Xen host:

   1. Log in to the proxy host and generate SSH keys for the vdsm user.

      # sudo -u vdsm ssh-keygen

   2. Copy the vdsm user’s public key to the RHEL 5 Xen host.

      # sudo -u vdsm ssh-copy-id root@xenhost.example.com

   3. Log in to the RHEL 5 Xen host to verify that the login works correctly.

      # sudo -u vdsm ssh root@xenhost.example.com

3. Log in to the Administration Portal.
4. Click → .
5. Click More Actions (
   
   ) and select Import. This opens the Import Virtual Machine(s) window.
6. Select the Data Center that contains the proxy host.
7. Select XEN (via RHEL) from the Source drop-down list.
8. Optionally, select a RHEL 5 Xen External Provider from the drop-down list. The URI will be pre-filled with the correct URI. See Adding a RHEL 5 Xen Host as a Virtual Machine Provider in the Administration Guide for more information.
9. Enter the URI of the RHEL 5 Xen host. The required format is pre-filled; you must replace <hostname> with the host name of the RHEL 5 Xen host.
10. Select the proxy host from the Proxy Host drop-down list.
11. Click Load to list the virtual machines on the RHEL 5 Xen host that can be imported.

12. Select one or more virtual machines from the Virtual Machines on Source list, and use the arrows to move them to the Virtual Machines to Import list.

    Due to current limitations, Xen virtual machines with block devices do not appear in the Virtual Machines on Source list. They must be imported manually. See Importing Block Based Virtual Machine from Xen host.

13. Click Next.
14. Select the Cluster in which the virtual machines will reside.
15. Select a CPU Profile for the virtual machines.

16. Use the Allocation Policy and Storage Domain lists to select whether the disk used by the virtual machine will be thinly provisioned or preallocated, and select the storage domain on which the disk will be stored.

    The target storage domain must be a file-based domain. Due to current limitations, specifying a block-based domain causes the V2V operation to fail.

17. If a virtual machine appears with a warning symbol beside its name, or has a tick in the VM in System column, select the Clone check box to clone the virtual machine.

    Cloning a virtual machine changes its name and MAC addresses and clones all of its disks, removing all snapshots.

18. Click OK to import the virtual machines.

1. Click → .
2. Select a cluster.
3. Click Edit.
4. Click the General tab.

1. Click → .
2. Select the virtual machine.
3. Click Edit.
4. Click the System tab.
5. Click the Advanced Parameters arrow.
6. Specify the Custom CPU Type and click OK.

Importing a Block-Based Virtual Machine from a RHEL 5 Xen Host

1. Enable public key authentication between the proxy host and the RHEL 5 Xen host:

   1. Log in to the proxy host and generate SSH keys for the vdsm user.

      # sudo -u vdsm ssh-keygen

   2. Copy the vdsm user’s public key to the RHEL 5 Xen host.

      # sudo -u vdsm ssh-copy-id root@xenhost.example.com

   3. Log in to the RHEL 5 Xen host to verify that the login works correctly.

      # sudo -u vdsm ssh root@xenhost.example.com

2. Attach an export domain. See Attaching an Existing Export Domain to a Data Center in the Administration Guide for details.

3. On the proxy host, copy the virtual machine from the RHEL 5 Xen host:

   # virt-v2v-copy-to-local -ic xen+ssh://root@xenhost.example.com vmname

4. Convert the virtual machine to libvirt XML and move the file to your export domain:

   # virt-v2v -i libvirtxml vmname.xml -o rhev -of raw -os storage.example.com:/exportdomain

5. In the Administration Portal, click → , click the export domain’s name, and click the VM Import tab in the details view to verify that the virtual machine is in your export domain.
6. Import the virtual machine into the destination data domain. See Importing the virtual machine from the export domain for details.

6.13.9. Importing a Virtual Machine from a KVM Host

The virtual machine must be shut down before being imported. Starting the virtual machine through KVM during the import process can result in data corruption.

An import operation can only include virtual machines that share the same architecture. If any virtual machine to be imported has a different architecture, a warning appears and you are prompted to change your selection to include only virtual machines with the same architecture.

If the import fails, refer to the relevant log file in /var/log/vdsm/import/ and to /var/log/vdsm/vdsm.log on the proxy host for details.

1. Enable public key authentication between the proxy host and the KVM host:

   1. Log in to the proxy host and generate SSH keys for the vdsm user.

      # sudo -u vdsm ssh-keygen

   2. Copy the vdsm user’s public key to the KVM host. The proxy host’s known_hosts file will also be updated to include the host key of the KVM host.

      # sudo -u vdsm ssh-copy-id root@kvmhost.example.com

   3. Log in to the KVM host to verify that the login works correctly.

      # sudo -u vdsm ssh root@kvmhost.example.com

2. Log in to the Administration Portal.
3. Click → .
4. Click More Actions (
   
   ) and select Import. This opens the Import Virtual Machine(s) window.
5. Select the Data Center that contains the proxy host.
6. Select KVM (via Libvirt) from the Source drop-down list.
7. Optionally, select a KVM provider External Provider from the drop-down list. The URI will be pre-filled with the correct URI. See Adding a KVM Host as a Virtual Machine Provider in the Administration Guide for more information.

8. Enter the URI of the KVM host in the following format:

   qemu+ssh://root@kvmhost.example.com/system

9. Keep the Requires Authentication check box selected.
10. Enter root in the Username field.
11. Enter the Password of the KVM host’s root user.
12. Select the Proxy Host from the drop-down list.
13. Click Load to list the virtual machines on the KVM host that can be imported.
14. Select one or more virtual machines from the Virtual Machines on Source list, and use the arrows to move them to the Virtual Machines to Import list.
15. Click Next.
16. Select the Cluster in which the virtual machines will reside.
17. Select a CPU Profile for the virtual machines.
18. Optionally, select the Collapse Snapshots check box to remove snapshot restore points and include templates in template-based virtual machines.
19. Optionally, select the Clone check box to change the virtual machine name and MAC addresses, and clone all disks, removing all snapshots. If a virtual machine appears with a warning symbol beside its name or has a tick in the VM in System column, you must clone the virtual machine and change its name.
20. Click each virtual machine to be imported and click the Disks sub-tab. Use the Allocation Policy and Storage Domain lists to select whether the disk used by the virtual machine will be thin provisioned or preallocated, and select the storage domain on which the disk will be stored. An icon is also displayed to indicate which of the disks to be imported acts as the boot disk for that virtual machine. See Virtual Disk Storage Allocation Policies in the Technical Reference for more information.
21. If you selected the Clone check box, change the name of the virtual machine in the General tab.
22. Click OK to import the virtual machines.

1. Click → .
2. Select a cluster.
3. Click Edit.
4. Click the General tab.

1. Click → .
2. Select the virtual machine.
3. Click Edit.
4. Click the System tab.
5. Click the Advanced Parameters arrow.
6. Specify the Custom CPU Type and click OK.

6.13.10. Importing a Red Hat KVM Guest Image

Procedure

1. Download the most recent KVM virtual machine image from the Download Red Hat Enterprise Linux list, in the Product Software tab.
2. Upload the virtual machine image using the Manager or the REST API. See Uploading Images to a Data Storage Domain in the Administration Guide.
3. Create a new virtual machine and attach the uploaded disk image to it. See Creating a Linux virtual machine.
4. Optionally, use cloud-init to configure the virtual machine. See Using Cloud-Init to Automate the Configuration of Virtual Machines for details.
5. Optionally, create a template from the virtual machine. You can generate new virtual machines from this template. See Templates for information about creating templates and generating virtual machines from templates.

6.14.1. Live Migration Prerequisites

This is one in a series of topics that show how to set up and configure SR-IOV on Red Hat Virtualization. For more information, see Setting Up and Configuring SR-IOV

• The source and destination hosts are members of the same cluster, ensuring CPU compatibility between them.

Live migrating virtual machines between different clusters is generally not recommended.

• The source and destination hosts’ status is Up.
• The source and destination hosts have access to the same virtual networks and VLANs.
• The source and destination hosts have access to the data storage domain on which the virtual machine resides.
• The destination host has sufficient CPU capacity to support the virtual machine’s requirements.
• The destination host has sufficient unused RAM to support the virtual machine’s requirements.
• The migrating virtual machine does not have the cache!=none custom property set.

6.14.2. Configuring Virtual Machines with SR-IOV-Enabled vNICs to Reduce Network Outage during Migration

1. Ensure that the destination host has an available VF.
2. Set the Passthrough and Migratable options in the passthrough vNIC’s profile. See Enabling Passthrough on a vNIC Profile in the Administration Guide.
3. Enable hotplugging for the virtual machine’s network interface.
4. Ensure that the virtual machine has a backup VirtIO vNIC, in addition to the passthrough vNIC, to maintain the virtual machine’s network connection during migration.
5. Set the VirtIO vNIC’s No Network Filter option before configuring the bond. See Explanation of Settings in the VM Interface Profile Window in the Administration Guide.

6. Add both vNICs as slaves under an active-backup bond on the virtual machine, with the passthrough vNIC as the primary interface.

   The bond and vNIC profiles can be configured in one of the following ways:

   • The bond is not configured with fail_over_mac=active and the VF vNIC is the primary slave (recommended).

     Disable the VirtIO vNIC profile’s MAC-spoofing filter to ensure that traffic passing through the VirtIO vNIC is not dropped because it uses the VF vNIC MAC address.

   • The bond is configured with fail_over_mac=active.

     This failover policy ensures that the MAC address of the bond is always the MAC address of the active slave. During failover, the virtual machine’s MAC address changes, with a slight disruption in traffic.

6.14.3. Configuring Virtual Machines with SR-IOV-Enabled vNICs with minimal downtime

1. Create a vNIC profile with SR-IOV enabled vNICS. See Creating a vNIC profile and Setting up and configuring SR-IOV.
2. In the Administration Portal, go to → , select the vNIC profile, click Edit and select a Failover vNIC profile from the drop down list.
3. Click OK to save the profile settings.

4. Hotplug a network interface with the failover vNIC profile you created into the virtual machine, or start a virtual machine with this network interface plugged in.

   The virtual machine has three network interfaces: a controller interface and two secondary interfaces. The controller interface must be active and connected in order for migration to succeed.

5. For automatic deployment of virtual machines with this configuration, use the following udev rule:

     UBSYSTEM=="net",
     ACTION=="add|change",
     ENV{ID_NET_DRIVER}!="net_failover",
     ENV{NM_UNMANAGED}="1",
     RUN+="/bin/sh -c '/sbin/ip link set up $INTERFACE'"

   This udev rule works only on systems that manage interfaces with NetworkManager. This rule ensures that only the controller interface is activated.

6.14.4. Optimizing Live Migration

The Auto Converge migrations and Enable migration compression options are available for cluster levels 4.2 or earlier.

For cluster levels 4.3 or later, auto converge is enabled by default for all built-in migration policies, and migration compression is enabled by default for only the Suspend workload if needed migration policy. You can change these parameters when adding a new migration policy, or by modifying the MigrationPolicies configuration value.

Procedure

1. Enable auto-convergence at the global level:

   # engine-config -s DefaultAutoConvergence=True

   1. Enable migration compression at the global level:

      # engine-config -s DefaultMigrationCompression=True

   2. Restart the ovirt-engine service to apply the changes:

      # systemctl restart ovirt-engine.service

2. Configure the optimization settings for a cluster:

   1. Click → and select a cluster.
   2. Click Edit.
   3. Click the Migration Policy tab.
   4. From the Auto Converge migrations list, select Inherit from global setting, Auto Converge, or Don’t Auto Converge.
   5. From the Enable migration compression list, select Inherit from global setting, Compress, or Don’t Compress.
   6. Click OK.

3. Configure the optimization settings at the virtual machine level:

   1. Click → and select a virtual machine.
   2. Click Edit.
   3. Click the Host tab.
   4. From the Auto Converge migrations list, select Inherit from cluster setting, Auto Converge, or Don’t Auto Converge.
   5. From the Enable migration compression list, select Inherit from cluster setting, Compress, or Don’t Compress.
   6. Click OK.

6.14.5. Guest Agent Hooks

• Before migration
• After migration
• Before hibernation
• After hibernation

6.14.6. Automatic Virtual Machine Migration

6.14.7. Preventing Automatic Migration of a Virtual Machine

1. Click → and select a virtual machine.
2. Click Edit.
3. Click the Host tab.

4. In the Start Running On section, select Any Host in Cluster or Specific Host(s), which enables you to select multiple hosts.

   Explicitly assigning a virtual machine to a specific host and disabling migration are mutually exclusive with Red Hat Virtualization high availability.

   If the virtual machine has host devices directly attached to it, and a different host is specified, the host devices from the previous host will be automatically removed from the virtual machine.

5. Select Allow manual migration only or Do not allow migration from the Migration Options drop-down list.
6. Click OK.

6.14.8. Manually Migrating Virtual Machines

When you place a host into maintenance mode, the virtual machines running on that host are automatically migrated to other hosts in the same cluster. You do not need to manually migrate these virtual machines.

Live migrating virtual machines between different clusters is generally not recommended.

Procedure

1. Click → and select a running virtual machine.
2. Click Migrate.

3. Use the radio buttons to select whether to Select Host Automatically or to Select Destination Host, specifying the host using the drop-down list.

   When the Select Host Automatically option is selected, the system determines the host to which the virtual machine is migrated according to the load balancing and power management rules set up in the scheduling policy.

4. Click OK.

6.14.9. Setting Migration Priority

1. Click → and select a virtual machine.
2. Click Edit.
3. Select the High Availability tab.
4. Select Low, Medium, or High from the Priority drop-down list.
5. Click OK.

6.14.10. Canceling Ongoing Virtual Machine Migrations

Procedure

1. Select the migrating virtual machine. It is displayed in → with a status of Migrating from.
2. Click More Actions (
   
   ), then click Cancel Migration.

6.14.11. Event and Log Notification upon Automatic Migration of Highly Available Virtual Servers

Example 6.4. Notification in the Events Tab of the Administration Portal

Example 6.5. Notification in the Manager engine.log

6.15.1. What is High Availability?

• A host becomes non-operational due to hardware failure.
• A host is put into maintenance mode for scheduled downtime.
• A host becomes unavailable because it has lost communication with an external storage resource.

• The virtual machine is shut down from within the guest.
• The virtual machine is shut down from the Manager.
• The host is shut down by an administrator without being put in maintenance mode first.

6.15.2. High Availability Considerations

• Power management must be configured for the hosts running the highly available virtual machines.
• The host running the highly available virtual machine must be part of a cluster which has other available hosts.
• The destination host must be running.
• The source and destination host must have access to the data domain on which the virtual machine resides.
• The source and destination host must have access to the same virtual networks and VLANs.
• There must be enough CPUs on the destination host that are not in use to support the virtual machine’s requirements.
• There must be enough RAM on the destination host that is not in use to support the virtual machine’s requirements.

6.15.3. Configuring a Highly Available Virtual Machine

Procedure

1. Click → and select a virtual machine.
2. Click Edit.
3. Click the High Availability tab.
4. Select the Highly Available check box to enable high availability for the virtual machine.

5. Select the storage domain to hold the virtual machine lease, or select No VM Lease to disable the functionality, from the Target Storage Domain for VM Lease drop-down list. See What is high availability for more information about virtual machine leases.

   This functionality is only available on storage domains that are V4 or later.

6. Select AUTO_RESUME, LEAVE_PAUSED, or KILL from the Resume Behavior drop-down list. If you defined a virtual machine lease, KILL is the only option available. For more information see Virtual Machine High Availability settings explained.
7. Select Low, Medium, or High from the Priority drop-down list. When migration is triggered, a queue is created in which the high priority virtual machines are migrated first. If a cluster is running low on resources, only the high priority virtual machines are migrated.
8. Click OK.

6.16.1. Enabling SAP Monitoring

1. Click → and select a virtual machine.
2. Click Edit.
3. Click the Custom Properties tab.

4. Select sap_agent from the drop-down list. Ensure the secondary drop-down menu is set to True.

   If previous properties have been set, select the plus sign to add a new property rule and select sap_agent.

5. Click OK.

6.16.2. Configuring Red Hat Enterprise Linux 5.4 and later Virtual Machines to use SPICE

Typically, this is most useful for virtual machines where the user requires the use of the graphical user interface. System administrators who are creating virtual servers may prefer not to configure SPICE if their use of the graphical user interface is minimal.

6.16.3. KVM Virtual Machine Timing Management

• Clocks can fall out of synchronization with the actual time which invalidates sessions and affects networks.
• Virtual machines with slower clocks may have issues migrating.

The Network Time Protocol (NTP) daemon should be running on the host and the virtual machines. Enable the ntpd service and add it to the default startup sequence:

# service ntpd start
# chkconfig ntpd on

# systemctl start ntpd.service
# systemctl enable ntpd.service

Using the ntpd service should minimize the affects of clock skew in all cases.

The NTP servers you are trying to use must be operational and accessible to your hosts and virtual machines.

These instructions are for AMD revision F CPUs only.

The process of configuring kernel parameters can be automated using the ktune package

6.16.4. Adding a Trusted Platform Module device

If there is TPM data stored for the virtual machine and the TPM device is disabled in the virtual machine, the TPM data is permanently removed.

1. In the Add Virtual Machine or Edit Virtual Machine screen, click Show Advanced Options.
2. In the Resource Allocation tab, select the TPM Device Enabled check box.

• TPM devices can only be used on x86_64 machines with UEFI firmware and PowerPC machines with pSeries firmware installed.
• Virtual machines with TPM devices can not have snapshots with memory.

• While the Manager retrieves and stores TPM data periodically, there is no guarantee that the Manager will always have the latest version of the TPM data.

  This process can take 120 seconds or more, and you must wait for the process to complete before you can take snapshot of a running virtual machine, clone a running virtual machine, or migrate a running virtual machine.

• TPM devices can only be enabled for virtual machines running RHEL 7 or later and Windows 8.1 or later.
• Virtual machines and templates with TPM data can not be exported or imported.

7.2.1. Sealing a Linux Virtual Machine for Deployment as a Template

In RHV 4.4, to seal a RHEL 8 virtual machine for a template, its cluster level must be 4.4 and all hosts in the cluster must be based on RHEL 8. You cannot seal a RHEL 8 virtual machine if you have set its cluster level to 4.3 so it can run on RHEL 7 hosts.

7.2.2. Sealing a Windows Virtual Machine for Deployment as a Template

7.6.1. Migrating Templates to the Export Domain

The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disks, and templates can then be uploaded from the imported storage domain to the attached data center. See the Importing Existing Storage Domains section in the Red Hat Virtualization Administration Guide for information on importing storage domains.

1. Click → and select a template.
2. Click Export.
3. Select the Force Override check box to replace any earlier version of the template on the export domain.
4. Click OK to begin exporting the template; this may take up to an hour, depending on the virtual disk size and your storage hardware.

1. Click → and select the export domain.
2. Click the domain name to see the details view.
3. Click the Template Import tab to view all exported templates in the export domain.

7.6.2. Copying a Template’s Virtual Hard Disk

1. Click → .
2. Select the template disk(s) to copy.
3. Click Copy.
4. Select the Target data domain from the drop-down list(s).
5. Click OK.

7.7.1. Importing a Template into a Data Center

The export storage domain is deprecated. Storage data domains can be unattached from a data center and imported to another data center in the same environment, or in a different environment. Virtual machines, floating virtual disks, and templates can then be uploaded from the imported storage domain to the attached data center. See the Importing Existing Storage Domains section in the Red Hat Virtualization Administration Guide for information on importing storage domains.

1. Click → and select the newly attached export domain.
2. Click the domain name to go to the details view.
3. Click the Template Import tab and select a template.
4. Click Import.
5. Use the drop-down lists to select the Target Cluster and CPU Profile.
6. Select the template to view its details, then click the Disks tab and select the Storage Domain to import the template into.
7. Click OK.
8. If the Import Template Conflict window appears, enter a New Name for the template, or select the Apply to all check box and enter a Suffix to add to the cloned Templates. Click OK.
9. Click Close.

7.7.2. Importing a Virtual Disk from an OpenStack Image Service as a Template

1. Click → and select the OpenStack Image Service domain.
2. Click the storage domain name to go to the details view.
3. Click the Images tab and select the image to import.

4. Click Import.

   If you are importing an image from a Glance storage domain, you have the option of specifying the template name. OpenStack Glance is now deprecated. This functionality will be removed in a later release.

5. Select the Data Center into which the virtual disk will be imported.
6. Select the storage domain in which the virtual disk will be stored from the Domain Name drop-down list.
7. Optionally, select a Quota to apply to the virtual disk.
8. Select the Import as Template check box.
9. Select the Cluster in which the virtual disk will be made available as a template.
10. Click OK.

7.8.1. Managing System Permissions for a Template

• Create, edit, export, and remove associated templates.
• Import and export templates.

You can only assign roles and permissions to existing users.

7.8.2. Template Administrator Roles Explained

Table 7.1. Red Hat Virtualization System Administrator Roles

7.8.3. Assigning an Administrator or User Role to a Resource

Procedure

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the resource’s name to go to the details view.
3. Click the Permissions tab to list the assigned users, the user’s role, and the inherited permissions for the selected resource.
4. Click Add.
5. Enter the name or user name of an existing user into the Search text box and click Go. Select a user from the resulting list of possible matches.
6. Select a role from the Role to Assign: drop-down list.
7. Click OK.

7.8.4. Removing an Administrator or User Role from a Resource

1. Use the resource tabs, tree mode, or the search function to find and select the resource in the results list.
2. Click the resource’s name to go to the details view.
3. Click the Permissions tab to list the assigned users, the user’s role, and the inherited permissions for the selected resource.
4. Select the user to remove from the resource.
5. Click Remove. The Remove Permission window opens to confirm permissions removal.
6. Click OK.

7.9.1. Cloud-Init Use Case Scenarios

• Virtual Machines Created Based on Templates

  You can use the Cloud-Init options in the Initial Run section of the Run Once window to initialize a virtual machine that was created based on a template. This allows you to customize the virtual machine the first time that virtual machine is started.

• Virtual Machine Templates

  You can use the Use Cloud-Init/Sysprep options in the Initial Run tab of the Edit Template window to specify options for customizing virtual machines created based on that template.

• Virtual Machine Pools

  You can use the Use Cloud-Init/Sysprep options in the Initial Run tab of the New Pool window to specify options for customizing virtual machines taken from that virtual machine pool. This allows you to specify a set of standard settings that will be applied every time a virtual machine is taken from that virtual machine pool. You can inherit or override the options specified for the template on which the virtual machine is based, or specify options for the virtual machine pool itself.

7.9.2. Installing Cloud-Init

1. Log in to the virtual machine.

2. Enable the repositories:

   • For Red Hat Enterprise Linux 6:

     # subscription-manager repos 
         --enable=rhel-6-server-rpms 
         --enable=rhel-6-server-rh-common-rpms

   • For Red Hat Enterprise Linux 7:

     # subscription-manager repos 
         --enable=rhel-7-server-rpms 
         --enable=rhel-7-server-rh-common-rpms

   • For Red Hat Enterprise Linux 8, you normally do not need to enable repositories to install Cloud-Init. The Cloud-Init package is part of the AppStream repo, rhel-8-for-x86_64-appstream-rpms, which is enabled by default in Red Hat Enterprise Linux 8.

3. Install the cloud-init package and dependencies:

   # dnf install cloud-init

   For versions of Red Hat Enterprise Linux earlier than version 8, use the command yum install cloud-init instead of dnf install cloud-init.

7.9.3. Using Cloud-Init to Prepare a Template

While the following procedure outlines how to use Cloud-Init when preparing a template, the same settings are also available in the New Virtual Machine, Edit Template, and Run Once windows.

1. Click → and select a template.
2. Click Edit.
3. Click Show Advanced Options
4. Click the Initial Run tab and select the Use Cloud-Init/Sysprep check box.
5. Enter a host name in the VM Hostname text field.
6. Select the Configure Time Zone check box and select a time zone from the Time Zone drop-down list.

7. Expand the Authentication section.

   • Select the Use already configured password check box to use the existing credentials, or clear that check box and enter a root password in the Password and Verify Password text fields to specify a new root password.
   • Enter any SSH keys to be added to the authorized hosts file on the virtual machine in the SSH Authorized Keys text area.
   • Select the Regenerate SSH Keys check box to regenerate SSH keys for the virtual machine.

8. Expand the Networks section.

   • Enter any DNS servers in the DNS Servers text field.
   • Enter any DNS search domains in the DNS Search Domains text field.

   • Select the In-guest Network Interface check box and use the + Add new and — Renove selected buttons to add or remove network interfaces to or from the virtual machine.

     You must specify the correct network interface name and number (for example, eth0, eno3, enp0s). Otherwise, the virtual machine’s interface connection will be up, but it will not have the cloud-init network configuration.

9. Expand the Custom Script section and enter any custom scripts in the Custom Script text area.
10. Click OK.

7.9.4. Using Cloud-Init to Initialize a Virtual Machine

1. Click → and select a virtual machine.
2. Click the Run drop-down button and select Run Once.
3. Expand the Initial Run section and select the Cloud-Init check box.
4. Enter a host name in the VM Hostname text field.
5. Select the Configure Time Zone check box and select a time zone from the Time Zone drop-down menu.
6. Select the Use already configured password check box to use the existing credentials, or clear that check box and enter a root password in the Password and Verify Password text fields to specify a new root password.
7. Enter any SSH keys to be added to the authorized hosts file on the virtual machine in the SSH Authorized Keys text area.
8. Select the Regenerate SSH Keys check box to regenerate SSH keys for the virtual machine.
9. Enter any DNS servers in the DNS Servers text field.
10. Enter any DNS search domains in the DNS Search Domains text field.

11. Select the Network check box and use the + and — buttons to add or remove network interfaces to or from the virtual machine.

    You must specify the correct network interface name and number (for example, eth0, eno3, enp0s). Otherwise, the virtual machine’s interface connection will be up, but the cloud-init network configuration will not be defined in it.

12. Enter a custom script in the Custom Script text area. Make sure the values specified in the script are appropriate. Otherwise, the action will fail.
13. Click OK.

To check if a virtual machine has Cloud-Init installed, select a virtual machine and click the Applications sub-tab. Only shown if the guest agent is installed.

7.10.1. Configuring Sysprep on a Template

Do not reboot the virtual machine while Sysprep is running.

Prerequisites

• The Windows virtual machine parameters have been correctly defined.

  If not, click → , click Edit, and enter the required information in the Operating System and Cluster fields.

• The correct product key has been defined in an override file on the Manager.

1. Build the Windows virtual machine with the required patches and software.
2. Seal the Windows virtual machine. See Sealing Virtual Machines in Preparation for Deployment as Templates
3. Create a template based on the Windows virtual machine. See Creating a template from an existing virtual machine
4. Update the Sysprep file with a text editor if additional changes are required.

7.10.2. Using Sysprep to Initialize a Virtual Machine

Using Sysprep to Initialize a Virtual Machine

This procedure starts a virtual machine with a set of Sysprep settings. If the relevant settings are included in the template the virtual machine is based on, review the settings and make changes where required.

1. Create a new Windows virtual machine based on a template of the required Windows virtual machine. See Creating a Virtual Machine Based on a Template.
2. Click → and select the virtual machine.
3. Click the Run drop-down button and select Run Once.
4. Expand the Boot Options section, select the Attach Floppy check box, and select the [sysprep] option.
5. Select the Attach CD check box and select the required Windows ISO from the drop-down list.
6. Move the CD-ROM to the top of the Boot Sequence field.
7. Configure any further Run Once options as required. See Virtual Machine Run Once settings explained for more details.
8. Click OK.