bhyve A solid HOWTO with BHYVE on FreeBSD 14 and Windows 11

jbo@ said:
I am glad to hear that you got it working!

I forgot to point that out explicitly but yeah: With Microsoft Windows you have to specify the sockets, cores and threads explicitly.
As per my recollection, if you only specify the number of CPUs, bhyve creates just N sockets with one core each.
This creates all sorts of issues with Windows guests. The regular Windows desktop editions simply do not support multiple sockets (or more than 2?) and with the Server editions require you to license per socket. Therefore, you end up in a situation where your Windows guest just has one (or two?) CPUs available.
Or something along those lines... not a Windows expert - just remembering this from past troubleshooting sessions.
Click to expand...
This all makes sense. Obviously, I'm also not a Windows expert (very from from it, in fact.) I appreciate your help!
 
Could you post speed tests of windows barebones, disk speed, CPU benchmark, then with it virtualized passing through the GPU. I see many benefits with zfs snapshots to rollback windows VM, but I don't want my compile times to suffer compiling apps for windows and android.

I was thinking of trying same thing passing through GPU and some USB ports for a KVM to switch over mouse and keyboard.

On my dell server I have successfully bhyve'd freebsd, Ubuntu, windows 11, windows server, openbsd, netbsd and home assistant. I find I have most of them turned off at home and only home assistant always running. Successfully passed through some USB ports there so it's prepped for zigbee and zwave if I need it. I guess most people pass through GPU to work with cuda.

Currently I use a KVM switch to switch back and forth between windows 11 machine and a Mac mini m4, depending what platform I need to compile for, but I think windows 11 under freebsd would be cool
 
You must log in or register to reply here.
Back
Top