Microsoft’s Hyper-V puts VMWare and Linux on notice

After his last foray into the “Linux guy reviews a Microsoft product” space, Jason Perlow is back — this time to take a look at Microsoft’s Hyper-V, the hypervisor-based virtualization solution built into the newly released Windows Server 2008.

Although Hyper-V is still in beta and isn’t slated to ship in final form until the latter half of this year — and will be missing a few previously-promised features by the time it does arrive — it just might be the “killer app” for Windows Server, and one which will have Microsoft’s competitors scrambling to keep up, Perlow claims.


Here he is, in his asbestos-lined underwear, awaiting the inevitable flames . Take it away, Jason:

I confess to being a virtualization junkie. I’ve been using VM technology on the x86 platform since 1999, when VMWare Workstation first came on the market with their first Linux release. Since then, I’ve worked with a number of virtualization products on the desktop and on the server, as well as in enterprise environments, particularly with VMWare’s ESX Server product, the current market leader in hypervisor-based paravirtualization solutions, as well as with Xen, the Open Source project that comprises the virtualization core of a number of Linux and Unix-based virtualization products and OSes, such as Citrix XenServer, Oracle VM, Sun xVM, Red Hat Enterprise Linux 5, and SuSE Linux Enterprise Server 10. Now I can add Microsoft’s Hyper-V (the beta version in the final Windows 2008 Server bits) to my list.

Hyper-V, formerly known as “Viridian”, greatly differs from the virtualization product from Microsoft currently marketed as Microsoft Virtual Server in that it uses a hypervisor to provide hardware abstraction services to the OS environment and do resource allocation and partitioning. This differs from products such as Microsoft Virtual Server, VMWare Server and VMWare Workstation, Parallels, Linux KVM, and the recently Sun-acquired Virtualbox from Innotek use a technique known as host-based virtualization in which a host operating system such as Windows or Linux runs a subprocess provided by its native kernel called a Virtual Machine Monitor (VMM) to provide virtualization services such as a virtual CPU, memory and devices to a virtual machine. A hypervisor, on the other hand, is a thin abstraction layer which boots on the native hardware that performs some of the functions of an OS kernel, but abstracts much of what is needed to run multiple operating systems with their applications on top of it.

The advantages of hypervisor-based virtualization is that it tends to be faster and more enterprise scalable. The disadvantages are that hypervisors tend to be heavily hardware dependent and usually require hardware acceleration, such as Intel’s “VT” or AMD’s “Pacifica” extensions present in the latest Xeon and Opteron chips, such as it is with Hyper-V and Xen-based solutions, and require modified OS kernels and special paravirtualized device drivers to be run in the VM environment to facilitate enhanced I/O and networking performance.

VMWare’s ESX differs from Hyper-V and Xen in that it currently uses pure software based virtualization, so it doesn’t need the VT or Pacifica extensions. However, it has a much tighter environment as to what kind of hardware it can run on – the hypervisor has a limited device driver compatibility list and VMWare keeps its ESX hypervisor source code very close to the vest, so development goes at a much slower pace – SATA disk drives, which are now commonplace on commodity x86 server machines, are not currently supported in VMWare ESX 3. ESX Server also requires a special networked clustered file system known as VMFS to store the virtual machine images, and you have to dedicate a SAN-based LUN to it. Hyper-V, on the other hand, will run on any modern system that can run 64-bit Windows 2008, stores all its virtual machines on regular directories in NTFS, and provides third-party and built-in driver support by using what is referred to a “Parent” OS as a pass-thru mechanism. In Xen parlance, this is also referred to as “Domain 0”, where device and file system support is provided by the Linux kernel (or in the case of Sun xVM, Solaris) and Linux file systems such as ext3 and ReiserFS.

So let’s get down to the nitty gritty – installation, ease of use, and performance.

It should come as no surprise that Hyper-V’s architecture looks remarkably similar to Xen’s, as Microsoft and XenSource – now a part of Citrix Systems – embarked on a technology sharing partnership in 2006.

The only thing you need to do to use Hyper-V is do a default install of Windows Server 2008, which took about 20 minutes on my Opteron dual-core machine, then go to the Windows 2008 Server Manager and choose “Add New Role” and select “Hyper-V” server. After a few minutes of self configuration and a reboot, Hyper-V boots Server 2008 and you can now start provisioning new Virtual Machines using the Hyper-V Microsoft Management Console (MMC) snap-in tool.

After installing the virtual machine, which can be done via CD-ROM/DVD media or mounting an ISO file, you install the Integration Components (similar to VMWare’s tools) to provide enhanced networking and paravirtualized hardware support. For Windows guest OSes — with the exception of Vista, which will not work with the Integration Tools yet but will run slower in full virtualization mode– this is accomplished with a simple wizard and a reboot of the virtual machine.

source: blogs.zdnet.com

Submit Article :- BlinkList + Blogmarks + Digg + Del.icio.us + Ekstreme Socializer + Feedmarker + Furl + Google Bookmarks + ma.gnolia + Netvouz + RawSugar + Reddit + Scuttle + Shadows + Simpy + Spurl + Technorati + Unalog + Wink

Related Posts by Categories

Widget by Hoctro