ZeroDev

Yesterday (09 Sep. 2009) Sun released a new maintenance release for VirtualBox
[it contains only minor fixes, ebuilds are available
on jokey's overlay[1] as usual

UPDATE:
Due a critical bug[2] virtualbox upstream silently updated (the official
announcement should be posted later) the virtualbox-bin amd64 binary[3]
i just revbumped on jokey's overlay[1] app-emulation/virtualbox-bin to 3.0.6-r1

[1] http://overlays.gentoo.org/dev/jokey
[2] http://www.virtualbox.org/ticket/616
[3] http://vbox.innotek.de/pipermail/vbox-dev/2009-September/001822.html

Today Sun released a new maintenance release for VirtualBox
[it contains only minor fixes, ebuilds are available
on jokey's overlay[1] as usual

I just bumped the following ebuilds too:

• net-libs/gsoap (2.7.13)
• dev-util/kbuild (0.1.5-r2 aka r2336)

[1] http://overlays.gentoo.org/dev/jokey

Problem:
You are using VirtualBox in headless mode and you have to setup
hostonly networking with a specific VirtualMachine,
adding a new hostonly interface with an enabled dhcp server.

Step 1 - (Create a new interface):
First you have to add a new hostonly/dhcp interface using the command:

/opt/VirtualBox/VBoxNetAdpCtl add

Note that at the moment the interface name is harcoded/determined by the
"VBoxNetAdpCtl" command, so you can't call it for istance
"foobarif0", a fixed name "vboxnetN" will be assigned (eg: vboxnet1)

Step 2 - (Add and enable a dhcp server)
Now you can add, if you wish to, a dhcp server to the new interface
"vboxnet1" and configure a dhcp range, for example, with the command:

VBoxManage dhcpserver modify --ifname vboxnet1 \
--ip 192.168.1.254 --netmask 255.255.255.0 \
--lowerip 192.168.1.0 --upperip 192.168.1.250 --enable

Step 3 - (Register the interface and enable HostOnly newtworking)
Now you can register the "new" hostonly, dhcp enabled,
interface "vboxnet1" with an existing VirtualMachine with the
following commands:

VBoxManage modifyvm wxp --nic1 hostonly
VBoxManage modifyvm wxp --hostonlyadapter1 vboxnet1

Step 4 - (Start the VM with VBoxRDP)
Finally you can start the VirtualMachine (and connect later to it
via RDP with an rdp client, rdesktop for example), let's fire up the
VirtualMachine with the command:

VBoxVRDP -s MachineName

Enjoy

Notes:
Not sure if it is a bug or a default behaviour but keep in mind
that a new/different hostonly adapter must be first created
manually with "VBoxNetAdpCtl" and then registered later with the
virtualmachine, on the official manual this is not reported[1].

[1] http://www.virtualbox.org/manual/UserManual.html#vboxmanage-dhcpserver

Another week another (minor) release!

today VirtualBox 3.0.2 was released, it's a maintenance release this means that it will contain only bugfixes[1] and no new features.

Updated ebuilds are available on jokey's overlay as usual[2].

[1] http://www.virtualbox.org/wiki/Changelog
[2] http://overlays.gentoo.org/dev/jokey

As usual new ebuilds are available on jokey's overlay[1],
this release introduced some interesting features like an initial/experimental
support for DirectX accelleration with windows guest, talking about ebuilds the relevant news are:

• app-emulation/virtualbox-modules: added support for the new kernel module vboxnetadp.
• app-emulation/virtualbox-ose: fixed problematic mesa checks in configure (thanks to Grzegorz Chwesewicz and David Gence, wrt #265558 and #268885)
• app-emulation/virtualbox-guest-additions: dropped the old vboxadd-timesync binary, added new vboxadd-service binary, added new virtualbox-guest-additions initd
• x11-drivers/xf86-video-virtualbox: added support for the new vboxvideo drm kernel driver, added a patch to fix mesa checks in configure (thanks to Grzegorz Chwesewicz and David Gence, wrt #265558 and #268885)

Please report any issue with these ebuilds on the virtualbox 3.0.0 bump request bug[2].

[1] http://overlays.gentoo.org/dev/jokey/
[2] https://bugs.gentoo.org/show_bug.cgi?id=275963