bhyve-webadmin
bhyve-webadmin copied to clipboard
Windows 10 VM - setup reboots vm with virtio disk
I tried to deploy to windows virtual Machines as described in ==> https://bhyve.npulse.net/deploy_windows <==. I used 21H2 (19044.1266 ISO to be precise) and the (latest ?) Virtio ISO linked in the top of the manual.
First i attached the virtual system disk as described on VirtIO, but when windows setup loads the driver, the VM reboots immediately.
With the AHCI Option for the disk the windows installation worked perfect without any issues.
My FreeBSD System is 14.0-current if that matters for this issue.
Thanks your report, I have seen this issue when I used to a wrong driver as virt/io. There are multiple viostor driver and you need to pickup the latest one for win10.
Please report back if you have any update on this case.
I tried this several times with the viostor driver for Win10/amd64 but always with the result that the vm rebooted. I will try older Win10 Versions the next day to find the cause ... it could also be a problem in the bhyve in 14.0-current ...
I would bet on the Windows's driver fault than bhyve itself. I will try to reproduce in the following days.
W11 (22000.194) is too new for a virtio disk driver to test (i used viostor w10/amd64) but has the same issue. The virtual machine was powerd off but not rebooted after selecting the driver ...
I will try W11 setup with AHCI Disk.
Windows 11 runs fine in bhyve, instalen an ahci/sata disk driver. :-)
okay, nice to hear that at least ahci works. I have never seen difference between AHCI and VirtIO on side of performance. Thanks your effort to made this research.
I will going to check Win11 this weekend under Bhyve.
I tried today an older version (18363 aka W10 1909) as OEM iso with similar settings. The viostor driver gets loaded, the machine crashes after the disk was selected, the fist 100mb boot partition was created on the disk.
Interestingly, all Windows VM show a hardware change notification (error code 0xC004F211) in the activation settings, although they have not been activated yet ...