Home > Hyper-V, Windows 2008 R2, Windows Server 2008 > Virtual PC Guy’s: Is it a Scalability Issue to run Drivers in the Hyper-V Parent Partition? (Answer: No)

Virtual PC Guy’s: Is it a Scalability Issue to run Drivers in the Hyper-V Parent Partition? (Answer: No)

Source

I am sitting in the VMworld session “TA3880 – Head-To-Head Comparison: VMware vSphere and ESX vs. Hyper-V and XenServer”.  It is interesting to listen to VMware’s perspective on this.

One point that they have raised – which I have heard before – is that VMware ESX has better scalability than Hyper-V because they run their drivers in the hypervisor, while we run our drivers in the parent partition.  VMware usually then continues to say that they tried this approach (drivers in the parent partition, or the “service console” to use VMware nomenclature) with older versions of ESX and it caused scalability issues that were resolved by moving the drivers and emulated devices into the hypervisor.

Now, I remember when VMware announced that they were moving all of their drivers and emulated devices into the hypervisor.  At this time they were proudly talking about how they were doing this and how it helped so much with scalability, and I was thinking “that’s insane – why would they do that! I would never put code that complicated into the hypervisor”.  So I decided to do some research; and I found the simple answer for this:

The ESX service console (in what they now call “ESX classic”) is a uniprocessor partition.

Compared to this the Hyper-V parent partition has access to all processors in the physical computer, and runs an operating system with great scalability (Windows Server).

So yes, a running your drivers and emulated devices in a uniprocessor partition would be a scalability bottleneck.  But running your drivers and emulated devices in a multi-processor, highly scalable parent partition does not cause a single bit of scalability issues.

Cheers,
Ben

Advertisements
  1. Skeptic-Al
    October 15, 2009 at 12:43 am

    Soooo. What you are leading the sheep to the cliff with is “Win Core drivers are Solid and Scalable”? As if the same driver issues in Native load Win2K8 R2 will not impact the Win2K8 R2 w/Hyper-V Hosts?!
    All I am saying is “Look at the Win2K8 R2 patches on Update Tuesday and show me any patching engine discrimination between Win2K8 R2 Native and Win2K8 R2 hosting Hyper-V services. This would leave you to believe that Host vulerabilities are ‘Mutually Inclusive’ of guest vm vulnerabilities.
    This bodes well?
    That “emulated devices in a multi-processor, highly scalable parent partition..” (That is highly vulnerable to security and comaptibility fixes equal to the guest vms that it is hosting) Does cause a bit of scalability issues.

    To be very clear = It is a Host registry that is hosting many guest vm registries.
    Is there a special Hyper-V ‘regedt32V.exe’ that will protect Us? 🙂

    My two pennies worth.
    Keep at Hyper-V Team, you are getting better.

  1. September 13, 2009 at 11:38 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: