Blog Posts

Microsoft released Hyper-V Server as a FREE download from their website on Wednesday. Like lots of other server geeks out there, I downloaded it immediately and installed it to see what it was like. It took me about an hour and a half to complete the whole install process. I recorded the whole session as a video file and then edited it down to 5 minutes by speeding up all of the sections where it is loading files or rebooting.

I have decided to also give away for FREE my video of the Hyper-V Server install. Yes that's right. You can view my video for FREE, just like you can download Hyper-V Server or ESXi and install them for FREE.

I did the entire install remotely from my desk - our servers are in another room. In order to do the install I connected via remote desktop into a "gateway" system in the lab and then used a browser from that system to connect to the Dell Remote Access Card (DRAC) in the target server. Then using the remote console redirection and virtual media features of the DRAC I did the install from the Hyper-V Server ISO that was on our file server.

Hyper-V Server is basically Windows Server 2008 Core with only the Hyper-V role included. Did I mention that it is free? Which is a really big deal - I don't remember Microsoft ever giving away something like this before. Because it is based on Windows Server Core it does not have a GUI. It does include a text based configuration tool that enables you to set the hostname, IP, subnet, etc (This is included in the FREE video). Once a Hyper-V Server is on the network you can then use the Hyper-V Manager MMC from a Windows Server 2008 or Vista system to manage it.

Todd

The super virtualization engineering team here at Dell recently upgraded the Dell Virtualization Advisor Tool. This free on-line tool prompts you to answer about 10 questions and then gives a detailed sizing of servers and storage. Additionally it will list the available services that might be useful when implementing the proposed solution. The part that I really like is it is easy to go back and change your answers to some of the questions to see how that affects the proposed solution. For example you can change your preferred storage from fibre channel to iSCSI.

In addition to support for VMware based solutions, it will now also provide Microsoft Hyper-V and Citrix XenServer based solutions as well. So for those that are interested in what is needed for a Hyper-V solution with high-availability and "quick-migration" the advisor can help. Additionally if you want to get the specifications for a Xen Server solution with live migration and backup and recovery capabilities - the advisor has a configuration recommendation.

The other new feature of the advisor tool is the ability to specify what workloads you will be running in the VMs which makes the sizing more accurate. You are able to specify the number of test and dev, file servers, web servers, domain controller, DNS servers, and other you will be running as VMs.

Take advantage of the free advice.

Todd

I just finished up testing for a new whitepaper on Hyper-V performance and one of the initial things I had to figure out was how to measure the CPU utilization on the server. What is known as the parent partition (the initial Windows Server 2008 that is installed on the server and then used to enable the Hyper-V role) does not include the CPU utilization for its VMs in the main Processor Utilization performance counter. This was surprising to me at first, but makes sense when you consider the architecture of Hyper-V. In this architecture, the VMs do not go through the parent partition to access the processors. (Although I/O does to use the device drivers of the parent partition.)

In order to solve this problem Microsoft has created some new performance counters that are specific to the Hyper-V Hypervisor. Early on in the betas for Hyper-V it wasn't clear what these counters did, as I blogged about back in January, but it is now much clearer with some guides from Microsoft.

In order to measure the total CPU utilization on a Windows Server 2008 system running VMs under Hyper-V use the Hyper-V Hypervisor Logical Processor % Total Run Time counter in Performance Monitor (more affectionately known as perfmon). If you just look at the % CPU Utilization or the performance tab of Task Manager you will only see the CPU utilization of the parent partition and not the VMs.

Todd

I just posted a new video to delltechcenter.com on the virtualization demos page. It is a demo of how Microsoft System Center Virtual Machine Manger 2008 (SCVMM), which is currently in beta, can be used to clone a Hyper-V virtual machine. This was fun to put together because this is the first chance I've had to work with SCVMM 2008.

There were a couple of surprising things that I discovered around the cloning demo. The first was that a VM must be prepared in advance by running sysprep (at least for windows VMs) before doing the clone. With VMware Virtual Center it is possible to have the sysprep and other customization done as part of the clone. The second surprise to me was that Windows Server 2008 includes sysprep. In the Windows\system32\sysprep directory it is there waiting to be run. And when it is run there are only a couple of very simple options to pick from. I think that it is a much easier tool to use this way. With previous versions of Windows Server the sysprep tools were on the installation cd in a deploy.cab file, which meant you had to track down the cd. I like it better just included with the OS install - although I wonder if this is a potential problem.

In addition to the Hyper-V clone demo, Scott also put up a cool demo of SCVMM managing some VMware ESX Servers and VMs. So you might want to check them both out while you are there. We're going to talk about these demos in today's chat on Hyper-V Management.

Todd

The second post on the Microsoft Virtualzation Team Blog about Quick Migration and VMotion was added a few days ago. It is mostly a discussion about how VMware HA and Quick Migration both provide a failover solution for UNplanned downtime. I agree with Jeff that both do basically the same thing in the event of an unplanned server outage - the VM is moved to another server and restarted.

The difference that he doesn't talk about is that the rules of the failover are different because of the underlying filesystem that is used in each solution. Microsoft Hyper-V and Quick Migration are using the tried and true Microsoft failover-clustering, which uses an NTFS filesystem on the shared storage. As this is not a cluster file system, the shared storage is actually only visible to one of the servers at a time to prevent corruption. VMware ESX server and VMware HA are working with VMs that are on a VMFS file system which is cluster aware - meaning that multiple ESX servers are able to access the files (or VMs in other words) at the same time.

So following a failure of a Hyper-V server, all VMs on the same disk (or LUN) must be recovered on the same server because the LUN or disk can only be used by one server at a time. In the event of a failure of an ESX server, the VMs can be restarted on any ESX server that has access to the LUN. In order to achieve this flexibility with Hyper-V and Quick Migration it would be necessary to have each VM on it's own LUN. This isn't impossible, but could be more complex to setup and manage.

The end result would be same - the VMs would be restarted on another server. Some of the underlying details can make a difference with flexibility in where those VMs end up.

Todd