Virtualizing my own hard drive

[rickaustinson]

I am trying to create a virtual machine of my own workstation hard drive for a project. The system is running Windows Server 2003 x64 on intel processors. I started by using Macrium Reflect to capture an image of the hard drive. I then used Macrium again to convert that image into a .VHD file readable by Virtual Box, and created the virtual machine.

But when I attempt to launch said machine... it blue screens.

Now I have created virtual machines from physical ones in the past without issue using WinImage and the physical drive in an external case.(WinImage can make a .VHD files directly, where as Macrium has to write a different file and then convert). Anyway, its usually as simple as creating a .VHD file and then pointing Virtual Box at it with the right settings.

It basically just turns on and bluescreens. I configured the VM with 2GB of RAM and 1 CPU(where as the physical machine has 24GB and 8 CPUs) But I can't really see that making too much of a difference.

Does anyone have any thoughts about what I might be doing wrong here?

[BillG]

I have no idea what is happening. All I can say is that I was surprised by how well Macrium Reflect worked when I tried it. I did a Windows 7 p2v from a fairly old laptop and Windows 8.1 from a i7 desktop without a lot of hope, and they both booted up first try.

p2v is an inexact science, to say the least. There are too many unknowns - even the expensive conversion programs fail when they hit something they don't expect. Making the vm look as much like the original host (and removing as much unnecessary junk from the physical machine) as possible usually pays dividends.

[rickaustinson]

I've used other programs that worked well and have every faith in Macrium... trouble is I really can't take the time to strip down the target machine. Its my primary workstation and the reason for virtualizing it is because of all the stuff it has. I've never had issues in the past with doing this sort of conversion, but you're right - its a very inexact science. I've only tried a few times before.

Is there any reason to believe trying the whole process a second time around would work any better? Just throw out what I've got and start over? Is it hit or miss or just if it didn't work, its not going to?

[mpack]

We could all waste a lot of time on well meaning but empty speculation. Get the contents of the bluescreen if you want real answers.

[rickaustinson]

Done.

Handy thing about virtual box - VERY easy to get screenshots of BSODs.

[mpack]

7B == No boot disk.

[rickaustinson]

That doesn't make any sense - the bluescreen is a windows error, it can't be generated until windows has already started(or at least tried to start).

[jorgensen]

Wrong harddisk driver - try using IDE controller and PIIX 3 chipset in settings.
Otherwise this will fix it: http://www.richud.com/wiki/Windows_XP_S ... 00007B_FIX
Instead of using a boot CD, you can attach the vdi file to another vm, and use hive in the registry.
Alternative: http://supportishere.com/quick-methodol ... 07b-error/

[rickaustinson]

I set the driver to ICH6 and it actually booted just fine. Its got a few more problems to deal with now but that's to be expected. Now its actually booting so that works.

Thanks!