Opened 13 years ago
Closed 8 years ago
#10264 closed defect (fixed)
Linked Clones: Data-corruption on VM rename, unbootable VM
| Reported by: | Technologov | Owned by: | |
|---|---|---|---|
| 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:
- make new VM "Windows XP Platinum"
- make new linked-clone "Windows XP Clone1"
- rename the linked-clone VM to "Windows XP Clone11"
- reboot host OS
Actual result:
the differencing disk in the linked clone VM will become inaccessible. VM unbootable.
-Technologov, 19.Feb.2012.
Attachments (2)
Change History (7)
by , 13 years ago
| Attachment: | Windows XP Clone1 11.vbox added |
|---|
comment:3 by , 12 years ago
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:5 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Should be fixed for a long time now.
Note:
See TracTickets
for help on using tickets.
linked-clone VM meta-data, corrupted.