VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (484 - 486 of 16363)

Ticket Resolution Summary Owner Reporter
#9286 duplicate vboxdrv blocks suspend domingo
Description

After upgrading to 4.1 r73009 the vboxdrv service blocks the host machine to go into suspend.

I cannot tell if I get a kernel panic but the caps lock button lights up.

If I stop the driver service before I send the host into suspend it succeeds. The second I start it and try to suspend it fails.

The failure occurs no matter what guest I've running or even without starting Virtualbox at all. Right after boot up I can try to send the host into suspend and it will fail/succeed depending on if vboxdrv is started or not.

The host is Ubuntu Natty running stock kernel 2.6.38-10-generic

#2051 fixed vboxdrv and vboxnet don't automatically start with SabayonLinux dave_p_b
Description

The files /etc/init.d/vboxdrv and /etc/init.d/vboxnet don't work with SabayonLinux. SabayonLinux contains both /etc/gentoo-release and /etc/sabayon-release files which confuses the vboxdrv and vboxnet scripts so they think that the OS is gentoo instead of sabayonlinux. The error produced by running either of these scripts is /etc/init.d/vboxdrv: line 97: /sbin/functions.sh: No such file or directory. This is because the functions.sh file, which in gentoo is placed in the /sbin/ folder, in SabayonLinux it is contained in the /lib/rc/sh/ folder, with a link from the /etc/init.d/ folder. E.g. /etc/init.d/functions.sh -> /lib/rc/sh/functions.sh.

When the file VirtualBox-1.6.6-Linux_amd64.run is run, it reports that the vboxdrv module failed to be built. However, this is incorrect. It is built, but to load the modules you have to do it manually E.g modprobe vboxdrv. The /etc/init.d/vboxnet script, however, cannot be run manually.

I have attached the vboxdrv and vboxnet scripts that I changed to recognize the SabayonLinux OS. However, they still don't launch automatically, even after adding them by using the rc-update add command. I don't think that either /etc/init.d/vboxdrv or /etc/init.d/vboxnet scripts work with openrc-0.2.5-r1 or baselayout-2.0.0 that SabayonLinux uses in it's latest 3.5 release.

Hope this can be fixed soon.

#5686 fixed vboxdrv and vboxguest export the same symbols causing conflict on a host that is also used as a guest => Fixed in SVN Seth Randall
Description

I run a Ubuntu Linux install as my primary desktop. I also run it as a guest from my Windows partition. When running as a host the install can't load the vboxnetflt module because it tries to load vboxguest as a dependency, but vboxdrv is already loaded with the exported symbols vboxguest tries to register.

Perhaps there should be a separate module that they all rely on called vboxcommon that has the functions that are common to both.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy