Cannot add VM.xml after reinstallation

[Edward Yang]

It's completely out of expectation again.

I recently re-installed Windows XP and of course re-installed VirtualBox.

I wanted to add two guest OS. I selected Machine->Add from main menu. Somehow, I was able to add one of them, but I failed to add Fedora.xml. It complained about not finding a virtual disk with guid {xxx}. The disk is there, nothing changed. This VM has a saved state, and I don't want to lose the state.

After many tries, I suddenly had an idea - the disk was not in Virtual Media Manager. so I started VMM, but it did now allow me to add a VD directly!

So I created a new VM definition and select the VD. Now the VD was in VMM and finally I could add the existing Fedora.xml and the saved state is kept.

[Edward Yang]

I know how the bug comes.

If a VM has saved state, then it will not be able to add to VM Manager after a fresh new installation.

[Edward Yang]

Another related bug of this bug is that if I remove the 'temporary' VM that references the problematic VDI file, then it disappears again in VMM.

[Edward Yang]

Please ignore this and close it.

[Frank Mehnert]

Thanks!