Custom Query (16363 matches)
Results (2005 - 2007 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2050 | worksforme | VBoxSDL restores state slowly on Ubuntu Hardy (but not Gutsy) | ||
| Description |
On my machines, restoring the saved state of a VM with ~512Mb RAM generally takes about 8 secs or so, regardless of frontend. The only exception is VBoxSDL running on Ubuntu Hardy, which seems to take ~22 secs or so. The same version (1.6.6) running on Gutsy does not exhibit this problem. Hardly a major issue, but I'm working on an appliance / kiosk use for VBox, and it would be nice to have start up as fast as possible :) Incidentally, I tried downgrading the libsdl1.2debian* packages on Hardy back to the Gutsy versions, in case that was the issue, but it didn't help. |
|||
| #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. |
|||
| #2052 | fixed | Keyboard problems on X11 hosts in version 2.0 | ||
| Description |
This ticket is for reporting problems with keyboard handling on X11 hosts (currently Linux and Solaris) in VirtualBox 2.0. |
|||

