Going Hyper

Sat, Jan 31, 2009 4-minute read

I built myself a new server last weekend, as the old one (a Dell 620 that was shipped in 2001!) finally kicked the bucket.   With much help from Horsey, I pieced together a dual-core monster with 8GB of RAM and a saucy new case.  Horse suggested I look into a bare metal hypervisor OS, like ESXi, which I thought was a smashing idea.  I have been doing much of my work in VMs these days, and probably am in the same place as Kyle.  However, I was finding out that once I was in the land of VMs, I always wanted more.  There’d be some reason why I needed another VM environment, but having that many being served up by the lappy was slowing…things…down.  My laptop is running Windows Server 2008, after I got sick of Vista, a move I highly recommend.  (Incidentally, if you do move to WS2008, remove the “Windows System Resource Manager” Feature.  The wmiprvse.exe process was kiling me)

So, I tried ESXi, but my boot drive was an 80GB SATA drive, and the installation process could not find it.  Actually, it couldn’t even find the controller.  I found all kinds of tricks to try to get it to work, but no dice.  So, Horse suggested XenCenter , but before  I had a chance to look at it, I found Microsoft Hyper-V Server.  It’s MS’s answer to the bare-metal hypervisor.  No GUI, no server roles, just a bare install that serves up VMs via Hyper-V.  I have been liking Hyper-V on the workstation, so this was intriguing.

After downloading the iso and creating the image, the install was crazy easy.  It asks very few questions, reboots, and it’s done.  You get screen that looks like this:

[caption id=“attachment_121” align=“alignleft” width=“128” caption=“The bare Hyper-V Server desktop”]The bare Hyper-V Server desktop[/caption]

As you can see, there isn’t much to it.  You can set up a network connection, download updates, and set local administrators.  You can also enable/disable remote desktop.  All pretty basic stuff.  The installation guide itself is a bare Word doc, and the configuration guide isn’t much larger, which I consider good things, as bulky documents are not indicative of anything more than wordy technical writers.

I should point that I am not a hypervisor or OS guru, by any measure.  I know enough about Windows OS to get what I need done, and I use people like Horse as my external hard drive for the more rare and difficult needs.  The fact that I set up this hypervisor means that any organism with opposable thumbs could easily do so as well.

The singular issue I had setting up the OS was seeing it from other machines.  I work out of my house and VPN into home base.  This means, that, in order to put one of my boxes on the domain, I have to VPN in first.  I tried to figure out how to do this briefly for the hypervisor, but gave up as it’s not all that important that it is on the domain.  However, this caused me grief when trying to see the box from my laptop on my home network.  After much trial and error, I finally had to put the server in the lappy’s host file and the lappy in the server’s host file, as well as basically disable the fire wall on the server.  I don’t think I’d have had near the issues if the hypervisor had been on the domain.  If you are on a domain and having issues, start with HVRemote, as it seems to solve many others’ issues.

Once you can see the server from your laptop (or other boxes), you can use the Hyper-V management tool to create and start VMs.  This is where I think Hyper-V Server really sells itself.  I am already familiar with Hyper-V, so adding another server node was easy.  Here’s what it looks like:

[caption id=“attachment_123” align=“alignleft” width=“128” caption=“Hyper-V Manager with Hyper-V Server added.”]Hyper-V Manager with Hyper-V Server added.[/caption]

So, you can see the server and my laptop in the manager window.  Really nice.  Plus, since I went with Hyper-V, I was able to copy one of my Virtual Hard Drives (vhd) from a lappy VM to the server and create a new VM on the server from it.  In other words, moving VMs to the server is WAY easy.  Creating new VMs is also a snap.  The Hyper-V New Virtual Machine Wizard allows you to create a new vhd or select an existing one.  If you create a new vhd, the installation options consist of  waiting til later, using a CD/DVD, or using an .iso image file.  I did the later, and it was great.  I just keep iso files on the hypervisor, and point to them as needed.  Very nice.

I’ve been working for roughly a week now using the VMs on the hypervisor only, and it has been great.  The laptop is faster, the VMs are much faster, and I am getting more stuff done.  All in all, I think Hyper-V Server is a great solution for developers that want to server up VMs in a easy and fast manner.

Reblog this post [with Zemanta]