VirtualBox 2.1.2 don´t run virtual machine and other problems opening .vhd disc

[Andrew]

I still have problems when I import .vhd machines created from Virtual PC. This Virtual machine had a Windows XP SP3 Operative System, when i try to open it with VirtualBox it crash even when I close or shutdown the machine before in Virtual Pc. The host machine is also a Windows XP SP3 machine.

[Andrew]

VirtualBox Log after .vhd machine crash

[Andrew]

In this version at least the Virtual MAchine inside the .vhd file is not damaged when I open it with VirtualBox and I can open it in Virtual PC, in previous VirtualBox version 2.1.0 the virtual machines were permanently damaged when I opened them and couldn´t be used again in Virtual PC.

[Frank Mehnert]

You mentioned that you closed the machine or shut the machine down in Virtual PC. Note that .vhd images contain only the disk information, therefore you should really cleanly shut down the .vhd image before you use it in VirtualBox. Though maybe I misunderstood you.

What does crash mean: Do you see a blue screen of the guest, did the VirtualBox application terminate abnormally or something else? And does the latest release 2.1.4 improve anything?

[Andrew]

I mean that I Shutdown the Virtual Machine in Virtual PC before opening the corresponding .vhd image in Virtual BOX. After that when i run this Virtual Machine I get a Blue Screen of Dead in the guest machine, sometimes it just restart.

I haven´t used the 2.1.4 version yet, I´ll try and report then. Thank you for reply.

[Andrew]

I forgot to mention that recently I only get a Window error from Virtual Box with the Log that I attached to this report before. No more BSD even when I try to run using Safe Mode in the guest machine.

[Sander van Leeuwen]

You can't just move a Windows VM from Virtual PC to VirtualBox. See ​http://www.215389.xyz/wiki/Migrate_Windows .

Windows doesn't like such things if you don't take appropriate measures.

[Andrew]

Thanks for the info sandervl73, I adjust some settings and now I know the reason to get sometimes a BSD or just a Virtual Box crash window (Guru Meditation Window).

When I don´t set a ACPI I always get the Virtual Box crash Window, when I set ACPI ON I get the BSD on the guest machine with a Normal Windows Start (but I don´t get a Guru Meditation Window from Virtual Box) if I set ACPI ON and try to run in SAfe Mode I get just a VM restart.

Now I´m making a Restore installation process from the installation Disc, I hope this work and report the results. Thank you.

[Andrew]

The Repair installation process from Windows installation Disc works, after that I could restore my Virtual Machine in Virtual Box, but now I can´t access it from Virtual PC (I think I have to repair the installation again from Virtual PC, and follow the same process for each one, each time I have to restore a .vhd image in Virtual PC or Virtual Box).

I´ll like that in a near future the compatibility could be transparent for end users and just with a click restore a saved session between Virtual PC and Virtual BOX, maybe some Hardware emulation in Virtual Box to simulate a Virtual PC (Virtual Hardware) environment, that could be possible?.

For now, It could be good to have some extra information or dialogs when a users imports a .vhd image, alerting about possible problems and the workaround. The Guru Window don´t give any help after a crash opening a .vhd image and this is a well know behavior. The information is in the virtualbox homepage but should be accessible from Virtual Box application.

Thank again for all your help.

[Klaus Espenlaub]

I see no reason why we should annoy every user with some alert message when importing a VHD file. It's the same behavior as you'd get on real PCs if you move the hard disk from one to the other.