VM won't start after Hardy Update

gspawn · Post by **gspawn** » 29. May 2008, 07:17

I seem to run into this problem every time I update Ubuntu, but here's the deal. When I updated form Gutsy to Hardy, virtualbox started giving me the usual error, but then I installed the version 1.6 of virtualbox and everything worked fine. Later on, I decided to change from the vanilla Hardy install to Ubuntu Studio 8.04, and once again, virtualbox is broken and isn't working. I've tried removing and reinstalling 1.6, but when it tries to compile the kernel during setup, it still fails. Here's the error i'm getting:

Code: Select all

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).


Result Code: 
0x80004005
Component: 
Console
Interface: 
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}

So, of course I try running the /etc/init.d/vboxdrc setup as root, and this is what it says:

Code: Select all

 * Stopping VirtualBox kernel module                                                                                          *  done.
 * Recompiling VirtualBox kernel module
 * Look at /var/log/vbox-install.log to find out what went wrong

Here are the contents of the log file:

Code: Select all

/etc/init.d/vboxdrv: 311: /opt/VirtualBox-1.4.0/src/build_in_tmp: not found

I have already tried the solution listed for the person who was having problems with virtualbox breaking every time he rebooted, and that did nothing. Any ideas how I can get this fixed?[/code]

karu · Post by **karu** » 4. Jun 2008, 12:21

Hello,
same to me, kernel update on Ubunto 8.04 with VB 1.6:
/etc/init.d/vboxdrv: 311: /opt/VirtualBox-1.4.0/src/build_in_tmp: not found

Is there any solution except to totaly reinstall virtualbox?

gspawn · Post by **gspawn** » 4. Jun 2008, 17:53

I did finally get it working. Here's what I did.

First off, update your linux headers:

Code: Select all

sudo apt-get install linux-headers-$(uname -r)

Then, completely remove any version of virtualbox you have installed, and make sure you download the latest binary from Sun. I couldn't get the version o the ubuntu repository to work. Double click on the .deb file and it should work.

theTAZ57 · Post by **theTAZ57** » 4. Jun 2008, 20:46

Hi there,
since the new kernel update ( 2.6.24-18 ), VB doesn't work on my kubuntu 8.04!!!

I try all answers above.

have any idea?

thanks all

Post by **Sasquatch** » 4. Jun 2008, 22:58

theTAZ57 wrote:Hi there,
since the new kernel update ( 2.6.24-18 ), VB doesn't work on my kubuntu 8.04!!!

I try all answers above.

have any idea?

thanks all

What version do you use? The OSE version or the PUEL one? For the OSE, wait until the devs have the Kernel Modules ready for VB. If you have the PUEL version, the kernel module should be installed automatically now. If it doesn't, run 'sudo /etc/init.d/vboxdrv setup'.
If it all fails, try to reinstall VB. Your settings and VMs will be kept.

karu · Post by **karu** » 5. Jun 2008, 01:49

That is exactly what I did.
But I don't want to unstall and install virtualbox completly every time I get a kernal update. There is somthing wrong with virtualbox.

theTAZ57 · Post by **theTAZ57** » 5. Jun 2008, 07:17

@Sasquatch

Hi
I do all you said, but nothing works

I got the PUEL version

regards

Post by **Sasquatch** » 5. Jun 2008, 09:36

This is strange. It works for me, so there might be something wrong on your system. Did you install everything needed for your kernel? So the image and headers? I have no idea why it wouldn't work.

nikopol · Post by **nikopol** » 5. Jun 2008, 11:57

Same problem here - I actually hadn't much on that image so I wiped and tried to reinstall XP. This timeI had a complete lockup when formatting with Ubuntu becoming unresponsive.

It does seem to have coincided with the kernel update but even running it on the previously fine kernel (and obviously recompiling the module) has the same lockup problem. It seems the VB doesn't actually take up cpu cycles but goes into some disk access frenzy which it does not seem able to come out of. I've tried formatting to FAT and NTFS (fast and non-fast formats) and it still locks the system.

I'm using the PUEL version, on Ubuntu Heron (with the 18 kernel but tried with the 17)

theTAZ57 · Post by **theTAZ57** » 6. Jun 2008, 06:57

hi all
I downloaded le latest revision of VB, and it works

funnyname · Post by **funnyname** » 10. Jun 2008, 22:59

Not working for me either. I get the same error as the first post in this thread.

I uninstalled the previous version - and installed the latest from Sun. virtualbox_1.6.2-31466_Ubuntu_hardy_i386.deb and it will not work.\

Any more suggestions? Would like to get this to work. This will show me not to upgrade kernels everytime Ubuntu tells me to.

funnyname · Post by **funnyname** » 13. Jun 2008, 03:35

BUMP -

- Still not working. Are there any suggestions. I would like to get it working after the update to kernel 2.6.24.18 generic.

Post by **Sasquatch** » 13. Jun 2008, 10:25

It works for me just fine as I said earlier in this topic. I will post my list of installed programs that might be needed for VB with version numbers, see if there is anything different with your list. Note that I use Xfce and you probably use Gnome, keep that in mind too.

funnyname · Post by **funnyname** » 14. Jun 2008, 02:12

Thanks for the help. Just for info - I am using Kubuntu 8.10 and loaded VirtualBox with the downloadable version, not the one in the repository.

Mon1018 · Post by **Mon1018** » 18. Jun 2008, 13:05

Thank you for the info. you seem to be a nice guy.