Linked Clones: Data-corruption on VM rename, unbootable VM

[Technologov]

Host: Windows XP, VBox 4.1.8

Hi,

Doing a rename of a linked-clone VM then rebooting host results in "inaccessible VDI", and non-bootable guest OS.

Steps to reproduce:

1. make new VM "Windows XP Platinum"

2. make new linked-clone "Windows XP Clone1"

3. rename the linked-clone VM to "Windows XP Clone11"

4. reboot host OS

Actual result:

the differencing disk in the linked clone VM will become inaccessible. VM unbootable.

-Technologov, 19.Feb.2012.

[Technologov]

linked-clone VM meta-data, corrupted.

[Technologov]

Master VM meta-data, corrupted.

[Technologov]

This bug is still true for 4.1.14.

-Technologov

[klaus]

This is a very nasty and hard to fix bug...

[klaus]

In trunk this is fixed with r41231, and I need to find a way to apply the same idea to 4.1. Shouldn't be extremely difficult any more.

[Era Scarecrow]

Related or identical issue: Ticket #10849