Date: Fri, 27 Jul 2018 12:03:35 -0300 From: =?UTF-8?Q?Josias_L=2E_Gon=C3=A7alves?= <josiaslg@bsd.com.br> Cc: "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: Re: bhyve server 2016 lockup Message-ID: <CANgqCK_fRsL5=BqLXmJTA-0kiEcsziJirdj9ZgpQm87iTpiBcw@mail.gmail.com> In-Reply-To: <de65a3c6c9e64da28cb923dfe62768e7@SERVER.ad.usd-group.com> References: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> <1530874279.512578.1431934576.27AF56F1@webmail.messagingengine.com> <1dbba8ac-eca4-bb09-9d3b-ec26ed1452e5@cgi.cz> <de65a3c6c9e64da28cb923dfe62768e7@SERVER.ad.usd-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2018-07-06 9:05 GMT-03:00 Matt Churchyard <matt.churchyard@userve.net>: > 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 complain= s > 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@cgi.cz > 775 144 257 > 234 697 102 > 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@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=3D58:9c:fc:08:8e= :70 > >> -s 6:0,fbuf,tcp=3D0.0.0.0:5900 -s 7:0,xhci,tablet w2016 > > Hi Matt, > > > > try using virtio for nic & storage to start with. I've used specificall= y > 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 whe= re > I got this advice. > > > > Also, it=E2=80=99s 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 =E2=80=9Chard disk=E2=80=9D, as the = lowest numbered > slot is what=E2=80=99s 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 > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org= / > mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscribe@freebsd.org" > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization- > unsubscribe@freebsd.org" > If BLOCKIF_IOV_MAX is turned a arg in bhyve, we could possible use specific values to linux machines and windows machines. I have change this in block_if.h and have some machines to just run windows and others to run just linux. Is a kind of fragmentation i don't like and if have some option to pass in bhyve specify the BLOCKIF_IOV_MAX, would be good. If not possible, create some option where if specify windows like guest, other value of BLOCKIF_IOV_MAX is used by bhyve in execution.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANgqCK_fRsL5=BqLXmJTA-0kiEcsziJirdj9ZgpQm87iTpiBcw>