Tuesday, March 14, 2006

Virtualization Part 2

So today we declared our bias towards vz. We've been using Microsoft Virtual Server for over a year and today's notice is nothing more than standardizing on something we already do. From now on, however, vz is assumed unless the project warrants something else.

Here is why we like vz:
- Less hardware/more isolation - we use 2-4 guests per host with none of the issues around multiple apps per server

- Easier backup/recovery. For many of these instances, we can backup the disk file and we're gold.

- Faster deployment/Simplified duplication. We define an OS image or an application image and when we decide we need another copy running, we copy the disk file, sysprep and we're ready to go.

- Portability. If we need to move an instance between physical servers, it's two files and we're done.

Why we might choose not to virtualize an app:

- I/O. Apps with high i/o, disk or network, might require us to stick with hardware. We're currently running a test to understand the performance hit on each i/o type.

- Lot's of local storage needs. We just haven't tackled this one yet.


vz is on the radar screen again. We already use MS Virtual Server and run instances of XP, W2k & W2k3 for many of our production processes. We've decided to baseline the performance of our host servers as we believe that we should be able to increase memory and add guests. More on the results later.

I was reading a report on Vz from InfoTech and they mentioned a couple interesting things.

  1. The Xen open source Vz project, which just announced support for Intel VT extensions
  2. The Intel VT extension which are available on some Xeon processors
With the changes, we need to carefully consider our vz strategy. Do we want vz-over a guest OS. If so, MS-VS or VMWare GSX are great prices for us now that GSX is free!