Skip to content

Commit 9cb7d23

Browse files
authored
Merge pull request #69791 from ousleyp/rhelmachinetype-bugfix
CNV#36931: Updating machine type section for 4.14+
2 parents 2e13ac3 + 1fef880 commit 9cb7d23

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

modules/virt-rhel-9.adoc

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,14 +10,12 @@
1010

1111
As in previous versions, you can perform the update without disrupting running workloads. {VirtProductName} {VirtVersion} supports live migration from {op-system-base} 8 nodes to {op-system-base} 9 nodes.
1212

13-
[id="new-rhel-9-machine-type_{context}"]
14-
== New {op-system-base} 9 machine type
13+
[id="rhel-9-machine-type_{context}"]
14+
== {op-system-base} 9 machine type
1515

16-
This update also introduces a new {op-system-base} 9 machine type for VMs: `machineType: pc-q35-rhel9.2.0`. All VM templates that are included with {VirtProductName} now use this machine type by default.
16+
All VM templates that are included with {VirtProductName} now use the {op-system-base} 9 machine type by default: `machineType: pc-q35-rhel9.<y>.0`, where `<y>` is a single digit corresponding to the latest minor version of {op-system-base} 9. For example, the value `pc-q35-rhel9.2.0` is used for {op-system-base} 9.2.
1717

18-
Updating {VirtProductName} does not change the `machineType` value of any existing VMs. These VMs continue to function as they did before the update.
19-
20-
While it is not required, you might want to change a VM's machine type to `pc-q35-rhel9.2.0` so that it can benefit from {op-system-base} 9 improvements.
18+
Updating {VirtProductName} does not change the `machineType` value of any existing VMs. These VMs continue to function as they did before the update. You can optionally change a VM's machine type so that it can benefit from {op-system-base} 9 improvements.
2119

2220
[IMPORTANT]
2321
====

0 commit comments

Comments
 (0)