Custom Query (16363 matches)
Results (1480 - 1482 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1512 | worksforme | VirtualBox throws internal error when starting any VM | ||
| Description |
The first time you try to start a VM after installing or updating VirtualBox, it works. On all successive attempts (even after quitting and relaunching), it fails: VM creation failed (GVMM).
VBox status code: -32 (VERR_INTERNAL_ERROR).
Result Code:
0x80004005
Component:
Console
Interface:
IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
I'm using VirtualBox on Mac OS X 10.4.10 on a Mac Pro. This bug is not specific to any virtual machine. I just created a new one for Ubuntu 8.10 and it did the same thing. This bug seems to be the sequel to #191, which had the exact same behavior, only a different error message (“out of memory”). The virtual machine is set to 1024 MiB; MemMeters tells me that I have 4081 MiB free system-wide. |
|||
| #1513 | fixed | Strange pointer integration with kubuntu 8.04 guest | ||
| Description |
My host : gentoo linux 2.6.24.6 with vbox 1.5.6 and vbox-modules 1.5.7 My guest : kubuntu 8.04 with vbox-modules 1.5.7 Mouse integration works, but only on this guest my X cursor mouse don't desapear over the guest. So i can see the mouse pointer of my guest and over this one, my mouse pointer. |
|||
| #1514 | fixed | Virtualbox 1.5.6_OSE bug | ||
| Description |
Looks like using relay crashes it. I'm using close to the out-of-the-box relay from kernel 2.6.25 and am getting handler faults; then everything dies and I have to restart it. If the newer one works with this could you please tell me? I don't want to have to force it to insert itself into the kernel only to have more failures. Thanks. --Marlow |
|||

