Custom Query (16363 matches)
Results (427 - 429 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2594 | fixed | vboxmanage: make it easier to work with VDI files from different locations than ~/.VirtualBox/VDI | ||
| Description |
I have a local direcotry for VirtualBox images as I don't want to store them via NFS. Now when I want to clone an image I get this: ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi Debian-Etch-Template.vdi Debian-Etch-grsec.vdi
VirtualBox Command Line Management Interface Version 1.6.6_OSE
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.
[!] FAILED calling virtualBox->OpenVirtualDiskImage(Bstr(argv[0]), vdi.asOutParam()) at line 3307!
[!] Primary RC = NS_ERROR_FAILURE (0x80004005) - Operation failed
[!] Full error info present: true , basic error info present: true
[!] Result Code = NS_ERROR_FAILURE (0x80004005) - Operation failed
[!] Text = Could not access hard disk image '/home/ms/.VirtualBox/VDI/Debian-Etch-Template.vdi' (VERR_FILE_NOT_FOUND)
[!] Component = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
I can do: ms@mango:~/lokal/VirtualBox-Images> ln -s /home_lokal/ms/VirtualBox-Images/Debian-Etch-Template.vdi /home/ms/.VirtualBox/Debian-Etch-Template.vdi And then: ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi ./Debian-Etch-Template.vdi Debian-Etch-grsec.vdi ms@mango:~/lokal/VirtualBox-Images> vboxmanage clonevdi ./Debian-Etch-Template.vdi Debian-Etch-rsbac.vdi But now vboxmanage creates the images in ~/.VirtualBox/VDI. Thus I have to move them around again: ms@mango:~/lokal/VirtualBox-Images> mv ~/.VirtualBox/VDI/Debian-Etch-{grsec,rsbac}.vdi .
Thus all I ask is that vboxmanage respects the path I give instead of insisting on ~/.VirtualBox/VDI. I know I could symlink VDI completely, but I want to have the option to keep some images via NFS. I tested with VirtualBox 1.6.6 as thats the latest OSE edition I can get via backports.org for Debian Etch. I can try with a newer one in case its needed. The issue is minor, but rather annoying. |
|||
| #15334 | fixed | vboxmanage startvm reports success even if virtualization is turned of and the vm won't start | ||
| Description |
vboxmanage startvm reports: VM successfully started, but the VM is not started, and if you try to start the vm from the GUI, you get an error message with the error code: VERR_VMX_MSR_ALL_VMX_DISABLED I'm running a Debian wheezy64 guest on Windows 7 SP1. So the workaround is to enable virtualization in the BIOS, but I would like to know that my script starting the server failed, instead of succeeded. |
|||
| #12397 | fixed | vboxmanage startvm crashes after restorestate | ||
| Description |
After powering off a machine and doing restorestate, vboxmanage startvm fails. When trying the same command again it works. When doing just poweroff and startvm (without restorestate) it works just fine. root@Darkside:~/cuckoo/utils# VBoxManage controlvm cuckoo1 poweroff 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% root@Darkside:~/cuckoo/utils# VBoxManage snapshot cuckoo1 restorecurrent Restoring snapshot a402eb58-481f-4ace-b17e-4409101436c3 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% root@Darkside:~/cuckoo/utils# VBoxManage startvm cuckoo1 Waiting for VM "cuckoo1" to power on... VBoxManage: error: No error info VBoxManage: error: Details: code NS_ERROR_CALL_FAILED (0x800706be), component ProgressProxy, interface IProgress root@Darkside:~/cuckoo/utils# VBoxManage startvm cuckoo1 Waiting for VM "cuckoo1" to power on... VM "cuckoo1" has been successfully started. |
|||

