Hyper-V Program Manager
So once you have the Hyper-V Beta installed and up and running you will probably want to start making virtual machines and playing with them. Of all the possible guest operating systems - Windows Server 2008 is the 'premier' one, in both performance and ease of installation.
To install Windows Server 2008 on the Hyper-V Beta you will need to:
Does the 2008 installation disk have the drivers for the SCSI controller emulated by virtual server? Installing 2003 in a virtual machine on an emulated SCSI seemed to take forever because it didn't have the driver. Be great if the 2008 setup detected it was in a VM and automatically installed the VM additions.
:) Guess I'm guilty of not reading all the way to end. Great news regarding the integrated virtual machine additions!!!
"Attention! You should only use the same version of Windows Server 2008 in the virtual machine that you did on the physical computer. Using a different version can cause compatibility issues later on."
Doesn't that destroy 50% of the purpose of using virtual machines in the first place?
If I had to test whether the latest program I was working on would run correctly in 12 different language versions, I'd sure prefer to test it in virtual machines. Of course if the program interacts with external devices then I have to install all those language versions on real machines and reboot all the time, but otherwise it used to be really convenient to use virtual PCs.
Norman Diamond -
Not really. Note that this is only an issue if you are wanting to run pre-release operating systems. Once an operating system has RTM'd we are able to ensure that the integration components don't change. There is certainly no issue with running different languages.
"this is only an issue if you are wanting to run pre-release operating systems"
OK, that takes care of it. Thank you for that clarification.
Great article. You finally got me to try this out. But instead of installing 2008 under 2008, I tried with Win2003 Std R2 as guest under Hyper-V. :-) doesn't work.
2003 can't recognize the network adapter (legacy or not) and Hyper-V's integration services dont run unless 2003 SP2 is found. Eh, catch 22.
So, is there a way I can connect the guest 2003 R2 to recognize the network adapter so that I can windows update it? Is the Network adapter in guest OS Microsoft Generic (VMBus) or the actual (680i mobo -- so Nvidia?? ).
PS: I'm just playing around.. nothing urgent.
Finally figured out. I had to use winimage to get the sp2 installed as a vhd.
Now this rocks!
we've faced similar problems installing a guest Windows 2003 R2 version - cannot get networking to work - this makes it very hard for us to evaluate the product.