It’s that time of the year again, Microsoft Management Summit 2010 is coming up.  Conferences like these are always a great opportunity for vendors to demonstrate new products and technologies.

I thought it would be interesting to go back to MMS 2009 and take a look at some of the futures Microsoft was selling in the virtualization space.

MMS 2009 Day 1 Keynote Demo

One of the big demos on stage during the day 1 keynote session was the seamless integration of public and private clouds — possible only with Microsoft System Center Virtual Machine Manager technology, according to the script.

Now, there is nothing wrong with a vendor demonstrating visionary technology in a setting like this.  But if you actively call out your competitors as being incapable of offering a particular solution, a higher level of scrutiny is certainly warranted.

The Setup

Microsoft has secretly replaced some of the regular icons in SCVMM with cloud icons.  Let’s see if anyone notices…

Whoops, the keynote presenter let the cat out of the bag:

The host with the cloud icons are part of the public cloud hosted by Maximum ASP, while the host with the regular cloud server icon are part of my private cloud.

Wow, public and private cloud — two great tastes that taste great together.  And the significance?

Vendors like VMware want you to believe that you have to revolutionize both the data center and the cloud in order to take advantage of scenarios like this. They want you to rearchitect your entire infrastructure. Our existing System Center customers have the foundation today by which to seamlessly move from the private cloud to the public cloud.

This preview of a future release of System Center Virtual Machine Manager shows you the potential of the integration of the private cloud with the public cloud. You can get started today by taking advantage of Maximum ASP’s public cloud hosting capabilities.

Okay, I get it.  Someday SCVMM will be able to talk to a Hyper-V machine at some web host and you won’t have to rearchitect anything — and you can get a taste of it today somehow by signing up with MaximumASP.

What a difference a year (didn’t) make

I recently contacted MaximumASP (i.e., a year later) to see how things are going with their public-private cloud.  This was the response:

The public-private cloud is not a product we are offering at this time. During the demo it was simply a POC that was constructed with Microsoft.

Well, we all knew it was a POC.  But why would Microsoft make such a powerful point that VMware cannot offer this capability?  Is this FUD?

The recap

A year ago, Microsoft attacked the virtualization industry leader for not offering a feature equivalent to a fake concocted demo they highlighted during their keynote.  Surprisingly, a year later, Microsoft and their hosting partner are still not offering the convoluted capability.

Frankly, this is not cloud computing — public or private.  This stunt merely highlighted the fact that you can place a hypervisor host at a remote location and manage it from the same console that you use to manage the other hosts in your datacenter.

Oh, and as for the web server VM they migrated from the “private” to “public” cloud — no details on just how the clients of that service would find it in the new location… but that’s another topic.

Tags: , ,

VMware vSphere experts know that the ESX architecture has a critical advantage over other hypervisors like Xen, KVM, and Hyper-V.  Instead of relying on general-purpose third-party device drivers, VMware ESX comes with hardened, stress-tested drivers — ready for your toughest enterprise workloads.

Windows deserves applause for reliability improvements in recent years.  Unfortunately, the most reliable Windows design will never be able to counteract the damage that can be inflicted by a misbehaving device driver.  In fact, take a look at this slide from a Mark Russinovich TechEd session where he makes the point that the majority of Windows blue screens (BSODs) are caused by third-party drivers:

Experts agree — Windows reliability is a function of driver reliability.

What about those drivers included with Windows?

You might be under the impression that these third-party drivers are for off-brand NICs purchased from the clearance bin at Fry’s.  That’s not exactly the case — plenty of drivers are included right on the Windows DVD.

Consider this recent situation detailed by Mark Wilson.  He set up a Hyper-V test machine with some Intel PRO/100 NIC cards and when he plugged in an Ethernet cable — instant BSOD!

Read the rest of this entry »

Tags: ,

I bet you never thought of Hyper-V as a tricked-out custom hypervisor — with one less layer than VMware ESX — but it is…

“Yo dawg, I heard you like Patch Tuesday, so I put Windows in your hypervisor so you can patch it while you virtualize!”

Inspired by a joke from Kendrick Coleman. With apologies to Xzibit.

Tags: , ,

Clearly, the capability introduced with VMware vSphere 4 that allows VMware ESX 4 to virtualize itself is a real crowd-pleaser.

However, one limitation that some have discovered while using this lab-testing technique is the lack of ability to use snapshots with virtual ESX systems.  In fact, after taking a snapshot of a virtual ESX VM, you will see the system boot into the recovery shell like so:

Ouch.

Can we fix it?

I asked some super-smart engineers inside VMware about the issue, and of course they know all about it and how to make it work.

The solution is to enable an undocumented advanced configuration option on the physical ESX host like so:

Read the rest of this entry »

Tags: , , , , ,

Microsoft has done remarkable things with virtualization — unbelievable, some say.

One outstanding achievement is the way the Hyper-V architects managed to completely collapse the guest operating system layer directly into the hypervisor.  Take a look at this diagram from a Microsoft Virtualization competitive brochure:

[Yes, it's that same brochure again.]

There are several key differences between Microsoft and VMware hypervisor architectures.  While the hardware and applications layers are pretty straightforward, applications don’t run directly on hardware.  As you are about to see, these two platforms take very different approaches when it comes to virtualizing workloads.

The VMware vSphere solution is to use a thin, high-performance virtualization layer that enables a single physical system to simultaneously host multiple virtual machines.  Each of these virtual machines executes isolated instances of traditional guest operating systems — Windows, Linux, Solaris, Netware, etc.

Due to apparent technological advancements in Hyper-V, it is now possible to run applications of all kinds directly on that integrated Windows OS/hypervisor layer without the need for a guest operating system at all.  This allows Microsoft to omit an entire layer from their virtualization architecture.

I’m sure you have seen various announcements about the exceptional support that Hyper-V has for Linux workloads.  Without a guest operating system layer, one must logically conclude that Linux applications are actually running on the Windows/Hyper-V hypervisor integration directly.  Spectacular!

I thought I’d test this technological breakthrough in the lab myself by running Postfix, a very popular Linux SMTP mail server, on Windows Server 2008 R2 with Hyper-V.  According to the diagram above, Postfix is classified as an application — the third layer. Read the rest of this entry »

Tags: , , , ,

« Older entries § Newer entries »