bhyve server 2016 lockup

Fri Jul 6 12:59:43 UTC 2018

Normally I would be using virtio-net, and advise as much with vm-bhyve.
It is sometimes useful to use e1000 briefly in order to have Internet access to download drivers…
This machine is just for testing and I hadn’t bothered going through the process of finding and installing virtio drivers, minimal as that is.

Not that I think my lockups were nic related, but some users may use e1000 just for simplicity and ideally it should be a stable choice, albeit with lower performance and more overhead than virtio.

Thanks for the additional vote regarding stability. I think my issue was most likely low memory related. In production I probably wouldn’t want to give any less than 16-20GB to WS2016, more depending on services installed.

Matt

>I use virtio-net for everything... the only moment I needed an em1000 was with 8.2-RELEASE guest :)

>the drivers should be in NetKVM directory or something like that.

>ad. production... have no trouble with stability so far...

--

   regards

Jakub Chromy

CGI Systems div.

----------------

CGI CZ s.r.o.

sales at cgi.cz<mailto:sales at cgi.cz>

775 144 257

234 697 102

www.cgi.cz<http://www.cgi.cz>
On 6.7.2018 14:05, Matt Churchyard wrote:

Thanks for the replies guys. I've increased memory and switched to virtio-net. Been running for an hour or two so far. Windows just complains about the boot device if I try to move to virtio-blk.

I might set up another test using different settings during installation and see how that goes.

Only really played about with bhyve so far but starting to consider using for production machines, so any hard lockup is a bit of a worry.

Regards,

Matt

Dave,

you got working Windows guest with virtio-blk?

I thought it was still unstable. I've tested virtio storage (on bhyve) + virtio storage drivers on several windows guest  ~ 2 months ago and they were crashing all the time.

So I use ahci-hd with every windows guest we run (from 7 to Win Server 2012).

--

    regards

Jakub Chromy

CGI Systems div.

----------------

CGI CZ s.r.o.

sales at cgi.cz<mailto:sales at cgi.cz>

775 144 257

234 697 102

www.cgi.cz<http://www.cgi.cz>

On 6.7.2018 12:51, Dave Cottlehuber wrote:

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/<mailto: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#<https://hackmd.io/s/rJvJuE-CW>

A+

Dave

_______________________________________________

freebsd-virtualization at freebsd.org<mailto:freebsd-virtualization at freebsd.org> mailing list

https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization

To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe at freebsd.org"<mailto:freebsd-virtualization-unsubscribe at freebsd.org>

_______________________________________________

freebsd-virtualization at freebsd.org<mailto:freebsd-virtualization at freebsd.org> mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization

To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe at freebsd.org"<mailto:freebsd-virtualization-unsubscribe at freebsd.org>