Date: Sat, 26 Feb 2011 15:05:45 -0500 From: Ryan Stone <rysto32@gmail.com> To: freebsd-emulation@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.4 Message-ID: <AANLkTi=37uuDpYodH7XMkW-PqwAQLWxAv9oqUDVC9ko=@mail.gmail.com> In-Reply-To: <AANLkTi=raeFqgjnBtpAAQwMdkoxCgvD0k2d%2BbK2p_CeT@mail.gmail.com> References: <AANLkTi=raeFqgjnBtpAAQwMdkoxCgvD0k2d%2BbK2p_CeT@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 23, 2011 at 9:24 PM, Ryan Stone <rysto32@gmail.com> wrote: > I'm running VirtualBox 4.0.4 under PC-BSD 8.1. =A0Previously I had the > latest VirtualBox PBI installed(3.2.12). =A0VirtualBox 4.0.4 has > recognized my previous VMs and I'm able to start them, but if I try to > open the "Settings" window in VirtualBox OSE Manager it crashes with > an assertion failure. =A0I'm not sure if the fact that I had some VMs > from a previous installation hanging around has anything to do with > the problem: I see the crash if I run the OSE Manager as root, and > root didn't have machines before. =A0I don't seem to get a core file, > but that could be a problem on my end. =A0The output to the console is: > > [rstone@pcbsd-7934 rstone]VirtualBox > Type Manifest File: /home/rstone/.VirtualBox/xpti.dat > nsNativeComponentLoader: autoregistering begins. > nsNativeComponentLoader: autoregistering succeeded > nNCL: registering deferred (0) > Xlib: =A0extension "GLX" missing on display ":0.0". > > !!Assertion Failed!! > Expression: pContext > Location =A0: /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.0.4_O= SE/src/VBox/Frontends/VirtualBox/src/VBoxGLSupportInfo.cpp(665) > static bool VBoxVHWAInfo::checkVHWASupport() > Trace/BPT trap: 5 > > > Let me know if you need any more information. > To follow up: I tried re-building the port without the DEBUG option enabled, and I'm now able to open the Settings window. Maybe the assert that's tripping is incorrect? Also, with VirtualBox 3.2.10 and 3.2.12 I was able to crash the VM(Guru Meditation) within minutes by stressing a host-only or internal network(I filed a ticket for the host-only networking crash here: http://www.virtualbox.org/ticket/8089). I'm very happy to report that I am unable to reproduce the problem in 4.0.4, with or without DEBUG enabled. I was able to to an installworld over NFS in two virtual machines without the VM crashing either time. Previously the VM would always crash before the installworld completed. I've been running netperf over a host-only network for about two hours now without a crash. Thanks for the great work! Now that these crashes To follow up: I tried re-building the port without the DEBUG option enabled, and I'm now able to open the Settings window. Maybe the assert that's tripping is incorrect? Also, with VirtualBox 3.2.10 and 3.2.12 I was able to crash the VM(Guru Meditation) within minutes by stressing a host-only or internal network(I filed a ticket for the host-only networking crash here: http://www.virtualbox.org/ticket/8089). I'm very happy to report that I am unable to reproduce the problem in 4.0.4, with or without DEBUG enabled. I was able to to an installworld over NFS in two virtual machines without the VM crashing either time. Previously the VM would always crash before the installworld completed. I've been running netperf over a host-only network for about two hours now without a crash. Thanks for the great work! Ryan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=37uuDpYodH7XMkW-PqwAQLWxAv9oqUDVC9ko=>