bhyve windows 11 on bhyve

I have just upgraded some of our virtual desktop environments using https://github.com/builtbybel/Flyby11

So whoever uses a Windows 10 VM and wants to do in-place upgrades to Windows 11 - I can recommend this tool. It switches off some checks, like the one for compatibility by having a TPM 2.0 chip.
 
I run Win10 routinely in ESXi virtual machines without a hitch.

Does BHYVE offer a similar installation, where the VM host type is selected at creation time?
 
jbo@ said:
I don't know... might be just me - but somehow I trust these sorts of tools even less than Microsoft.
Click to expand...
me neither, however, my trust in fumbling around in the registry as described by some random "how to bypass windows 11 checks" posts or article is just a little higher. We'll see what happens if Win 11 25H2 is released. I hope we have a stable TPM 2.0 emulation with FreeBSD/bhyve.

bgavin said:
I run Win10 routinely in ESXi virtual machines without a hitch.

Does BHYVE offer a similar installation, where the VM host type is selected at creation time?
Click to expand...
Windows 10 is no problem with bhyve. However, Windows 11 is because it checks various things, and one of the official requirements for Windows 11 to run is a TPM 2.0 chip - and FreeBSD/bhyve does not offer TPM 2.0 emulation.
 
kenrap said:
We already have a functional TPM driver that works on Windows 11: tpm(4)

And add it to your kld_list for convenience.

Assuming you use vm-bhyve, plop this into your Windows 11 VM config:
Code: 
bhyve_options="-l tpm,passthru,/dev/tpm0"
(Look ma, no registry hacking!)
Click to expand...
Yes it works! I installed windows 11 from win11.img, not from usb, because when installing windows 11 it freezes if you do passthru usb host controller. I did the following: sudo dd if=/dev/da0 of=win11.img bs=4m status=progress, and then set it as a secondary hdd in bhyve cmd line. I also set one processor with 16 cores one thread each. During install I did not set an activation key, I activated windows after it was installed. Then I changed bhyve cmd (see attached picture). All works (but slowly). ...I haven't tried 'passthru' usb controller yet.

w11_bhyve.png
 
You probably want to change your CPU config so you don't end up with two sockets in the Windows 11 guest.

It's a licensing nightmare.
 
jbo@ said:
You probably want to change your CPU config so you don't end up with two sockets in the Windows 11 guest.

It's a licensing nightmare.
Click to expand...
I have retail license, not OEM (if it somehow affects the situation). I set license right after install (with one processor), and now it continues to work (with two sockets).

:-/
 
You must log in or register to reply here.
Back
Top