VirtualBox

Ticket #2813 (closed defect: fixed)

Opened 7 months ago

Last modified 5 months ago

clonehd/clonevdi creating corrupted clones of VDI image => Fixed in SVN

Reported by: Thalic Assigned to:
Priority: major Component: virtual disk
Version: VirtualBox 2.1.0 Keywords: clonehd clonevdi corrupt image
Cc: Guest type: Windows
Host type: Windows

Description

Cloning a dynamic VDI file using clonehd/clonevdi results in corrupt clone. The cloned VDI file is smaller than the original VDI file. Cloned Windows guest failed to boot. clonehd/clonedvi did not report any errors during cloning.

Original VDI file was about 1.5GB, cloned file about 1.4GB. Trying to boot cloned guest resulted in following error message: 

A disk read error occurred
Press Ctrl+Alt+Del to restart

After booting original VDI, it grew a bit to 1.6GB, clone created from this file was about 1.5GB. Trying to boot cloned guest resulted in following error message: 

Windows could not start because the following file is missing
or corrupt:
<Windows root>\system32\hal.dll
Please re-install a copy of the above file.

Cloning the original VDI into a VDMK image did not cause any of the aforementioned problems.

Other forum user mentioned same problem and downgraded to 2.0.6 for testing and reported that problem is not present in 2.0.6.

Host: Windows XP SP3
Guest: Windows XP SP2 (right after installation, no updates installed)
Original VDI image created on VirtualBox 2.1.0

Forum thread: http://forums.virtualbox.org/viewtopic.php?p=50519

Change History

2008-12-22 09:48:53 changed by ppgrainbow

The other day, I tried to create a backup clone of the Windows XP guest OS and it had no effect at all. The progress bar just stayed at 0% all of the time.

I'm hoping that Sun fixes the glitch that causes hard disk images to not be cloned properly. Until then, it's best that you use the Windows NT Backup utility.

2008-12-22 10:13:29 changed by wallace

I can tell the same bug about the clonehd command with the same characteristics as the first post.

I hope it could be fixed as soon as possible.

(follow-up: ↓ 4 ) 2008-12-28 15:41:05 changed by sagattarii

Same here :( Version 2.1.0

Linux Host, Windows and Linux Guests.

Workaround: Copy it by hand and then use "VBoxManage internalcommands sethduuid file.vdi" to set a new uuid.

(in reply to: ↑ 3 ; follow-up: ↓ 5 ) 2008-12-29 00:32:18 changed by ppgrainbow

Replying to sagattarii:

Same here :( Version 2.1.0 Linux Host, Windows and Linux Guests. Workaround: Copy it by hand and then use "VBoxManage internalcommands sethduuid file.vdi" to set a new uuid.

A better idea would be to wait until a new version of VirtualBox comes out. _

(in reply to: ↑ 4 ; follow-up: ↓ 9 ) 2009-01-04 22:50:59 changed by Philip Verstraeten

Replying to ppgrainbow:

Replying to sagattarii:

Same here :( Version 2.1.0 Linux Host, Windows and Linux Guests. Workaround: Copy it by hand and then use "VBoxManage internalcommands sethduuid file.vdi" to set a new uuid.

A better idea would be to wait until a new version of VirtualBox comes out. _

Worked as a charm ! Thanks...

2009-01-05 01:50:02 changed by aeichner

Fixed in svn. Thanks for the report.

2009-01-05 09:05:01 changed by frank

  • summary changed from clonehd/clonevdi creating corrupted clones of VDI image to clonehd/clonevdi creating corrupted clones of VDI image => Fixed in SVN.

2009-01-05 09:09:40 changed by Thalic

Excellent, thank you!

(in reply to: ↑ 5 ) 2009-01-05 14:06:20 changed by ppgrainbow

Replying to Philip Verstraeten:

Replying to ppgrainbow:

Replying to sagattarii:

Same here :( Version 2.1.0 Linux Host, Windows and Linux Guests. Workaround: Copy it by hand and then use "VBoxManage internalcommands sethduuid file.vdi" to set a new uuid.

A better idea would be to wait until a new version of VirtualBox comes out. _

Worked as a charm ! Thanks...

You're welcome! _

(follow-up: ↓ 11 ) 2009-01-19 10:41:57 changed by DanielKulesz

Same here - using clonevdi on a Linux image results in a non-bootable image where even the filesystem cannot be mounted.

Regarding this workaround: Are there any caveats in using "VBoxManage internalcommands sethduuid file.vdi" on a copied file compared to the intended way? I've seen clonevdi doing some sanity checks on the copied image, but apart from that - does it do more than copying the file and setting a new uuid?

(in reply to: ↑ 10 ) 2009-01-19 13:04:32 changed by ppgrainbow

Replying to DanielKulesz:

Same here - using clonevdi on a Linux image results in a non-bootable image where even the filesystem cannot be mounted. Regarding this workaround: Are there any caveats in using "VBoxManage internalcommands sethduuid file.vdi" on a copied file compared to the intended way? I've seen clonevdi doing some sanity checks on the copied image, but apart from that - does it do more than copying the file and setting a new uuid?

I don't have the slightest idea.

The only way I did this was to perform a backup copy of the data on Windows XP guest onto my USB hard drive. I did that by using one of the shared folders on drive W.

The last time I made a backup of all of the data was on the 18th of last month and the WindowsXP.bkf file contains 7.34 GB worth of data...so, if something were to go wrong, I have the backup file with me.

So...the other choice is backup all of the data onto a shared folder incase something screws up.

2009-01-21 14:47:54 changed by sandervl73

  • status changed from new to closed.
  • resolution set to fixed.

© 2009 Sun Microsystems, Inc.
Contact – Privacy policy