This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
computing:windows11-vm [2022/07/31 00:24] – oemb1905 | computing:windows11-vm [2022/07/31 00:31] (current) – oemb1905 | ||
---|---|---|---|
Line 31: | Line 31: | ||
{{ : | {{ : | ||
- | The Overview pane allows you to pick a chipset and specify the bootloader you want to use. These options were specified on many Wikis, so I followed suit. After this was done, I then changed the Boot Options so that the CD-ROM was punched, and so that it was at the top of the list. This is because virt-manager interprets the .iso as a CD-ROM and won't find the installer media unless this is done. It might already be set this way on your virt-manager instance but it was not on mine, so big thanks to shawnsg for their tutorial | + | The Overview pane allows you to pick a chipset and specify the bootloader you want to use. These options were specified on many Wikis, so I followed suit. After this was done, I then changed the Boot Options so that the CD-ROM was punched, and so that it was at the top of the list. This is because virt-manager interprets the .iso as a CD-ROM and won't find the installer media unless this is done. It might already be set this way on your virt-manager instance but it was not on mine because |
{{ : | {{ : | ||
+ | Lastly, once virt-manager was configured for using secure boot and to load the installer media, it was now time to configure this virtual machine to use the software based TPM module we created earlier. To do that, I clicked "Add Hardware" | ||
+ | {{ : | ||
- | --- // | + | Once those two environments were built, the ovfm package installed, and virt-manager configured to leverage all of those properly, the machine booted flawlessly. Here's the splash screen after the core parts of the OS installed: |
+ | |||
+ | {{ : | ||
+ | |||
+ | --- // | ||