VirtualBox

Ticket #3181 (closed defect: fixed)

Opened 5 years ago

Last modified 3 years ago

2.1.2 VBoxManage clonevdi doesn't work after upgrade from 2.0.6

Reported by: ezrasimeloff Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 2.1.2 Keywords: clonevdi
Cc: Guest type: other
Host type: other

Description (last modified by sandervl73) (diff)

I can no longer clonevdi.

It worked great on 2.0.6 with Mac OS X for my solaris guest OS's but now I've upgraded to 2.1.2 I cannot get the vdi's cloned.

What I have not tried is cloning an image I created using this version. So the VDI's were created under version 2.0.6 I don't know if this is relevant.

VBoxManage clonevdi Solaris10TOI.vdi Solaris10TOIRoleManagerStart.vdi
VirtualBox Command Line Management Interface Version 2.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

[!] FAILED calling a->virtualBox->OpenHardDisk2(src, srcDisk.asOutParam()) at line 369!
[!] Primary RC  = VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error
[!] Full error info present: true , basic error info present: true 
[!] Result Code = VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error
[!] Text        = Could not get the storage format of the hard disk '/Users/ezrasimeloff/Library/VirtualBox/HardDisks/Solaris10TOI.vdi' (VERR_FILE_NOT_FOUND)
[!] Component   = HardDisk2, Interface: IHardDisk2, {ed6e2525-c2fd-42a4-917a-7a9045ac9e15}
[!] Callee      = IVirtualBox, {339abca2-f47a-4302-87f5-7bc324e6bbde}

Change History

comment:1 Changed 5 years ago by netinhoteixeira

The same happens on openSUSE 11.1 with VirtualBox 2.1.2.

comment:2 Changed 5 years ago by ThatFoxyKid

Can confirm that this bug exists with v2.1.2 on Linux 2.6.27.10 #3 SMP PREEMPT (Zenwalk 5.4). Perhaps this should be moved to a non-specific platform section.

comment:3 Changed 5 years ago by sandervl73

  • Host type changed from Mac OS X to other
  • Guest type changed from Solaris to other
  • Summary changed from 2.1.2 VBoxManage clonevdi doesn't work on a MAC OS 10 after upgrade from 2.0.6 to 2.1.2 VBoxManage clonevdi doesn't work after upgrade from 2.0.6

comment:4 Changed 5 years ago by sandervl73

  • Description modified (diff)

comment:5 Changed 5 years ago by sandervl73

The error says file not found, so are you sure '/Users/ezrasimeloff/Library/VirtualBox/HardDisks/Solaris10TOI.vdi' does actually exist?

comment:6 Changed 5 years ago by ThatFoxyKid

This turned out to be a PICNIC for me (Problem In Chair Not In Computer).

clonehd and clonevdi function in the filesystem with .VirtualBox/HardDisks as the root directory. You must specify the .vdi image to clone in relationship to this directory or specify the FULL PATH.

For example, the following two commands will work:

VBoxManage clonehd "Windows XP.vdi" "Windows Copy.vdi"
VBoxManage clonehd "/home/username/.VirtualBox/HardDisks/Windows XP.vdi" "/home/username/.VirtualBox/HardDisks/Windows Copy.vdi"

But the following will not:

VBoxManage clonehd ".VirtualBox/HardDisks/Windows XP.vdi" ".VirtualBox/HardDisks/Windows Copy.vdi"

This solved the issue for me. Also be sure to enclose your paths in quotes if they include spaces or special characters.

comment:7 Changed 5 years ago by ezrasimeloff

I love the acronym!

Interesting information -- It does indeed work with full paths! which is outstanding.

However this is a regression from the 2.0.6 version.

This is totally wacky behavior why on earth would it behave this way? In my view this would remain a bug unless there is some pretty interesting explanation - longer then one line - why this behavior isn't.

1> A regression from previous versions. 2> Odd.

thanks Ezra.

comment:8 Changed 5 years ago by pjw1965

I can confirm this:

$ ls /var/tmp/VirtualBox -ldlrwxrwxrwx 1 me users 22 2008-05-15 07:40 /var/tmp/VirtualBox -> /mnt/media/VirtualBox/

clonehd and clonevdi works not when used a Symbolic Link as in /var/tmp/VirtualBox/VDI/harddisk.vdi, but works with absolut direct path /mnt/media/VirtualBox/VDI/harddisk.vdi (as in ~/.VirtualBox/VirtualBox.xml used).

This should be fixed. The error-Message is confusing!!!

[!] Result Code = VBOX_E_IPRT_ERROR (0x80BB0005) - Runtime subsystem error [!] Text = Could not get the storage format of the hard disk '/var/tmp/VDI/harddisk.vdi' (VERR_FILE_NOT_FOUND)

comment:9 Changed 3 years ago by frank

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

Please reopen if still relevant with VBox 4.0.4.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use