John Howard - Senior Program Manager in the Hyper-V team at Microsoft

Senior Program Manager, Hyper-V team, Windows Core Operating System Division.

Using Hyper-V Manager "v1" against Windows Server 2008 R2

Using Hyper-V Manager "v1" against Windows Server 2008 R2

  • Comments 2
  • Likes

I had a couple of emails overnight asking whether it is possible to use Hyper-V Manager "v1" (as in KB952627 for Windows Vista SP1, or part of RSAT in Windows Server 2008) pointing to a machine running Windows Server 2008 R2 RC or Microsoft Hyper-V Server 2008 RC.

The short answer is yes, this works. The slightly longer (and intentionally non-exhaustive answer) is:

  • Bug fixes in the "v2" UI are not in "v1" UI
  • You won't have access to new features the "v2" UI exposes
  • You may see a warning when managing a "dedicated" network

The first two points are somewhat obvious, but it's that last point I wanted to expand a little further on in this post.

If you're not familiar with a "dedicated" network (otherwise known as an External Virtual Network for which the management operating system is not allowed to share the network adapter), take a trip back to my post a couple of days ago. The "v1" UI only knows about External Virtual Networks which have a virtual NIC in the parent partition. When it sees an external switch without the parent virtual NIC, it assumes that manual intervention or scripting has taken place to alter the network in some way. Hence, it blocks you being able to change the network into an Internal or Private network.

extsw-no-pvnic-from-v1

Somewhat aside to this (but I only say it as I know I’ll get plenty of email from the diligent readership I have letting me know....), you may notice that when using the v1 UI for managing a dedicated network, the "Enable virtual LAN identification for parent partition checkbox if enabled. Further you can set the VLAN ID, click OK and won't see an error – it will appear to succeed. The operation itself is meaningless as there is no virtual NIC in the parent partition to apply the VLAN ID to - if you subsequently were to re-open Virtual Network Manager using the "v1" UI, you'd note that the change had not been applied. It simply a bug and is fixed in the "v2" UI.

Cheers,
John.

Comments
  • The problem I am experiencing seems to fit your article. Any solutions?

    My Event logs show:

    eventID 23012:

    Device 'VMBus' in [server name] cannot load because it is incompatible with virtualization stack.  Server version 13 Client version 65537 (Virtual machine 716D7C42-8F53-4C0D-839B-C88A4ED94C6F).

    eventID=2:

    The parent partition uses a different VMBus version. You need to Install a matching VMBus version in this guest installation.

    Host machine runs Small Business Server 2008 - SP2 with vmbus driver version: 6.0.6002.18005

    Client machine runs Windows Server 2008 R2 with vmbus driver version: 6.1.7600.16385

  • Hey John I  am going to need you over the next few days just til I get the hang of being site admin of such complexity.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment