Date: Wed, 27 Aug 2014 11:53:19 -0400 From: Nikolai Lifanov <lifanov@mail.lifanov.com> To: freebsd-virtualization@freebsd.org Subject: Re: lost ability to run FreeBSD on bhyve on CURRENT Message-ID: <53FDFEEF.1060302@mail.lifanov.com> In-Reply-To: <53FDDFC3.1070206@mail.lifanov.com> References: <mailman.27.1409140801.32275.freebsd-virtualization@freebsd.org> <53FDDFC3.1070206@mail.lifanov.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/27/14 09:40, Nikolai Lifanov wrote: > On 08/27/14 08:00, freebsd-virtualization-request@freebsd.org wrote: >> Hi Nikolai, >>>> Can someone look at Bugzilla 192470 please? >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 >> We've not been able to repro this on E3-1220 v3, E5-2650, or E5-2609 >> v2 systems :( >> >> Do you have any xsave-related tunables set in loader.conf ? >> >> Do CURRENT guests work ? If so, would you be able to send a dmesg from >> one ? >> >> later, >> >> Peter. > > Hello. > > I don't have anything exotic in my loader.conf: > vmm_load="YES" > nmdm_load="YES" > pptdevs="10/0/0" > zfs_load="YES" > vfs.root.mountfrom="zfs:tank/ROOT/270660" > > Disabling ppt doesn't help either. CURRENT panics and drops me in ddb > when booting. I attached "sysctl hw.vmm" and the panic message when > trying to boot CURRENT to the bug. > Interestingly, boot works 1/many times. By repeatedly trying to boot it over and over again, I was able to get it to boot twice total. Once FreeBSD is able to boot, it works as expected. I'm about to attach the dmesg from this to Bugzilla. - Nikolai Lifanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53FDFEEF.1060302>