Date: Sat, 29 May 2010 13:44:33 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Beat Gaetzi <beat@freebsd.org> Cc: emulation@freebsd.org Subject: Re: CFT: VirtualBox 3.2.0 Message-ID: <AANLkTimfPLIIT-t7ZZi8ugAEhKSX7GYoqfXtC-id-y39@mail.gmail.com> In-Reply-To: <4C011524.7050806@FreeBSD.org> References: <4C011524.7050806@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 29, 2010 at 8:22 AM, Beat Gaetzi <beat@freebsd.org> wrote: > Hi, > > The vbox@ team is happy to announce a call for tester for VirtualBox 3.2.= 0. > > The VirtualBox 3.2.0 changelog is available here: > =A0http://www.virtualbox.org/wiki/Changelog > > Changes to the port: > =A0- VirtualBox and the guest additions have been updated to 3.2.0. > =A0- Add option to build with VNC support (Disabled by default) > =A0- Add option to build with VDE support (Disabled by default) > =A0- Add option to build webservice (Disabled by default) > =A0- Fix build with QT4 support disabled and X11 support enabled. > =A0- Replace custom pkg-install.in script with GROUPS framework. > =A0- Do not build Guest Additions in virtualbox-ose port. > =A0- Add patch to implement locking/unlocking of host DVD drive. > > You will find a tarball with the latest port version here: > =A0https://svn.bluelife.at/nightlies/virtualbox-port.tar.gz > > Please check the wiki page for known problems: > =A0http://wiki.freebsd.org/VirtualBox > > Please backup your virtual machines before upgrading and report any > functionality which was working with previous versions of VirtualBox and > no longer working with 3.2.0, any build failures or problems with the > newly added port options. > > Many thanks to the VirtualBox developers (especially Alexander Eichner > for all his work and help), all tester and patch submitter and the whole > vbox@ team especially decke@. > > Beat, on behalf of vbox@ First report: $ uname -a FreeBSD x300 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0 r208609: Fri May 28 04:25:01 CDT 2010 root@x300:/usr/obj/usr/src/sys/X300 amd64 The port builds fine, all options enabled. However, on loading kldload-ing vboxdrv.ko instantly panics the machine. I'm unable to obtain a dump (double fault?), but I can run appropriate debugging commands if someone would like to steer me around :) Partially transcribed backtrace: Tracing pid 5325 tid 100183 td 0xffffff0067aa23e0 bzero() at bzero+0xa VBoxDrvFreeBSDModuleEvent() at VBoxDrvFreeBSDModuleEvent+0x3d module_register_init() at module_register_init+0xa8 linker_load_module() at... kern_kldload() at... kldload() at... syscall() at... Thank you to everyone on the vbox@ team for the AWESOME effort put into bringing another powerful virtualization option to FreeBSD. -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimfPLIIT-t7ZZi8ugAEhKSX7GYoqfXtC-id-y39>