bhyve server 2016 lockup

[Dave Cottlehuber]

On Fri, 6 Jul 2018, at 10:22, Matt Churchyard wrote:
> Hello,
> 
> I have a server 2016 virtual machine which I only created for testing 
> and don't use much. Booting it up recently I've found that it locks up 
> consistently within a few minutes of booting. What can I do to try and 
> figure out what's causing the problem?
> 
> Host was recently updated to 11.2
> # uname -a
> FreeBSD dev.--- 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 
> 04:32:14 UTC 2018     root at releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/
> GENERIC  amd64
> 
> Bhyve command is as follows
> # bhyve -c 2 -m 2G -Huwl bootrom,/usr/local/share/uefi-firmware/
> BHYVE_UEFI.fd
>   -U 841e8764-75f4-11e8-b2e3-50e549369bc6 -l com1,stdio
>   -s 0,hostbridge -s 31,lpc -s 3:0,ahci-cd,/vm/.config/null.iso -s 
> 4:0,ahci-hd,/vm/w2016/disk0.img -s 5:0,e1000,tap1,mac=58:9c:fc:08:8e:70
>   -s 6:0,fbuf,tcp=0.0.0.0:5900 -s 7:0,xhci,tablet w2016

Hi Matt,

try using virtio for nic & storage to start with. I've used specifically these drivers https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.96/virtio-win-0.1.96.iso and had trouble with both later and earlier drivers, YMMV, and I sadly forget where I got this advice.

Also, it’s possible to install virtio drivers directly from the CD without pointy-clicky stupidness. Just add the CD to your bhyve command, in a later "PCI slot" than the existing “hard disk”, as the lowest numbered slot is what’s used to boot from AFAICT. 

- open an elevated command prompt
- run for /d %i in (d:\*) do @pnputil -a %i\w7\amd64\*.inf (you may need a different driver than w7 here)
- some of those will fail but just carry on
- reboot FTW

more notes here on my bhyve setup https://hackmd.io/s/rJvJuE-CW#

A+
Dave