I didn't have the time to try to figure out the cause of the problem, but what I did try didn't work. Since I had been running with VirtualBox 3.1.0 with 3.0.x additions just fine before, I rolled back the changes made by the 3.1.0 additions and reinstalled the additions from 3.0.10, which was the last version of the additions running on my guest. Fortunately, I had the 3.0.10 guest additions ISO in my package cache so it was pretty painless.
This might not be enough for everyone, but the features I'm mostly concerned about- resizing my X display and shared clipboard- worked just fine before and continue to.
Host: Windows XP 32-bit
Guest: Arch Linux 32-bit (system is fully up to date, except VB-related packages)
I downloaded the .deb install file for my Kubuntu 9.10 Koala AMD64 environment, which is itself living inside of a Virtualox 3.2.6 machine on top of a Windows host. I'd like to set up a WindowsXP virtual machine inside of Linux, for a few CAD reader tools that are Windows Only. I'd rather have this inside my linux world rather than install those tools to the host Windows OS.
Is it possibel or not to have a Virtualbox installed in an OS that is itself running under Virtualbox, or do the guest things conflict with the host things?
Sorry to dig out this old post. But also with the latest version it happens to me too. My host system is WindowsXP Service Pack3 but there should be not an issue. Then I run latest Debian lenny as guest. There I install both virtualbox and guest additions. Also latest version from here.
What I did is as follows: I installed first the guest additions then installed the virtualbox environment. For the second I ran into problems right after he built the vboxdrv kernel module. I suppose that both modules vboxguest and vboxdrv are simply incompatible. Trying to install both things in reversed order results in the failure of the second installed one.
What I did is as follows: I installed first the guest additions then installed the virtualbox environment. For the second I ran into problems right after he built the vboxdrv kernel module. I suppose that both modules vboxguest and vboxdrv are simply incompatible. Trying to install both things in reversed order results in the failure of the second installed one.
Are you saying you installed the VirtualBox guest additions in the host?
That will not work. Remove them and then install the VirtualBox program in the host.
The guest additions (as they say) go in the guest.
Yes I did. But it was not done by accident. My debian system is running as both, host and guest. I have a nested setup with following chain:
WinXP -> Debian lenny -> Kubuntu
What a pity ... Then I'll take another software for one of these virtualization points. This setup is strange and possibly very rare, but is required at the moment
Just to throw it into the room. I want to make a "self healing" Internet café solution. The first virtualization is needed only for development purposes. I work under WinXP and I'm used to make snapshots and try out different things. Then to the second one: I want to make a minimal X11 setup where I run another visualization. But this one should serve as a jail for the user environment to protect the computers against viruses and other malware.
There still are use cases for having both the host and guest modules installed, however. I dual-boot Linux and Mac OS X; VirtualBox supports raw partition access, so while I'm booted in OS X I can run my Linux partition in a virtual machine, and vice versa. Unfortunately this is difficult as long as the host and guest kernel modules conflict!
