Kernel modules provided by virtualbox-ose and virtualbox-ose-guest-dkms conflict

[Forest Monsen]

Binary package hint: virtualbox-ose

When both virtualbox-ose (3.1.6-dfsg-2ubuntu2) and virtualbox-ose-guest-dkms (3.1.6-dfsg-2ubuntu2) packages are installed, VirtualBox fails to load the networking adapter for the guest OS and will not boot the guest OS. Disabling the networking adapter in the VirtualBox GUI allows the guest OS to boot. Removing the virtualbox-ose-guest-dkms package resolves the issue.

"Fixed" would mean that the guest OS would be allowed to boot normally, even if the virtualbox-ose-guest-dkms package is also installed.

To reproduce on Lucid Lynx 10.04 (64-bit):
- install both packages,
- install a guest OS in VirtualBox,
- enable the networking adapter as a bridged adapter using the host's eth0 interface (in the VirtualBox GUI),
- launch the virtual OS from the VirtualBox GUI at Applications -> Accessories -> VirtualBox OSE.

dmesg reveals:
<code>
[22602.693177] vboxdrv: Trying to deactivate the NMI watchdog permanently...
[22602.693181] vboxdrv: Successfully done.
[22602.693184] vboxdrv: Found 2 processor cores.
[22602.693283] VBoxDrv: dbg - g_abExecMemory=ffffffffa090fa20
[22602.693319] vboxdrv: fAsync=0 offMin=0xb7c offMax=0x1321
[22602.694754] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[22602.694759] vboxdrv: Successfully loaded version 3.1.6_OSE (interface 0x00100001).
[22602.703368] vboxguest: exports duplicate symbol RTMemExecFree (owned by vboxdrv)
</code>