Custom Query (16363 matches)
Results (334 - 336 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11237 | fixed | vhd is rejected after disk fill | ||
| Description |
Host and guest both are Windows XP. A process in guest took too much disk space and host drive was filled, a error appeared in guest, but I was able to shutdown it correctly. After shutdown I cannot run this VM again, installing fresh version of VirtualBox did not help. I have tried re-adding drive. This error appears: Failed to open the hard disk WinXPSP2.VHD. Could not get the storage format of the medium 'WinXPSP2.VHD' (VERR_NOT_SUPPORTED). Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: Medium Interface: IMedium {29989373-b111-4654-8493-2e1176cba890} Callee: IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2} Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) |
|||
| #4083 | obsolete | vesa driver crashes X when an application tries to use Composite with XRender | ||
| Description |
I use Slackware64-current in a VM. When I try to start up KDE-4.2.3 inside the VM, with the default configuration files, the xserver crashes. By default the vesa-driver is being used. KDE4 tries to enable Desktop Effects based on XRender if it finds the vesa-driver. This does work fine on a real machine, but crashes the xserver inside virtualbox. Tested version was VirtualBox 2.2.2, Xorg-server 1.4.2, xf86-video-vesa-1.3.0 |
|||
| #1501 | fixed | very high cpu utilisation if usb 2.0 is enabled | ||
| Description |
After upgrading from VirtualBox 1.5.6 to 1.6.0 on a Mandriva 2007.1 host, I noticed that the cpu utilisation for the VirtualBox process was near 80% when the guest OS (Windows 2000 Professional) was running - although the guest OS showed an utilisation of less than 10%. Before upgrading I was used to an cpu utilisation for the VirtualBox process of less than 15% (guest cpu utilisation + maximum of 5%). Disabling the usb 2.0 option gives again an cpu utilisation of 15%. |
|||

