Morosoft Hyper V in W2008 Server R2

[jimbo45]

Hi guys (and gals)

Anybody using W2008 Server R2 and Microsofts Hyper-V virtualisation - for a SMALL home / office network.

I'm currently using VMWARE server -- no problem with it but am curious to see how the Microsoft product compares - and performs against vmware server running on the same OS.

Anybody tried yet. Can you also control the VM from the local machine or do you need to have another machine to do it (like vmware esxi). vmware server can be controlled locally (or remotely) or both.

Cheers
jimbo

 

[H2SO4]

Anybody tried yet. Can you also control the VM from the local machine or do you need to have another machine to do it (like vmware esxi). vmware server can be controlled locally (or remotely) or both.

Microsoft's Hyper-V is a hypervisor-based solution like ESXi. The way they operate is fundamentally different to VMware Server and MS Virtual Server.

As you're probably aware, the hypervisor-based offerings require hardware assistance ("ring -1"), but they are capable of far better performance than the "server" products which are really just software emulators.

Because they're literally two (or more) separate OS installations concurrently running on the same machine, "control" comes down to accessing one computer from another the way you'd normally do it - through RDP for example.

Unlike ESXi, Hyper-V architecture includes provision for very low-level communication between kernel-mode code in parent and child partitions called "enlightenment". In a nutshell, select kernel-mode code has a direct line to its counterpart in the parent partition. VMware instead relies on a comparatively "fat" hypervisor which assumes some of the roles of the Hyper-V parent partition.

If you have specific questions, just ask

 

[Zealus]

Microsoft's Hyper-V is a hypervisor-based solution like ESXi. The way they operate is fundamentally different to VMware Server and MS Virtual Server.

As you're probably aware, the hypervisor-based offerings require hardware assistance ("ring -1"), but they are capable of far better performance than the "server" products which are really just software emulators.

Because they're literally two (or more) separate OS installations concurrently running on the same machine, "control" comes down to accessing one computer from another the way you'd normally do it - through RDP for example.

Unlike ESXi, Hyper-V architecture includes provision for very low-level communication between kernel-mode code in parent and child partitions called "enlightenment". In a nutshell, select kernel-mode code has a direct line to its counterpart in the parent partition. VMware instead relies on a comparatively "fat" hypervisor which assumes some of the roles of the Hyper-V parent partition.

If you have specific questions, just ask

Okay, I do have specific questions. I have a server (i.e. hardware) that supports virtualization. What is the proper sequence to install two Windows 2008 Server R2 (i.e. software) instances on this hardware? How do I manage each one if I attach monitor, keyboard and mouse to the hardware server or, in other words, which instance I will see when I turn monitor on? How do I switch between them? How do I install a third instance if need be?

Thanks!

 

[Jordus]

If you install Server 2008 R2 you will see the regular GUI for Server and you install Hyper-V as a role. This also installs the Hyper-V Manager console which you use to create and manage virtual machines.

If you install Hyper-V Server (the standalone hypervisor) you will get nothing but a command-line when you log in, and you will need another machine to install Hyper-V manager on (Vista, 7 or Server 08) to manage the VMs.

EDIT: Also make sure that your hardware actually meets all THREE requirements to run Hyper-V.

64-bit processor
Hardware Assisted Virtualization supported (Intel-VT or AMD-V)
Hardware based Data Execution Prevention (DEP)

If you are unsure, you can download a program called Securable that will tell you if your hardware qualifies.

http://www.grc.com/securable.htm

 

[Zealus]

Jordus,
thanks. I am actually planning to deploy this setup on one of the low-end Dell servers (that I yet have to purchase based on the exact criteria that you've mentioned) so there's nothing to run this on yet.

However. if you could elaborate on tools installation and where those tools would connect - I'd appreciate it.

 

[Jordus]

You will actually find the installation quite easy.

You need to ensure that Hardware Assisted Virtualization and Data Execution Prevention are turned on in the BIOS.

Then, install either Hyper-V server or Server 2008 (or R2) onto the server. The setup is very very similar to Vista/Win7 so you wont have an issue there, just boot from the DVD and go.

If using Server 2008 full install, you simply open the Server Manager and choose "Roles" and install the Hyper-V role. It will install the Hyper-V manager tool for you and then when you open it, you just click "OK" to connect to the local host and you are good to go.

If you are using Hyper-V server standalone, you will need to install the Hyper-V Manager tool on a Vista, 7 or server 2008 machine to manage the virtual machines on the server.

If you do this in a workgroup environment it can get slightly tricky but here is a tool to help you make it work: Hyper-V Remote Management Configuration Utility - Home

Here is the download to install hyper-v manager on a seperate machine: Description of the Windows Vista Management Tools update for the release version of Hyper-V

 

[Zealus]

Thanks a lot!

 

[pparks1]

Thanks for posting the links to manage HyperV when in a workgroup. I screwed around for over 1 day at work trying to make this stupid thing work..since server was in a DMZ off the network and I was on a domain. I ultimately got it working before, but it seemed unnecessarily complicated.

In our business we use VMWare ESXi instead. Seems to be much more simple and better suited for our business needs.