$ yum install -y qemu-guest-agent
The QEMU guest agent is a daemon that runs on the virtual machine and passes information to the host about the virtual machine, users, file systems, and secondary networks.
The qemu-guest-agent is widely available and available by default in Red Hat Enterprise Linux (RHEL) virtual machines (VMs). Install the agent and start the service.
|
To create snapshots of an online (Running state) VM with the highest integrity, install the QEMU guest agent. The QEMU guest agent takes a consistent snapshot by attempting to quiesce the VM’s file system as much as possible, depending on the system workload. This ensures that in-flight I/O is written to the disk before the snapshot is taken. If the guest agent is not present, quiescing is not possible and a best-effort snapshot is taken. The conditions under which the snapshot was taken are reflected in the snapshot indications that are displayed in the web console or CLI. |
Access the virtual machine command line through one of the consoles or by SSH.
Install the QEMU guest agent on the virtual machine:
$ yum install -y qemu-guest-agent
Ensure the service is persistent and start it:
$ systemctl enable --now qemu-guest-agent
Run the following command to verify that AgentConnected is listed in the VM spec:
$ oc get vm <vm_name>
For Windows virtual machines, the QEMU guest agent is included in the VirtIO drivers. Install the drivers on an existing or a new Windows installation.
|
To create snapshots of an online (Running state) VM with the highest integrity, install the QEMU guest agent. The QEMU guest agent takes a consistent snapshot by attempting to quiesce the VM’s file system as much as possible, depending on the system workload. This ensures that in-flight I/O is written to the disk before the snapshot is taken. If the guest agent is not present, quiescing is not possible and a best-effort snapshot is taken. The conditions under which the snapshot was taken are reflected in the snapshot indications that are displayed in the web console or CLI. |
In the Windows Guest Operating System (OS), use the File Explorer to navigate to the guest-agent directory in the virtio-win CD drive.
Run the qemu-ga-x86_64.msi installer.
Run the following command to verify that the output contains the QEMU Guest Agent:
$ net start
| Driver name | Hardware ID | Description |
|---|---|---|
viostor |
VEN_1AF4&DEV_1001 |
The block driver. Sometimes displays as an SCSI Controller in the Other devices group. |
viorng |
VEN_1AF4&DEV_1005 |
The entropy source driver. Sometimes displays as a PCI Device in the Other devices group. |
NetKVM |
VEN_1AF4&DEV_1000 |
The network driver. Sometimes displays as an Ethernet Controller in the Other devices group. Available only if a VirtIO NIC is configured. |
VirtIO drivers are paravirtualized device drivers required for Microsoft Windows
virtual machines to run in OpenShift Virtualization. The supported drivers are
available in the container-native-virtualization/virtio-win container disk of the
Red Hat Ecosystem Catalog.
The container-native-virtualization/virtio-win container disk must be attached to the virtual machine as a
SATA CD drive to enable driver installation. You can install VirtIO drivers during
Windows installation on the virtual machine or added to an
existing Windows installation.
After the drivers are installed, the container-native-virtualization/virtio-win container disk can be removed
from the virtual machine.
Install the VirtIO drivers from the attached SATA CD drive to an existing Windows virtual machine.
|
This procedure uses a generic approach to adding drivers to Windows. The process might differ slightly between versions of Windows. See the installation documentation for your version of Windows for specific installation steps. |
Start the virtual machine and connect to a graphical console.
Log in to a Windows user session.
Open Device Manager and expand Other devices to list any Unknown device.
Open the Device Properties to identify the unknown device.
Right-click the device and select Properties.
Click the Details tab and select Hardware Ids in the Property list.
Compare the Value for the Hardware Ids with the supported VirtIO drivers.
Right-click the device and select Update Driver Software.
Click Browse my computer for driver software and browse to the attached SATA CD drive, where the VirtIO drivers are located. The drivers are arranged hierarchically according to their driver type, operating system, and CPU architecture.
Click Next to install the driver.
Repeat this process for all the necessary VirtIO drivers.
After the driver installs, click Close to close the window.
Reboot the virtual machine to complete the driver installation.
Install the virtio drivers during or after Windows installation.
|
This procedure uses a generic approach to the Windows installation and the installation method might differ between versions of Windows. See the documentation for the version of Windows that you are installing. |
A storage device containing the virtio drivers must be attached to the VM.
In the Windows Guest OS, use the File Explorer to navigate to the virtio-win CD drive.
Double-click to run the appropriate installer for your VM:
For a 64-bit vCPU, use the virtio-win-gt-x64 installer. 32-bit vCPUs are no longer supported.
Optional: During the Custom Setup step of the installer, select the device drivers you want to install. The recommended driver set is selected by default.
After the installation is complete, select Finish.
Reboot the VM.
Open the system disk on the PC. This is typically C:.
Navigate to Program Files → Virtio-Win.
If the Virtio-Win directory is present and contains a sub-directory for each driver, the installation was successful.
You can add a VirtIO drivers container disk to a Windows virtual machine (VM) as a SATA CD drive.
VirtIO drivers are paravirtualized device drivers required for Microsoft Windows VMs to run in OpenShift Virtualization.
|
Downloading the |
Add the container-native-virtualization/virtio-win container disk as a CD drive by editing the VirtualMachine manifest:
# ...
spec:
domain:
devices:
disks:
- name: virtiocontainerdisk
bootOrder: 2 (1)
cdrom:
bus: sata
volumes:
- containerDisk:
image: container-native-virtualization/virtio-win
name: virtiocontainerdisk
| 1 | OpenShift Virtualization boots the VM disks in the order defined in the VirtualMachine manifest. You can either define other VM disks that boot before the container-native-virtualization/virtio-win container disk or use the optional bootOrder parameter to ensure the VM boots from the correct disk. If you configure the boot order for a disk, you must configure the boot order for the other disks. |
Apply the changes:
If the VM is not running, run the following command:
$ `virtctl start <vm>`
If the VM is running, reboot the VM or run the following command:
$ run `oc apply -f <vm.yaml>`
After the virtual machine has started, install the VirtIO drivers from the SATA CD drive.
Update the virtio drivers by using Windows Update.
A Windows guest operating system with the virtio drivers must be attached to the virtual machine (VM).
The cluster must be connected to the internet. Disconnected clusters cannot reach the Windows Update service.
In the Windows Guest operating system, use the File Explorer to navigate to Settings → Windows Update → Advanced Options → Optional Updates.
Install all updates from Red Hat, Inc..
Reboot the VM.
On the Windows VM, navigate to the Device Manager.
Select a device.
Select the Driver tab.
Click Driver Details and confirm that the virtio driver details list the correct version.