Date: Tue, 22 Dec 2015 17:14:18 -0700 From: Trent Thompson <trentnthompson@gmail.com> To: Peter Grehan <grehan@freebsd.org> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Windows/bhyve Bluescreen 0x50 Message-ID: <CAE7bWBp5Jh=Z1SpUHdUmg-EcspGXt39D9v3yZTLcyTv185Ze5w@mail.gmail.com> In-Reply-To: <56776BAA.1040102@freebsd.org> References: <CAE7bWBpnO%2BnChX=BA58NwthvZzf0bE11Muo=Y2btmPAqKPQtNA@mail.gmail.com> <56776BAA.1040102@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>It appears to be related to the number of vCPUs. Using a single vCPU will result in this, wherease >= 2 seems to work Ok with 2k16 tp3. That did the trick! I still seem to be having issues with the firmware on the i5 machine getting Windows 2016 to boot. (Windows 2008 and 2012 work fine) bhyve exits with: >$ vm exit[0] > reason VMX > rip 0x00000000017ca1d7 > inst_length 2 > status 0 > exit_reason 2 > qualification 0x0000000000000000 > inst_type 0 > inst_error 0 >$ sysctl hw.model >hw.model: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz Thanks for all your help!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE7bWBp5Jh=Z1SpUHdUmg-EcspGXt39D9v3yZTLcyTv185Ze5w>