VHD native boot server 2008 on windows workstation.

[boxtop]

I can't get it to work.  I created a 200 GB fixed size vhd file on my windows 7 desktop.  I used the windows AIK and Imagex to install the server 2008 image to the vhd.  I used bsdedit to set the boot options.   When I rebooted the workstation I got the boot menu and selected server 2008.  It boots then blue screened.   I thought, controller drivers for sure.  I reboot and go into repair and install the RAID drivers for my MBoard.  Now I can see the drive but it says the operating system files arent present.   There are dozens of writeups online on this process and it seems strait forward enough but I tried to do it three times with the same result all three times.

Anyone else ever try to use VHD native boot?

[scythe944]

Hmm... I would have certainly pointed my finger at controller drivers as well.

The only time that I've used a virtual machine was testing the XP mode under Windows 7 (as described here: http://www.microsoft.com/windows/virtual-pc/download.aspx)

Of course, you know that I don't have the type of hardware needed to try these things out for myself, so I can only offer some mis-guided / unexperienced tips that come to mind.

You said that you installed it first, then did a repair to add the RAID drivers.  Based on my experience, even though you'd be able to see the drive, the whole installation could be corrupt and need a re-install.  I guess I just base that off of changing the ATAPI settings of SATA drives in the BIOS.  If you have it set at AHCI when you install, then go and change it afterwards, you'll lose access to that drive.  So, I'd say get the drivers loaded before loading the system, and try it again.

If that doesn't work, I'll look around for some more tips, but then again, you can do that too.   

[boxtop]

Once I installed the controller drivers I could see the drive but the drive showed as empty even though I had applied an image to it.

These are the instructions I followed:

http://blogs.msdn.com/b/cmayo/archive/2010/03/05/adding-a-native-boot-vhd-to-windows-7-part-1.aspx

http://blogs.msdn.com/b/cmayo/archive/2010/03/05/adding-a-native-boot-vhd-to-windows-7-part-2.aspx

http://blogs.msdn.com/b/cmayo/archive/2010/03/05/adding-a-native-boot-vhd-to-windows-7-part-3.aspx

I guess I could create the vhd and then try and install to in normally but I dont know if a windows install disk would see the VHD as an available drive.  Plus would that Eff up my bootloader and make windows 7 unbootable.

I may need to try that.  It also just hit me that I never checked my bios to see if virtualization was turned on for my processor.  I just got an error in VMware player that would not let me install hyper-v on a virtual because the processor doesnt support it.  Maybe thats the problem.  I will check and report back.

[scythe944]

I just got an error in VMware player that would not let me install hyper-v on a virtual because the processor doesnt support it

Well, that would certainly explain things...

I thought newer mobo's would have this enabled by default, but in retrospect, I doubt it.  Most users won't touch the virtual abilities of their processors and I assume that it could cause performance/compatibility problems for those not utilizing the technologies employed by virtualization, so it's definitely worth a shot at looking at.

Anyway, after you get it running (which I fully believe that you will), let me know how you like the hyper-v vs. the vmware stuff.  I know that you'll be a little biased against it, now that you're a veteran of VMWare, but I'd like to hear your opinion on how it stacks up.

[boxtop]

I just got an error in VMware player that would not let me install hyper-v on a virtual because the processor doesnt support it

Well, that would certainly explain things...

I thought newer mobo's would have this enabled by default, but in retrospect, I doubt it.  Most users won't touch the virtual abilities of their processors and I assume that it could cause performance/compatibility problems for those not utilizing the technologies employed by virtualization, so it's definitely worth a shot at looking at.

Anyway, after you get it running (which I fully believe that you will), let me know how you like the hyper-v vs. the vmware stuff.  I know that you'll be a little biased against it, now that you're a veteran of VMWare, but I'd like to hear your opinion on how it stacks up.

[scythe944]

Maybe I can just boot to the media and install to the drive in a traditional install.

That's my thought exactly.  From within the virtual machine, you should be able to mount an ISO or possibly a VHD in the CD-ROM drive.

Then again, since I have no idea what I'm talking about, it's better off that you just share your experience with us. 

[boxtop]

Maybe I can just boot to the media and install to the drive in a traditional install.

That's my thought exactly.  From within the virtual machine, you should be able to mount an ISO or possibly a VHD in the CD-ROM drive.

Then again, since I have no idea what I'm talking about, it's better off that you just share your experience with us. 

See thats whats is tricky.   It isn't really a virtual machine.  Only the hard drive is virtual.  So essentially its like booting my computer, with all its hardware to a partition that exists on a virtual drive which is just a file residing on the file system of the primary OS.   The new install would directly access, RAM, CPU and other resources instead of accessing them through a hypervisor.  Does that make sense? 

Anyway if I figure out how to do it I will post the steps.

[scythe944]

Yeah, it makes sense to me.  It's the same thing as the Windows XP mode for Windows 7.

That's why I thought installing the drivers for the RAID controller before installing the OS would help.