Skip to content

Commit 9de63e5

Browse files
authored
Merge pull request #48696 from apinnick/more-create-template-fixes
Removing wizard references and other fixes.
2 parents f0a230c + b8a0606 commit 9de63e5

6 files changed

+11
-11
lines changed

modules/virt-adding-a-boot-source-web.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ There are four methods for selecting and adding a boot source in the web console
3434
. In the *Add disk* window, select *Use this disk as a boot source*.
3535
. Enter the disk name and select a *Source*, for example, *Blank (creates PVC)* or *Use an existing PVC*.
3636
. Enter a value for *Persistent Volume Claim size* to specify the PVC size that is adequate for the uncompressed image and any additional space that is required.
37-
. Select a *Type*, for example, *Disk*, which is required for hot-plugging, or *CD-ROM*.
37+
. Select a *Type*, for example, *Disk* or *CD-ROM*.
3838
. Optional: Click *Storage class* and select the storage class that is used to create the disk. Typically, this storage class is the default storage class that is created for use by all PVCs.
3939
+
4040
[NOTE]
@@ -52,4 +52,4 @@ Provided boot sources are updated automatically to the latest version of the ope
5252

5353
.. Click *Save and clone* if you cloned an existing PVC.
5454

55-
Your custom virtual machine template with a boot source is listed on the *Catalog* page. You can use this template to quick create a virtual machine.
55+
Your custom virtual machine template with a boot source is listed on the *Catalog* page. You can use this template to create a virtual machine.

modules/virt-assign-vgpu-passthrough-to-vm.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Use the {product-title} web console to assign vGPU passthrough devices to your v
1717
. Select the virtual machine to which you want to assign the device.
1818
. On the *Details* tab, click *GPU devices*.
1919
+
20-
If you add a vGPU device as a host device, you cannot access the device with VNC console.
20+
If you add a vGPU device as a host device, you cannot access the device with the VNC console.
2121

2222
. Click *Add GPU device*, enter the *Name* and select the device from the *Device name* list.
2323
. Click *Save*.

modules/virt-creating-a-vm-from-a-template-with-an-attached-boot-source.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,5 +12,5 @@ After you add a boot source to a template, you can create a virtual machine from
1212

1313
. In the {product-title} web console, click *Virtualization* -> *Catalog* in the side menu.
1414
. Select the updated template and click *Quick create VirtualMachine*.
15-
+
15+
1616
The *VirtualMachine details* is displayed with the status *Starting*.

modules/virt-enabling-dedicated-resources.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ endif::[]
2222
[id="virt-enabling-dedicated-resources_{context}"]
2323
= Enabling dedicated resources for a {object}
2424

25-
You enable dedicated resources for a {object} in the *Details* tab. Virtual machines that were created froma Red Hat template can be configured with dedicated resources.
25+
You enable dedicated resources for a {object} in the *Details* tab. Virtual machines that were created from a Red Hat template can be configured with dedicated resources.
2626

2727
.Procedure
2828

modules/virt-specializing-windows-sysprep.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,12 +16,12 @@ Specializing a virtual machine (VM) configures the computer-specific information
1616
.Procedure
1717

1818
. In the {product-title} console, click *Virtualization* -> *Catalog*.
19-
. Select a Windows template and click *Customize VirtualMachine*
19+
. Select a Windows template and click *Customize VirtualMachine*.
2020
. Select *PVC (clone PVC)* from the *Disk source* list.
2121
. Specify the *Persistent Volume Claim project* and *Persistent Volume Claim name* of the generalized Windows image.
2222
. Click *Review and create VirtualMachine*.
2323
. Click the *Scripts* tab.
2424
. In the *Sysprep* section, click *Edit*, browse to the `unattend.xml` answer file, and click *Save*.
2525
. Click *Create VirtualMachine*.
26-
+
26+
2727
During the initial boot, Windows uses the `unattend.xml` answer file to specialize the VM. The VM is now ready to use.

modules/virt-using-disk-image-install-windows.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,8 @@ You can use a disk image to install Windows on your virtual machine.
1515
1616
.Procedure
1717

18-
. In the {product-title} console, click *Virtualization* -> *Catalog* from the side menu
19-
. Select a Windows template and then click *Customize VirtualMachine*.
18+
. In the {product-title} console, click *Virtualization* -> *Catalog* from the side menu.
19+
. Select a Windows template and click *Customize VirtualMachine*.
2020
. Select *Upload (Upload a new file to a PVC)* from the *Disk source* list and browse to the DVD image.
2121
. Click *Review and create VirtualMachine*.
2222
. Clear *Clone available operating system source to this Virtual Machine*.
@@ -25,5 +25,5 @@ You can use a disk image to install Windows on your virtual machine.
2525
. Browse to the `autounattend.xml` answer file and click *Save*.
2626
. Click *Create VirtualMachine*.
2727
. On the *YAML* tab, replace `running:false` with `runStrategy: RerunOnFailure` and click *Save*.
28-
+
29-
The VM will start with the `sysprep` disk containing the `autounattend.xml` answer file is now attached to the VM.
28+
29+
The VM will start with the `sysprep` disk containing the `autounattend.xml` answer file.

0 commit comments

Comments
 (0)