Custom Query (16363 matches)
Results (445 - 447 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10834 | obsolete | vboxmanage controlvm <vm> poweroff hangs | ||
| Description |
I start several XP guests via Headless, then "controlvm poweroff" and "snapshot <vm> restorecurrent" before repeating the sequence. About every 200-300 cycles, the vboxmanage controlvm <vm> poweroff will hang, and continually spit errors to the log per the attached. I read in an old forum that concurrently powering off multiple guests can cause a hang, so I've wrapped mine in a lock that ensures 2 second delays between poweroff's of different guests. That does not eliminate the problem. |
|||
| #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)
|
|||
| #9324 | obsolete | vboxmanage clonehd fails if target file is registered but does not exist | ||
| Description |
This has nothing to do with the absolute file names and it appeared after 4.0.6. If the disk target is registered, but the file does not exists, clonehd used to succeed. Now it fails after successfully copying the file (it probably first copies the file and updates the UUID afterwards). Here is an example output, created on Windows Server 2008: E:\VirtualBox\HardDisks>vboxmanage clonehd tmp1.vdi tmp2.vdi
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Clone hard disk created in format 'VDI'. UUID: c79b05b3-0118-4653-9b59-f99d7d8965d0
E:\VirtualBox\HardDisks>del tmp2.vdi
E:\VirtualBox\HardDisks>vboxmanage clonehd tmp1.vdi tmp2.vdi
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to clone hard disk. Error message: Cannot register the hard disk 'E:\VirtualBox\HardDisks\tmp2.vdi' {710285eb-c083-40db-ae4f-7c411a5990c1} because a hard disk 'E:\VirtualBox\HardDisks\tmp2.vdi' with UUID {c79b05b3-0118-4653-9b59-f99d7d8965d0} already exists
The old behavior makes more sense. If that is not an option, the clonehd command has to fail before copying the file. |
|||

