Skip to content

Commit 2703b18

Browse files
authored
Merge pull request #66773 from apinnick/qemu-virtio-cleanup
VirtIO installation cleanup
2 parents e60cb6d + 89b9bf3 commit 2703b18

9 files changed

+75
-105
lines changed

modules/virt-about-virtio-drivers.adoc

Lines changed: 0 additions & 22 deletions
This file was deleted.

modules/virt-adding-virtio-drivers-vm-yaml.adoc renamed to modules/virt-adding-container-disk-as-cd.adoc

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,20 @@
55
//This file contains UI elements and/or package names that need to be updated.
66

77
:_content-type: PROCEDURE
8-
[id="virt-adding-virtio-drivers-vm-yaml_{context}"]
9-
= Adding VirtIO drivers container disk to a virtual machine
8+
[id="virt-adding-container-disk-as-cd_{context}"]
9+
= Installing VirtIO drivers from a container disk added as a SATA CD drive
1010

11-
You can add a VirtIO drivers container disk to a Windows virtual machine (VM) as a SATA CD drive.
12-
13-
VirtIO drivers are paravirtualized device drivers required for Microsoft Windows VMs to run in {VirtProductName}.
11+
You can install VirtIO drivers from a container disk that you add to a Windows virtual machine (VM) as a SATA CD drive.
1412

1513
[TIP]
1614
====
1715
Downloading the `container-native-virtualization/virtio-win` container disk from the link:https://catalog.redhat.com/software/containers/search?q=virtio-win&p=1[Red Hat Ecosystem Catalog] is not mandatory, because the container disk is downloaded from the Red Hat registry if it not already present in the cluster. However, downloading reduces the installation time.
1816
====
1917

18+
.Prerequisites
19+
20+
* You must have access to the Red Hat registry or to the downloaded `container-native-virtualization/virtio-win` container disk in a restricted environment.
21+
2022
.Procedure
2123

2224
. Add the `container-native-virtualization/virtio-win` container disk as a CD drive by editing the `VirtualMachine` manifest:
@@ -44,14 +46,14 @@ volumes:
4446
+
4547
[source,terminal]
4648
----
47-
$ `virtctl start <vm>`
49+
$ virtctl start <vm>
4850
----
4951

5052
* If the VM is running, reboot the VM or run the following command:
5153
+
5254
[source,terminal]
5355
----
54-
$ run `oc apply -f <vm.yaml>`
56+
$ oc apply -f <vm.yaml>
5557
----
5658
57-
. After the virtual machine has started, install the VirtIO drivers from the SATA CD drive.
59+
. After the VM has started, install the VirtIO drivers from the SATA CD drive.

modules/virt-installing-qemu-guest-agent-on-linux-vm.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,22 +5,22 @@
55

66
:_content-type: PROCEDURE
77
[id="virt-installing-qemu-guest-agent-on-linux-vm_{context}"]
8-
= Installing QEMU guest agent on a Linux virtual machine
8+
= Installing the QEMU guest agent on a Linux VM
99

1010
The `qemu-guest-agent` is widely available and available by default in {op-system-base-full} virtual machines (VMs). Install the agent and start the service.
1111

1212
[NOTE]
1313
====
1414
To create snapshots of an online (Running state) VM with the highest integrity, install the QEMU guest agent.
1515
16-
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.
16+
The QEMU guest agent takes a consistent snapshot by attempting to quiesce the VM 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.
1717
====
1818

1919
.Procedure
2020

21-
. Access the virtual machine command line through one of the consoles or by SSH.
21+
. Log in to the VM by using a console or SSH.
2222

23-
. Install the QEMU guest agent on the virtual machine:
23+
. Install the QEMU guest agent by running the following command:
2424
+
2525
[source,terminal]
2626
----
@@ -35,7 +35,7 @@ $ systemctl enable --now qemu-guest-agent
3535
----
3636

3737
.Verification
38-
. Run the following command to verify that `AgentConnected` is listed in the VM spec:
38+
* Run the following command to verify that `AgentConnected` is listed in the VM spec:
3939
4040
+
4141
[source,terminal]

modules/virt-installing-qemu-guest-agent-on-windows-vm.adoc

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,30 +5,28 @@
55

66
:_content-type: PROCEDURE
77
[id="installing-qemu-guest-agent-on-windows-vm_{context}"]
8-
= Installing QEMU guest agent on a Windows virtual machine
8+
= Installing the QEMU guest agent on a Windows VM
99

10-
For Windows virtual machines, the QEMU guest agent is included in the
11-
VirtIO drivers. Install the drivers on an existing or a new Windows installation.
10+
For Windows virtual machines (VMs), the QEMU guest agent is included in the VirtIO drivers. You can install the drivers during a Windows installation or on an existing Windows VM.
1211

1312
[NOTE]
1413
====
1514
To create snapshots of an online (Running state) VM with the highest integrity, install the QEMU guest agent.
1615
17-
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.
16+
The QEMU guest agent takes a consistent snapshot by attempting to quiesce the VM 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.
1817
====
1918

2019
.Procedure
2120

22-
. In the Windows Guest Operating System (OS), use the *File Explorer* to navigate to the `guest-agent` directory in the `virtio-win` CD drive.
23-
21+
. In the Windows guest operating system, use the *File Explorer* to navigate to the `guest-agent` directory in the `virtio-win` CD drive.
2422
. Run the `qemu-ga-x86_64.msi` installer.
2523

26-
2724
.Verification
28-
. Run the following command to verify that the output contains the `QEMU Guest Agent`:
29-
25+
. Obtain a list of network services by running the following command:
3026
+
3127
[source,terminal]
3228
----
3329
$ net start
34-
----
30+
----
31+
32+
. Verify that the output contains the `QEMU Guest Agent`.

modules/virt-installing-virtio-drivers-existing-windows.adoc

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,28 +5,29 @@
55

66
:_content-type: PROCEDURE
77
[id="virt-installing-virtio-drivers-existing-windows_{context}"]
8-
= Installing VirtIO drivers on an existing Windows virtual machine
8+
= Installing VirtIO drivers from a SATA CD drive on an existing Windows VM
99

10-
Install the VirtIO drivers from the attached SATA CD drive to an
11-
existing Windows virtual machine.
10+
You can install the VirtIO drivers from a SATA CD drive on an existing Windows virtual machine (VM).
1211

1312
[NOTE]
1413
====
15-
This procedure uses a generic approach to adding drivers to Windows.
16-
The process might differ slightly between versions of Windows.
17-
See the installation documentation for your version of Windows
18-
for specific installation steps.
14+
This procedure uses a generic approach to adding drivers to Windows. See the installation documentation for your version of Windows for specific installation steps.
1915
====
2016

17+
.Prerequisites
18+
19+
* A storage device containing the virtio drivers must be attached to the VM as a SATA CD drive.
20+
2121
.Procedure
2222

23-
. Start the virtual machine and connect to a graphical console.
23+
. Start the VM and connect to a graphical console.
2424
. Log in to a Windows user session.
2525
. Open *Device Manager* and expand *Other devices* to list any *Unknown device*.
26-
.. Open the `Device Properties` to identify the unknown device.
27-
Right-click the device and select *Properties*.
26+
.. Open the *Device Properties* to identify the unknown device.
27+
.. Right-click the device and select *Properties*.
2828
.. Click the *Details* tab and select *Hardware Ids* in the *Property* list.
2929
.. Compare the *Value* for the *Hardware Ids* with the supported VirtIO drivers.
30+
3031
. Right-click the device and select *Update Driver Software*.
3132
. Click *Browse my computer for driver software* and browse to the attached
3233
SATA CD drive, where the VirtIO drivers are located. The drivers are arranged
@@ -35,4 +36,4 @@ and CPU architecture.
3536
. Click *Next* to install the driver.
3637
. Repeat this process for all the necessary VirtIO drivers.
3738
. After the driver installs, click *Close* to close the window.
38-
. Reboot the virtual machine to complete the driver installation.
39+
. Reboot the VM to complete the driver installation.

modules/virt-installing-virtio-drivers-installing-windows.adoc

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,19 +2,16 @@
22
//
33
// * virt/backup_restore/virt-managing-vm-snapshots.adoc
44
// * virt/virtual_machines/creating_vms/virt-installing-qemu-guest-agent.adoc
5-
// * virt/virtual_machines/virt-installing-virtio-drivers-on-new-windows-vm.adoc
65

76
:_content-type: PROCEDURE
87
[id="virt-installing-virtio-drivers-installing-windows_{context}"]
98
= Installing VirtIO drivers during Windows installation
109

11-
Install the `virtio` drivers during or after Windows installation.
10+
You can install the VirtIO drivers while installing Windows on a virtual machine (VM).
1211

1312
[NOTE]
1413
====
15-
This procedure uses a generic approach to the Windows installation and the
16-
installation method might differ between versions of Windows. See the
17-
documentation for the version of Windows that you are installing.
14+
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.
1815
====
1916

2017
.Prerequisites
@@ -23,8 +20,8 @@ documentation for the version of Windows that you are installing.
2320
2421
.Procedure
2522

26-
. In the Windows Guest OS, use the `File Explorer` to navigate to the `virtio-win` CD drive.
27-
. Double-click the drive to run the appropriate installer for your VM:
23+
. In the Windows operating system, use the `File Explorer` to navigate to the `virtio-win` CD drive.
24+
. Double-click the drive to run the appropriate installer for your VM.
2825
+
2926
For a 64-bit vCPU, select the `virtio-win-gt-x64` installer. 32-bit vCPUs are no longer supported.
3027

@@ -35,6 +32,6 @@ For a 64-bit vCPU, select the `virtio-win-gt-x64` installer. 32-bit vCPUs are no
3532
.Verification
3633

3734
. Open the system disk on the PC. This is typically `C:`.
38-
. Navigate to *Program Files* -> *Virtio-Win*.
35+
. Navigate to *Program Files* -> *Virtio-Win*.
3936

4037
If the *Virtio-Win* directory is present and contains a sub-directory for each driver, the installation was successful.

modules/virt-supported-virtio-drivers.adoc

Lines changed: 0 additions & 30 deletions
This file was deleted.

modules/virt-updating-virtio-drivers-windows.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,18 @@
55

66
:_content-type: PROCEDURE
77
[id="virt-updating-virtio-drivers-windows_{context}"]
8-
= Updating VirtIO drivers on a Windows guest
8+
= Updating VirtIO drivers on a Windows VM
99

10-
Update the `virtio` drivers by using Windows Update.
10+
Update the `virtio` drivers on a Windows virtual machine (VM) by using the Windows Update service.
1111

1212
.Prerequisites
1313

14-
* A Windows guest operating system with the `virtio` drivers must be attached to the virtual machine (VM).
1514
* The cluster must be connected to the internet. Disconnected clusters cannot reach the Windows Update service.
1615
1716
.Procedure
1817

19-
. In the Windows Guest operating system, use the `File Explorer` to navigate to *Settings* -> *Windows Update* -> *Advanced Options* -> *Optional Updates*.
18+
. In the Windows Guest operating system, click the *Windows* key and select *Settings*.
19+
. Navigate to *Windows Update* -> *Advanced Options* -> *Optional Updates*.
2020
. Install all updates from *Red Hat, Inc.*.
2121
. Reboot the VM.
2222

@@ -25,4 +25,4 @@ Update the `virtio` drivers by using Windows Update.
2525
. On the Windows VM, navigate to the *Device Manager*.
2626
. Select a device.
2727
. Select the *Driver* tab.
28-
. Click *Driver Details* and confirm that the `virtio` driver details list the correct version.
28+
. Click *Driver Details* and confirm that the `virtio` driver details displays the correct version.

virt/virtual_machines/creating_vms/virt-installing-qemu-guest-agent.adoc

Lines changed: 30 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -18,19 +18,43 @@ include::modules/virt-installing-qemu-guest-agent-on-linux-vm.adoc[leveloffset=+
1818
include::modules/virt-installing-qemu-guest-agent-on-windows-vm.adoc[leveloffset=+2]
1919

2020
[id="installing-virtio-drivers"]
21-
== Installing VirtIO drivers
21+
== Installing VirtIO drivers on Windows VMs
2222

23-
include::modules/virt-supported-virtio-drivers.adoc[leveloffset=+2]
23+
VirtIO drivers are paravirtualized device drivers required for Microsoft Windows virtual machines (VMs) to run in {VirtProductName}. The supported drivers are
24+
available in the `container-native-virtualization/virtio-win` container disk of the link:https://catalog.redhat.com/software/containers/search?q=virtio-win&p=1[Red Hat Ecosystem Catalog].
2425

25-
include::modules/virt-about-virtio-drivers.adoc[leveloffset=+2]
26+
The `container-native-virtualization/virtio-win` container disk must be attached to the VM as a SATA CD drive to enable driver installation. You can install VirtIO drivers during Windows installation or added to an existing Windows installation.
2627

27-
include::modules/virt-installing-virtio-drivers-existing-windows.adoc[leveloffset=+2]
28+
After the drivers are installed, the `container-native-virtualization/virtio-win` container disk can be removed from the VM.
29+
30+
.Supported drivers
31+
[options="header"]
32+
|===
33+
|Driver name |Hardware ID |Description
34+
35+
|*viostor*
36+
|VEN_1AF4&DEV_1001 +
37+
VEN_1AF4&DEV_1042
38+
|The block driver. Sometimes labeled as an *SCSI Controller* in the *Other devices* group.
39+
40+
|*viorng*
41+
|VEN_1AF4&DEV_1005 +
42+
VEN_1AF4&DEV_1044
43+
|The entropy source driver. Sometimes labeled as a *PCI Device* in the *Other devices* group.
44+
45+
|*NetKVM*
46+
|VEN_1AF4&DEV_1000 +
47+
VEN_1AF4&DEV_1041
48+
|The network driver. Sometimes labeled as an *Ethernet Controller* in the *Other devices* group. Available only if a VirtIO NIC is configured.
49+
|===
2850

2951
include::modules/virt-installing-virtio-drivers-installing-windows.adoc[leveloffset=+2]
3052

31-
include::modules/virt-adding-virtio-drivers-vm-yaml.adoc[leveloffset=+2]
53+
include::modules/virt-installing-virtio-drivers-existing-windows.adoc[leveloffset=+2]
54+
55+
include::modules/virt-adding-container-disk-as-cd.adoc[leveloffset=+2]
3256

3357
[id="updating-virtio-drivers"]
3458
== Updating VirtIO drivers
3559

36-
include::modules/virt-updating-virtio-drivers-windows.adoc[leveloffset=+2]
60+
include::modules/virt-updating-virtio-drivers-windows.adoc[leveloffset=+2]

0 commit comments

Comments
 (0)