[Call For Testing] VirtualBox for FreeBSD!

[Paul Schenkeveld]

On Thu, May 14, 2009 at 09:12:37PM +0200, Martin Wilke wrote:
> 
> Howdy Guys,
> 
> After the announcement from Alexander Eichner about
> Virtualbox on FreeBSD, we started the work on a port
> for FreeBSD. Now we think that we solved the most
> problems and are ready for the first Call for Testing.

Many thanks!

So far I had a short ride but vbox fails every time after the first try.

If the following can help you debug/improve, read on, otherwise I'll just
wait for a more stable version.  If you want me to test anything or send
crash dump, please let me know.

 - Running 7.2-STABLE i386 as of Thu May 14 19:28:42 CEST 2009 on Dell
   Precision M4300 notebook (Intel T7500 Core-2 Duo, 2.2GHz VT-x enabled,
   3 GB RAM)
 - /proc is mounted
 - Downloaded vbox port yesterday evening (~ 18:50 UTC)
 - make -s install clean (watch many qt4 dependencies, dev86 and vbox
   install)
 - kldload vboxdrv (OK, even with X running)
 - $ VirtualBox
 - Created a guest with 512MB RAM, 2GB IDE pri master disk
 - Could not choose bridged network, so fell back to NAT
 - Installed FreeBSD 7.1 from 7.1 release DVD iso, feels very good, nice
   performance!
 - Could not NFS mount anything, vbox NAT translates NFS client to
   unprivileged port
 - Wanted to add second virtual disk to hold /usr/src and /usr/obj so
   stopped vbox, added virtual disk and tried to restart guest many
   times, no luck
 - Rebooted computer
 - kldload vboxdrv (with X11 running), system panics
 - Reboot and load vboxdrv from loader works
 - Trying to start existing vbox guest always fails, sometimes with error
   popup:
       Unknown error creating VM (VERR_PDM_DEVICE_NOT_FOUND).

       Result Code: NS_ERROR_FAILURE (0x80004005)
       Component:   Console
       Interface:   IConsole {a7f17a42-5b64-488d-977b-4b2c639ada27}
   but mostly I only see the console window appear and disappear within
   a second (/var/log/messages: pid 1283 (VirtualBox), uid 2506: exited
   on signal 11
 - Creating a new guest (in case disk image of old guest is damaged)
   never starts (shows same symptoms as original guest)

Thanks again for all the good work!

-- Paul Schenkeveld