Page 1 of 1

Workaround for cloning disks - only one problem left

Posted: 16. Jan 2009, 00:39
by Matthias70
Hi,
clonehd in Virtualbox 2.1 does not work! The machine does not start, when cloned with clonehd :-(
So I cloned my vdi file with this code:

Code: Select all

"F:\VirtualBox\VBoxManage.exe" clonehd -format VMDK disk_1.vdi disk_2.vdi
The new machine with the cloned drive works perfect.

There is only on difference in the virtual media manager!
The format of the vdi file is vmdk although the fileextension is .vdi?

Does anyone know if this could be a problem?
And does anyone know how to convert the vdi file to format vdi without losing data?

Thanks
Matthias

Posted: 16. Jan 2009, 01:43
by baf
Try instead:
Copy oldfile newfile
VBoxManage internalcommands sethduuid <filepath>

And see how that works.

Posted: 16. Jan 2009, 21:36
by Matthias70
Thanks, it works :-)
Matthias

Posted: 20. Jan 2009, 17:18
by Kahuna
baf wrote:Try instead:
Copy oldfile newfile
VBoxManage internalcommands sethduuid <filepath>

And see how that works.
I'm having similar problems with clonevdi - could you expand on your reply please 'baf' (nOOb speak please Bud).

Cheers

Posted: 20. Jan 2009, 22:25
by Sasquatch
Kahuna wrote:
baf wrote:Try instead:
Copy oldfile newfile
VBoxManage internalcommands sethduuid <filepath>

And see how that works.
I'm having similar problems with clonevdi - could you expand on your reply please 'baf' (nOOb speak please Bud).

Cheers
Copy the VDI you want to clone to a new location. Now you have that, open a command prompt. Change it's location so you're in the VB install folder (cd c:\program files\sun xvm virtualbox by default). Then run the VBoxManage command provided by baf. Like this:

Code: Select all

vboxmanage.exe internalcommands setvdiuuid c:\temp\clone.vdi
Where of course the last part is the full path of the VDI file you copied. After that, change it's name so you know it's the clone and register it in VB.

Posted: 21. Jan 2009, 14:09
by Kahuna
Thanks Sasquatch - I'll try that today.

Cheers

Posted: 23. Jan 2009, 00:00
by Sasquatch
The new release should fix the cloning issue.