#14646 closed defect (fixed)
Can't access any guest VM after Ubuntu Upgrade
| Reported by: | aingeru | Owned by: | |
|---|---|---|---|
| Component: | VMM | Version: | VirtualBox 5.0.4 |
| Keywords: | Ubuntu Host Upgrade | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
Hello, My host is Ubuntu 15.04 64bit and my guest VM's (Windows 7, Debian 8, Fedora 22) were working just fine but after I accepted automatic Ubuntu updates none of them are able to start and I get the same message for all of them:
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
The upgrades in Ubuntu were:
Commandline: aptdaemon role='role-commit-packages' sender=':1.77' Install: linux-signed-image-3.19.0-30-generic:amd64 (3.19.0-30.33), linux-image-extra-3.19.0-30-generic:amd64 (3.19.0-30.33), linux-image-3.19.0-30-generic:amd64 (3.19.0-30.33), linux-headers-3.19.0-30-generic:amd64 (3.19.0-30.33), linux-headers-3.19.0-30:amd64 (3.19.0-30.33) Upgrade: linux-headers-generic:amd64 (3.19.0.28.27, 3.19.0.30.29), linux-signed-generic:amd64 (3.19.0.28.27, 3.19.0.30.29), linux-signed-image-generic:amd64 (3.19.0.28.27, 3.19.0.30.29), linux-image-generic:amd64 (3.19.0.28.27, 3.19.0.30.29), linux-generic:amd64 (3.19.0.28.27, 3.19.0.30.29)
Any guidance is appreciated
Attachments (1)
Change History (5)
by , 9 years ago
comment:1 by , 9 years ago
Actually there are two problems: Most likely you did not recompile your host kernel modules. There is a bug in VBox 5.0.4 which crashes the process instead of showing a proper error message. So the solution for you is to do
/etc/init.d/vboxdrv setup
then you will be able to start your VMs. And we will fix the bug which prevents showing the error message.
And to recompile your host kernel modules automatically after kernel upgrade you could also install the DKMS package which does this job.
follow-up: 4 comment:3 by , 9 years ago
@frank
After upgrading to VirtualBox-5.0.10 in Fedora 22 (kernel 4.2.5-201) the command "$ sudo /sbin/vboxconfig" didn't install the kernel modules as expected even though the exit code was "0".
Also, there's no "/etc/init.d/vboxdrv" installed with the RPM package.
I resolved this issue by issuing the following command, which actually did the job:
$ sudo /usr/sbin/rcvboxdrv setup
Regards.
comment:4 by , 9 years ago
Still happening after VBox upgrade from 5.0.10 to 5.0.12_104815 (kernel 4.2.7-300.fc23.x86_64):
[pnazar@argos ~]$ sudo /sbin/vboxconfig sudo: /sbin/vboxconfig: command not found
[pnazar@argos ~]$ sudo /usr/sbin/rcvboxdrv setup Stopping VirtualBox kernel modules [ OK ] Uninstalling old VirtualBox DKMS kernel modules [ OK ] Trying to register the VirtualBox kernel modules using DKMS[ OK ] Starting VirtualBox kernel modules [ OK ]
Regards.
Replying to unPablo:
@frank
After upgrading to VirtualBox-5.0.10 in Fedora 22 (kernel 4.2.5-201) the command "$ sudo /sbin/vboxconfig" didn't install the kernel modules as expected even though the exit code was "0".
Also, there's no "/etc/init.d/vboxdrv" installed with the RPM package.
I resolved this issue by issuing the following command, which actually did the job:
$ sudo /usr/sbin/rcvboxdrv setupRegards.
Win7 log