virtualbox.org

I've had this problem tonight. It happened after OpenSuSE 11.1 ran one of its regular updates and installed patches for, amongst other things, glibc (it sticks in my mind as it was one of the packages I had to install manually before installing VBox). After that VBox would launch, but the virtual machines refused to start giving the error in the title of this thread. I closed VBox, uninstalled the VirtualBox package, then reinstalled it and restarted VBox, all without a reboot, and everything was working again. With OpenSuSE its a pretty painless and straight forward thing to do. Yast does make removing and adding packages very easy. Being a relative Linux newbie I wouldn't have had a clue about the command you mention above, but will make a note of it for next time, as I'm sure there will be a next time.

What might be of more interest to the techies is the problem I had before this one appeared. The update above is not the first patch to glibc that has been downloaded and installed on this PC. The first patch (a week or so back) also affected VBox, but in a different way. After that first patch was installed, VBox would attempt to start (bouncing virtualbox on the cursor, part built button on the task bar as appears to be the norm for any application when starting on OpenSuSE), but instead of VBox starting up, it would remain in that state for 2-3 times longer than normal, then simply vanish. Rebooting made no difference to this problem, and I therefore assumed a problem with the VBox installation (I'm a long time Windows user who is used to less than perfection), so uninstalled and reinstalled VBox. After that, it was working fine again. Better still, in both this case and the case tonight, the virtual machines were unaffected and were still lised in the VBox window when VBox ran up, and could be started without needing to change any settings in either the machines or in VBox itself.

So I managed to figure it out. It turned out that vboxnetflt did not compile during installation. I cd'd to the source dir and compiled manually, modproped it and then vboxdrv and it worked! If you are experiencing a similar problem try the below. Your source directory may differ from mine.

code:

cd /usr/src/vboxnetflt-2.1.4/
sudo make && sudo make install
modprobe vboxnetflt
modprobe vboxdrv

If everything exit's 0 then you should be good to go!

@foriamroot:
I had the same problem, especially the error message that has attracted me:

depmod....(bad exit status: 1)

A workaround for this issue is to run depmod manually (don't ask me why just because I also do not know why): and then, If there is no error message outof those commands, the problem is solved. Now I can run VB 2.2.4 in my Ubuntu box. For other Linux distros, you can do the same.

HTH,