Hey Nuno, - I'm not. I plugged in my monitor's HDMI cable directly into the GPU's HDMI port. Once bhyve starts up (if your passthrough is working correctly and your GPU's drivers are installed), it will output to your monitor. You would only need VNC for initial installation of Windows. - I'm not sure of the NVIDIA case. I do know there is someone who blogged about how they got theirs working: https://dflund.se/~getz/Notes/2024/freebsd-gpu/
Atm I'm currently trying to collect more info on why my bhyve VM randomly crashes sometimes. So far I've collected that the exit reason bhyve is showing is 0x60, which points to the following entries in the amd freebsd kernel sources: 0x60 https://github.com/freebsd/freebsd-src/blob/4c3a868d13c053ef173268cdfe1365978a282178/sys/amd64/vmm/amd/vmcb.h#L195 https://github.com/freebsd/freebsd-src/blob/4c3a868d13c053ef173268cdfe1365978a282178/sys/amd64/vmm/amd/vmcb.h#L128C1-L128C30 XSETBV https://github.com/freebsd/freebsd-src/blob/4c3a868d13c053ef173268cdfe1365978a282178/sys/amd64/vmm/amd/vmcb.h#L94 I also asked Proton's Lumo+ AI what is 0x60 to see what it comes up with, it said the following: exit_reason[0] = 0x60 is the VM‑exit code that bhyve reports when the guest triggers the XSETBV instruction. Why it happens XSETBV writes to the extended control register XCR0. In Intel VMX (the virtualization technology bhyve uses on x86), execution of XSETBV is not allowed to run directly in the guest; the CPU forces a VM‑exit so the hypervisor can validate the operation. bhyve records the exit reason as 0x60, which maps to the VMX exit reason “XSETBV” in the Intel specification. What it means for you The guest tried to enable or change AVX‑512 / XSAVE feature bits via XSETBV. Because bhyve does not currently emulate that instruction, it aborts the guest’s instruction stream and reports the exit code. In most cases the guest will continue after bhyve handles the exit, but if the hypervisor isn’t set up to emulate XSETBV you’ll see the VM stop or crash. Typical ways to deal with it Update bhyve – newer releases include basic XSETBV handling for common feature sets. Adjust the guest’s CPU flags – start the VM with a CPU model that doesn’t expose the XSAVE/XGETBV features the guest expects (e.g., -c host vs. a specific model). Patch bhyve – if you’re comfortable with C, you can add a handler for VMX_EXIT_REASON_XSETBV that either emulates the instruction or simply ignores it when the requested bits are already enabled. If you keep seeing the same exit repeatedly, it usually points to a mismatch between the guest’s expectations (often a modern Linux kernel or a Windows build that wants AVX‑512) and the capabilities bhyve is presenting. Aligning those expectations—either by tweaking the VM’s CPU configuration or by upgrading bhyve—generally resolves the issue. Jonathan Vasquez PGP: 34DA 858C 1447 509E C77A D49F FB85 90B7 C4CA 5279 Sent with ProtonMail Secure Email On Saturday, September 20th, 2025 at 19:47, Nuno Teixeira <edua...@freebsd.org> wrote: > Hello Jonathan! > > Thanks for excellent quality videos on yt, I already subscribed it :) > > Just a quick questions: > > 1- Are you using freerdp3 to connect to win11pro? (Asking this because vnc is > very slow) > 2- Do you know how is nvidia status compared to your use case? > > Thanks! > > Jonathan Vasquez <j...@xyinn.org> escreveu (sábado, 20/09/2025 à(s) 02:42): > >> Hey all, I've spent some time today doing a gaming demo. I've uploaded the >> video in 2K so you can get the maximum effect. It's been an interesting >> experience so far, and I'm going to try to make it my primary gaming >> machine. We'll see how it goes. It's definitely qwirky, and sometimes I need >> to reboot the VM 4-5 times before it "stabilizes" (which means the VM won't >> just randomly crash or have massive lag in game). I'll need to collect more >> data through play testing. >> >> You can take a look at the video here (I'll post timestamps in the video >> soon): >> >> https://youtu.be/_cz0RUAw5p8 >> >> Jonathan Vasquez >> PGP: 34DA 858C 1447 509E C77A D49F FB85 90B7 C4CA 5279 >> Sent with ProtonMail Secure Email >> >> On Wednesday, September 17th, 2025 at 22:33, Jonathan Vasquez >> <j...@xyinn.org> wrote: >> >>> Alright! The YouTube Video is up. Let me know what you think. I'm really >>> excited about this. >>> >>> https://youtu.be/Ob4-v7dTJGs > > -- > > Nuno Teixeira > FreeBSD UNIX: <edua...@freebsd.org> Web: https://FreeBSD.org
