Opened 16 years ago
Last modified 15 years ago
#4797 closed defect
VBox refuses to start VM's reports VM driver not accessible — at Version 1
| Reported by: | Marsh | Owned by: | |
|---|---|---|---|
| Component: | installer | Version: | VirtualBox 2.0.10 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Linux |
Description (last modified by )
Upgraded to VirtualBox 2.0.10-50334 from 2.0.8-44071. After upgrade Vbox immediately began reporting VM inaccessible errors (See error report below).
Recompiled kernel modules using /etc/vboxdrv setup command with same result.
Downgraded back to 2.0.8 VBox is back to working.
VBox does not appear be logging to the VBox.log file so I have extracted all the vbox messages I could find in other log files. Admittedly it is not much to go on but it is all that I have available.
Distro: Ubuntu (Dapper 6.06LTS)
Platform: AMD64
Kernel 2.6.15-54
Error Reports from VBox:
VERR_VM_DRIVER_NOT_ACCESSIBLE (rc=-1909)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Re-setup the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.
Change History (2)
by , 16 years ago
comment:1 by , 16 years ago
| Component: | other → installer |
|---|---|
| Description: | modified (diff) |
| Version: | VirtualBox 2.0.0 → VirtualBox 2.0.10 |
Well, I'm not aware of any change of the Linux installer between 2.0.8 and 2.0.10. I assume you installed the Dapper (.deb) package from our website, correct?
When you install VBox 2.0.10, what are the permissions of /dev/vboxdrv (/bin/ls -l /dev/vboxdrv)?
extracts of various linux log files