Custom Query (16363 matches)
Results (2002 - 2004 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2051 | fixed | vboxdrv and vboxnet don't automatically start with SabayonLinux | ||
| 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. |
|||
| #2053 | worksforme | kvm check fails | ||
| Description |
I have problems to start an vm because vbox 2.0.0 tells me there is kvm enabled but thats not true. Its definitly an module: develop:/home/crissi# modinfo kvm filename: /lib/modules/2.6.25-2-686/kernel/arch/x86/kvm/kvm.ko license: GPL author: Qumranet depends: vermagic: 2.6.25-2-686 SMP mod_unload 686 and its not loaded: develop:/home/crissi# lsmod | grep kvm develop:/home/crissi# Happens on Debian Lenny running 2.6.25-2-686 distribution kernel. Additional info: I had installed 1.6.4 which was running fine. Then I upgraded to 1.6.6 and it runs fine too. Then I upgraded to 2.0.0 (using the VirtualBox-1.6.6-Linux_x86.run binary) and it claims about kvm. I went back to 1.6.6 (fixed the xml too) and it also claims about kvm. I dont had rebooted from working vbox 1.6.4. |
|||
| #2054 | wontfix | 2.0.0 can't be run from outside /Applications | ||
| Description |
VirtualBox 2.0 can't be run from anywhere other than the /Applications folder. This is a regression from 1.6, and poor behaviour for any OS X app. Perhaps this restriction is to simplify the new update checks, but plenty of other Mac applications handle this properly... and even the ones that don't, still allow you to run the application from outside /Applications: they just install any updates into /Applications, rather than correctly over-writing the previous version. |
|||

