stop: 0x0000007B virtualbox cloning/upgrade issue

[SilverWave]

After cloning a existing VM XP disk...
VBoxManage clonevdi /home/sw/.VirtualBox/VDI/XP.vdi /home2/VirtualBox/VDI/GBXP1.vdi
...I created another VM and called it GBXP1, kept the options the same... but on boot up received EM stop: 0x0000007B

I found that the problem was with the "ID controller type" being set to PIIX4.

I set it to PIIX3 and all is well.

Settings > General > Advanced > ID controller type

Is PIIX4 the new default in 2.02?

Posting this to save others the pain I have suffered tracking this down

[Sasquatch]

Thanks for the post, but it's already mentioned in the Forum FAQ .

[benab]

Thanks for this tip SilverWave. I was going crazy until I saw your post. It fixed my problem as well.

I upgraded from 2.0.2 to 2.0.6 and encountered this problem.

The forum FAQ seem to only address upgrading from 1.5 to 1.6. I wonder if it should be updated.

Thanks again,
-Ben

[Sasquatch]

Thanks for this tip SilverWave. I was going crazy until I saw your post. It fixed my problem as well.

I upgraded from 2.0.2 to 2.0.6 and encountered this problem.

The forum FAQ seem to only address upgrading from 1.5 to 1.6. I wonder if it should be updated.

Thanks again,
-Ben

Not exactly. The issue is only if you have a VM from before 1.6.0. Since 1.6.0, there is the PIIX4 option and set as default. Before that, it was only PIIX3 that was available.

[felixion]

Thank you so much for the tip!
Fixed it for me

[mwildam]

Switching to PIIX3 did not solve the problem for me (and I have only single core processors).