How to create Win 11 Instance.

[CricutTech]

I am not finding much on how to create a Win 11 Instance.  I get the "Windows won't run on this hardware" error message when I try.  So it's either TPM 2.0 (which I confirmed is enabled in the host's BIOS) or UEFI / secure boot or something else.  Is it possible?  What's the trick?  Thanks.

PT

[jamgwert81 · Accepted solution]

I just ran into this issue myself trying to load a Windows 11 24H2 vm from the ISO.  I'm a total noob for this product coming over from VMware so this is like relearning some of the most basic stuff.

I believe when you import the ISO you have to check these three options.  Or if you've already imported it, click to Edit it and check them.  I just tested this and it appears to work, and lets you get past the screen you were talking about where the Windows installer doesn't think it meets the requirements.

I too am confused as to why these settings are not available\configurable on the VM you deploy, but rather need to be set on the Virtual Image before you deploy it.

[CricutTech]

That fixed it!  Thank you.
I was getting worried we bought a "server only" solution for our VMware replacement.

[dya]

Hello

Those settings appear to relate to the virtual machine configuration.

Incidentally, at the current time (8.0.9), Windows 11 installation was possible even with the following settings:

■VIRTO DRIVERS LOADED?
■UEFI
▢VTPM ENABLED
▢SECURE BOOT

Checking with `virsh dumpxml` revealed that
checking “UEFI” enables VTPM. Also, whether “SECURE BOOT” is checked or not makes no difference; it appears secure boot is not officially supported.

Translated with DeepL.com (free version)

[jamgwert81]

I tested this again with 24H2, and yes it appears that only UEFI is required on 8.0.9.  As you stated it must be adding the VTPM without telling you in the UI.  I'm wondering if it's supposed to be doing that or if that is a bug.  If it's not a bug, then I'm not sure what the VTPM option is doing in the UI.  I'd expect this to possibly be fixed in a future version.  A TPM of some sort is required on Windows 11.

It would be great to be able to have control over adding a VTPM and enable\disable of Secure Boot options after a VM is deployed.  I don't believe a TPM is required for the install of a WIndows Server OS, but it is required to take advantage of Bitlocker if you were to configure that.  I also wouldn't be surprised if this non-requirement of a TPM changes on future versions of the server OS.  There are certain scenarios where one might want to add a VTPM after the fact, like an in-place upgrade of a Windows vm and the new version of Windows requiring it (ie Win10 upgrading to Win 11).  I understand migration is typically performed to a newer VM but I can tell you from experience there are instances of where one will choose an in-place upgrade on a deployed vm.  Like when the VM is running applications or services where it is a bigger headache to migrate (ie User Desktop VMs).  Being able to add a VTPM to perform the upgrade would be beneficial in those instances.

[kwarnimo]

+1 on adding a vTPM to an existing instance.  I'm *guessing* I could take a backup of the VM, import it as an image, redeploy it as a new VM with vTPM enabled and be set but a cleaner approach would be nice.  

[dya]

https://community.hpe.com/t5/hpe-morpheus-vm-essentials/virtual-image-advanced-options-2/td-p/7254191https://community.hpe.com/t5/hpe-morpheus-vm-essentials/仮想イメージ-advanced-options-2/td-p/7254191

Regarding VTPM and Secure Boot, there was no clear answer, but we expect improvements in the future.