VirtualBox

Ticket #2708 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

clonevdi doesn't respect vdifolder property

Reported by: helix84 Owned by:
Priority: minor Component: VM control
Version: VirtualBox 2.0.6 Keywords:
Cc: Guest type: Linux
Host type: Linux

Description

I set vdifolder property to /opt/vm. After trying

VBoxManage clonevdi test/test.vdi db/db.vdi

throws error

Could not access hard disk image '/home/ctenar/.VirtualBox/test/test.vdi' (VERR_FILE_NOT_FOUND)

I know I should use absolute paths as documented in user manual. But I think this location should respect vdifolder instead of its default value.


/opt/vm$ VBoxManage list systemproperties
VirtualBox Command Line Management Interface Version 2.0.6
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

Minimum guest RAM size:      4 Megabytes
Maximum guest RAM size:      3584 Megabytes
Maximum video RAM size:      128 Megabytes
Maximum VDI size:            2097151 Megabytes
Default VDI folder:          /opt/vm
Default machine folder:      /opt/vm
VRDP authentication library: VRDPAuth
Webservice auth. library:    VRDPAuth
Hardware virt. extensions:   no
Log history count:           3
/opt/vm$ VBoxManage clonevdi test/test.vdi db/db.vdi
VirtualBox Command Line Management Interface Version 2.0.6
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

[!] FAILED calling virtualBox->OpenVirtualDiskImage(Bstr(argv[0]), vdi.asOutParam()) at line 3460!
[!] 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/ctenar/.VirtualBox/test/test.vdi' (VERR_FILE_NOT_FOUND)
[!] Component   = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916}
[!] Callee      = IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137}

Change History

comment:1 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

This should work at least as expected with the latest release 2.2.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use