virtualbox.org

Hello,

I am migrating a 64bit version of 2008 R2 from Hyper-V to Virtual Box. I am able to boot the guest OS once, but then after restarting, I receive a BSOD. The quick timing of the BSOD leads me to believe this is disk related. After the boot up error, I can choose to Launch Startup Repair from the Windows Error Recovery console. Once in the Recovery Console I can choose the Command Prompt where I issue the diskpart command.
This does show me the disk that is attached and if I select that disk using select disk 0 and the issue list volume I can see the volumes.

I think the problem is that the wrong volume is configured as the C drive?

Anyone try doing this yet or have any guidance on this issue?

TIA!

I am surprised that you got it to boot at all. have never been able to get a Hyper-V vhd to boot under VirtualBox or Windows VPC. I don't even try anymore.

This free tool does it:

http://www.starwindsoftware.com/converter

We've used it several times to convert Hyper-V images.

Yea - I found that application out there as well and it works fine for converting a VHD to a VMDK if I want to use VMWare. Converting the disk is not an issue w/ Virtual Box. I can use VHD just fine in VBox.

Like I said - I can boot the VM the first time just fine. It's after that bootup where I am unable to boot it for the second time.

Thx

It would help a lot if you can grab the BSOD. You can capture it by starting the VM and press F8 right before Windows loads. This will give you a boot menu where you can choose from several options, including safe mode, normal mode and 'disable automatic restart on system failure'. The BSOD will give you the information you need to solve it.
Have you tried safe mode too? May be a good idea to go into safe mode right after the import (before a reboot breaks it) and remove all the hardware devices and let it install them anew again.

I'm trying to do a similar thing with a Windows Server 2008 image. However, I get the BSOD shortly after the Windows splash screen starts.. it lasts a fraction of a second before rebooting.

The best I could capture was a STOP error 0X0000007B

Any thoughts?

That code means a hardware issue. Have you prepared the OS for moving to other hardware?

Figured it out. Was fairly obvious and simple to resolve in the end! Ain't that usually the way

Noticed in my settings that the virtual drive had been added on the SATA controller for some reason when I'd created the VM. I switched it over to the IDE controller and it booted quite happily.

lad29 wrote:Figured it out. Was fairly obvious and simple to resolve in the end! Ain't that usually the way

Noticed in my settings that the virtual drive had been added on the SATA controller for some reason when I'd created the VM. I switched it over to the IDE controller and it booted quite happily.

Yes! This solution working fine! But how to recode HDD from IDE to SATA may be it will work faster?