VirtualBox

Ticket #10264 (new defect)

Opened 2 years ago

Last modified 20 months ago

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

Reported by: Technologov Owned by:
Priority: blocker Component: other
Version: Keywords:
Cc: Guest type: other
Host type: other

Description

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"
  1. make new linked-clone "Windows XP Clone1"
  1. rename the linked-clone VM to "Windows XP Clone11"
  1. reboot host OS

Actual result:

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

-Technologov, 19.Feb.2012.

Attachments

Windows XP Clone1 11.vbox Download (13.4 KB) - added by Technologov 2 years ago.
linked-clone VM meta-data, corrupted.
Windows XP Platinum.vbox Download (52.6 KB) - added by Technologov 2 years ago.
Master VM meta-data, corrupted.

Change History

Changed 2 years ago by Technologov

linked-clone VM meta-data, corrupted.

Changed 2 years ago by Technologov

Master VM meta-data, corrupted.

comment:1 Changed 2 years ago by Technologov

This bug is still true for 4.1.14.

-Technologov

comment:2 Changed 2 years ago by klaus

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

comment:3 Changed 2 years ago by 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.

comment:4 Changed 20 months ago by Era Scarecrow

Related or identical issue: Ticket #10849

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use