id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
12130	"Linked clones aren't cleaned up when ""Remove"" performed"	Metaseller		"A linked clone, removed, then recreated under the same name, has incorrect state.

Steps to repro:
1. Download DSL (I used 4.4.10 ISO)
2. Create a new VM, specifying ""Linux 2.4"" as type, and allocating it a small hard drive (512MB, huge for DSL); set the DSL ISO as its optical drive.
3. Boot the VM into DSL and, as root:
{{{
# fdisk /dev/hda
-- create new primary partition (n, accept defaults, w to quit)
# mkfs /dev/hda1
# mkdir hdd; mount /dev/hda1 hdd
# echo Hello, world! >hdd/hello
}}}
4. Shut down the VM, boot fresh, prove that the file is actually there:
{{{
# mkdir hdd; mount /dev/hda1 hdd
# cat hdd/hello
}}}
5. Make a linked clone of the VM with the default name. Boot the clone and change the file (""Goodbye, world!""). Shut down.
6. Boot either VM, see that the file is unchanged in base and changed in clone.
7. Shut both VMs down and delete the clone, removing all files. ** Important **
8. Boot the base again; file is (correctly) unchanged. Alter the file (""Hello, changed world!""), shut down.
9. Make a linked clone using the same default name. Boot the clone. What does the file have?

Expected result: ""Hello, changed world!"", because the new clone was created from a VM whose state was that.

Actual result: ""Hello, world!"" - the unchanged version. Not, as I first thought, the version that the clone had had under its previous name; it's reset to that clone's origin.

Doing all the exact same steps but using a new and unique name for the new clone works correctly (""Hello, changed world!""). At no time were two VMs with the same name in existence, but the reuse of the name causes odd results.

Some discussion at https://forums.virtualbox.org/viewtopic.php?f=7&t=57342 led to this being posted."	defect	closed	other	VirtualBox 4.2.10	fixed	clone		Linux	Linux