Custom Query (16363 matches)
Results (856 - 858 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #7442 | worksforme | Virtualbox GUI crash on Windows 7 using 3.2.8 | ||
| Description |
Here is the information from the W7 Event Viewer: Faulting application name: VirtualBox.exe, version: 3.2.8.0, time stamp: 0x4c5aa88b Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802 Exception code: 0xc0000005 Fault offset: 0x000000000005302d Faulting process id: 0x1fe0 Faulting application start time: 0x01cb4e8734355120 Faulting application path: C:\PROGRA~1\Oracle\VIRTUA~1\VirtualBox.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: cc3ea0e0-ba87-11df-b60c-080027008043 Specifically this crash seems to happen when I have two Linux guests that are performing heavy I/O to one SATA hard drive. Virtualbox is running on a Windows 7 Quadcore with 8 GB of memory. |
|||
| #9584 | obsolete | vboxmanage closemedium disk broken: "The object is not ready", worked in 3.x | ||
| Description |
VBoxManage closemedium disk deleteme.vdi --delete gives VBoxManage.exe: error: The object is not ready VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005), component Medium, interface IMedium, callee IUnknown Context: "FindMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, pMedium.asOutParam())" at line 174 of file VBoxManageDisk.cpp The same result with full path to the vdi or without the extension; in fact whatever I write as the disk name I get the same error. It worked in 3.x and the vdi can be removed using the GUI. I can't use --delete when unregistering the VM because I want to keep the OS disk. MAYBE RELATED: some other guy at http://daniel.hepper.net/blog/ got $ VBoxManage list vms
"" {b68ed7a7-6e72-4f16-a438-8775cd80d9b3}
$ VBoxManage unregistervm {b68ed7a7-6e72-4f16-a438-8775cd80d9b3} --delete
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005),
component Machine, interface IMachine, callee nsISupports
Context: "Delete(ComSafeArrayAsInParam(aMedia),
pProgress.asOutParam())" at line 175 of file VBoxManageMisc.cpp
Segmentation fault
some other guy at http://forums.virtualbox.org/viewtopic.php?f=7&t=38150 Simply unregistering the machine without detaching the drives first seems to work, however unregistering the machine with the '--delete' flag gives: Code: Select all Expand viewCollapse view
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005),
component Machine, interface IMachine, callee nsISupports
Context: "Delete(ComSafeArrayAsInParam(aMedia),
pProgress.asOutParam())" at line 167 of file VBoxManageMisc.cpp
Segmentation fault (core dumped)
|
|||
| #9585 | obsolete | Immutable disk mounted to multiple VMs crash on resume saved state | ||
| Description |
Immutable disk type has changed behavior or is broken. Previously we have used it to lock an OS disk and attach it to multiple VMs (which get their own difference files). Now when attaching it as immutable to multiple VMs you can't start more than one VM and you get an error about read-only. Suddenly for no apparent reason it started working with multiple VMs but there's a bug: When resuming saved state the VM freezes with corrupted display. Multi-attach works but sometimes it has the same bug. |
|||

