Date: Mon, 01 Feb 2010 09:16:49 +0100 From: Bernhard Froehlich <decke@bluelife.at> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-emulation@freebsd.org Subject: Re: virtualbox-ose build fails on -current with utmp.h Message-ID: <227662eecaa700c7c817bafb49a09de8@bluelife.at> In-Reply-To: <4B5D0EF2.1030906@FreeBSD.org> References: <4B5BF458.50507@FreeBSD.org> <4B5D0EF2.1030906@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 24 Jan 2010 19:24:34 -0800, Doug Barton <dougb@FreeBSD.org> wrote: > Build was successful with today's changes, however my guest doesn't run. > I can kldload my vboxdrv module, then run VirtualBox, but my previously > working-just-fine WinXP guest goes from "Starting" to "Aborted" when I > try to fire it up. > > Nothing useful looking in the logs, in /var/log/all I have this: > pid 3574 (VirtualBox), exited on signal 5 > > And in the log that vbox creates in my home directory all I have is this: > Log created: 2010-01-25T03:03:05.295539000Z > Executable: /usr/local/lib/virtualbox/VirtualBox > i=0x0 Phys=0000000000000000 Heap > > Any suggestions? :) Probably it's a vbox regression? You could try our testing port which is at 3.1.4 BETA1 or the virtualbox-ose-devel port which tracks code from trunk. http://svn.bluelife.at/nightlies/virtualbox-port-r707.tar.gz -- Bernhard Fröhlich http://www.bluelife.at/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?227662eecaa700c7c817bafb49a09de8>