VBox 3.1.0: "FATAL: Could not read from the boot medium!"

[abcuser]

Hi,
today I have installed VirtualBox 3.1.0. I did the following:
1. clone VDI file using CloneVDI tool with compacting option
2. deleted original (huge) VDI file from file system
3. renamed cloned file to original file name
4. remove existing VDI from Virtual Media Manager
5. add cloned VDI to Virtual Media Manager
6. run virtual machine.

Right after Sun's VirtualBox splash screen and before GRUB screen I get error:
"FATAL: Could not read from the boot medium! Sytem halted."

This looks like something was going wrong with CloneVDI tool, but it was not! CloneVDI works fine. Why? Read on.
I did the following:
7. right click on machine and delete virtual machine
8. created new virtual machine and point to existing VDI (cloned VDI file in my case).
9. start virtual machine and it is working.

I was doing from step 1 to step 6 in any version of VirtualBox I can imagine. So this looks like a bug in VirtualBox 3.1.0.
Can someone else please test this out and if confirmed bug can be reported to public bugtracker.
Regards

[abcuser]

Hi,
The above problem is not a bug, I just forgot one step to finish. I am such an idiot!

Let me explain (read carefully step 5 and 6 in above post - something is missing):
a) I removed existing VDI from Virtual Media Manager, so of course this action detached VDI from virtual machine!
b) I added VDI to Virtual Media Manager and started virtual machine without any VDI attached to it! Sure it fails and error tells what is wrong: no boot media.
c) So one more step is required. Click on virtual machine and then Settings button and on Storage tab add new defined VDI file to IDE controller. So to tell VirtualBox product the relationship between VDI files defined in Virtual Media Manager and virtual machine.

Why new virtual machine was working:
Adding new virtual machine and attaching!!! existing VDI file attached relationship between virtual machine and VDI file. The action I was totally overlooked when doing above steps.

You know just a classical mistake when new version is out and a problem appears, it is in our nature that we think it is a new program version problem (aka bug), but product can't replace an idiot at other site of the computer.

This appeared because of two think:
a) Storage tab is new tab in VirtualBox and I was little bit confused.
b) I have never got this error before, because I have never did such a stupidity to forget to add VDI to virtual machine.
Regards

[Sasquatch]

Before anyone will call you an idiot (except you, you already did that ), I'll lock this .