Custom Query (16363 matches)
Results (1402 - 1404 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1432 | invalid | VirtualBox kernel driver not installed | ||
| Description |
Is not possible opening sistem attached error. Sorry for bad english y' am speak italian or french Tank, regards attached VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root. VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED). Codice d'uscita: 0x80004005 Componente: Console Interfaccia: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}
|
|||
| #1433 | fixed | stuck in fullscreen, host key doesn't work | ||
| Description |
Linux host, XP guest, VBox 1.5.6. Been using Seamless, worked nice, one day I resume the VM (nothing changed that I knew of) and it goes fullscreen and stays there no matter how often I press anything. Lowering resolution of the guest only gives me a smaller area with black borders, display stays in host's native resolution. Only way to get my system back is ssh in and stop the VM with VBoxManager. |
|||
| #1434 | worksforme | Host system reported that the file size limit - Reported incorrectly | ||
| Description |
I am running Ubuntu 7.10 on a Dual Core X6800 with 4GB Ram. I am running a WinXp SP2 client with a C: Drive VDI of 100GB and a D: Drive VDI of 100GD; both are dynamic disks. The Ubuntu host is running all partitions/file systems as ext3. All partitions are at least 300GB with the two partitions that hold the VDI files having over 200GB free space on each. I keep getting the following error. Usually happens when running a file sharing program on the WinXp guest. "Host system reported that the file size limit has been exceeded. VM execution is suspended. You need to move the file to a filesystem which allows bigger files." Given the amounts of space I have dedicated to the VDIs and base file systems; and the fact I am using ext3; how can this be? Is this a bug in the software? |
|||

