Date: Sat, 13 Sep 2014 00:06:14 +0200 From: Eric Masson <emss@free.fr> To: Mailing List FreeBSD Emulation <freebsd-emulation@FreeBSD.org>, FreeBSD VirtualBox Team <vbox@FreeBSD.org> Subject: Re: Virtualbox-ose 4.3.12 guru meditation while booting any VM Message-ID: <86r3zgo5nt.fsf@srvbsdfenssv.interne.associated-bears.org> In-Reply-To: <86mwa7so14.fsf@srvbsdfenssv.interne.associated-bears.org> (Eric Masson's message of "Wed, 10 Sep 2014 13:39:03 %2B0200") References: <86mwa7so14.fsf@srvbsdfenssv.interne.associated-bears.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Masson <emss@free.fr> writes: Hi, > I'm facing serious issues with virtualbox-ose since 4.3.x > > Current test has been done on r367755 : > virtualbox-ose-4.3.12_1 General-purpose full virtualizer for x86 hardware > virtualbox-ose-kmod-4.3.12 VirtualBox kernel module for FreeBSD > > Whenever I try to boot a VM (32/64 bits, any type), it enters Guru > Meditation state with the following message on host console : > > HMR0InitVM: ffffff808b9d9000 > nfe0: promiscuous mode enabled > > !!Assertion Failed!! > Expression: pVCpu->hm.s.idLastCpu == pCpu->idCpu > Location : /vol0/ports/build/usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.12/src/VBox/VMM/VMMR0/HMSVMR0.cpp(967) void hmR0SvmFlushTaggedTlb(PVMCPU) > vcpu idLastCpu=ffffffff pcpu idCpu=1 > nfe0: promiscuous mode disabled > > Until now, I could revert to r340725, and then build 4.2.22, the last > revision working flawlessly here, but 9.3-P1 ports infrastructure now > refuses to build unstaged ports. > > Kernel, world & VBox ports have been built with gcc then clang, giving > the same error. > > uname -a > FreeBSD srvbsdfenssv.interne.associated-bears.org 9.3-RELEASE-p1 FreeBSD > 9.3-RELEASE-p1 #0 r271308: Wed Sep 10 00:21:18 CEST 2014 > emss@srvbsdfenssv.interne.associated-bears.org:/usr/obj/usr/src/sys/M3N78-VM > amd64 > > dmesg > http://emss.free.fr/contents/Divers/dmesg.txt > > VBox.log > http://emss.free.fr/contents/Divers/VBox.log > > Any idea on something I could have overlooked ? > > What information could help solve the issue, please ? Using GENERIC kernel doesn't change anything to VirtualBox behaviour. Same error pops up, any idea please ? Regards Éric Masson -- Tu viens donc de traiter 120 votants de neuneux. Note que je suis d'accord avec toi, mais sache que cette position est relativement technique à assumer avec style, petit scarabée. -+- TP in GNU : Le style c'est l'homme, le reste est neuneueterie -+-
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86r3zgo5nt.fsf>