I still get an error while installing the Integration Components on Win2k3 after I installed Win2k8 RC1 on the host! HC?


In an earlier post, I said that you should install Windows Server 2008 RC1 with Hyper-V Beta if you’re getting error 61658 while trying to install the Integration Components in Windows Server 2003.

And you should.

But some people are still seeing it.  If you happen to be one of them, here’s why:

You probably didn’t really install Windows Server 2008 RC1 with Hyper-V Beta; you probably installed Windows Server 2008 RC1, which contained the Hyper-V CTP.

I won’t go into the reason behind having two similarly named releases so close together because I wasn’t involved in that discussion, so any attempt to explain it would be pure speculation on my part.  Needless to say, the situation we find ourselves in is that there is a Windows Server 2008 that has our beta bits in it, and one that has our old CTP bits.

If you’ve yet to install any build of RC1, you can get a link to download the one that has Hyper-V Beta here.

If you’ve already installed it and you’re curious as to whether or not you’ve got the CTP or the Beta bits of Hyper-V, you can easily tell.  If you had to double-click on any MSU files to get the role to show up in Server Manager, you have the CTP release.


After Blogging Mint:

I don’t know if anyone else out there ever saw these videos, but when I was in High School, my physics class had to watch some lectures given by a man named Paul G. Hewitt.  While describing miscellaneous laws of physics, he would commonly prove the law via some demonstration, then ask his class "HC?" which stood for "How come?"
My "Here’s why" series of posts wasn’t exactly inspired by Professor Hewitt, but I’ve yet to write a post without thinking about those videos in some way, so I consider them to be a sort of tip of the hat.
Comments (2)

  1. Gabrie says:

    Hi

    When installing, Hyper-V checks for the VT extension on the cpu. Can this check be disabled? I want to test Hyper-V within a VM but just because of this check it doesn’t work, the VM doesn’t report the VT extension to the Guest OS.

    When Im correct, VT is an extension to fix a “bug” in Intel architecture. Most hypervisors now a day support the VT extension and handle this inside the hypervisor. Therefore they don’t have to report the extension to the VM. Unfortunately if a VM checks for this, it won’t find it, although the VM would run perfectly without because the hypervisor handles it.

    So, can the check be disabled? Would be great for testlabs in which you want to build small farms of Hyper-V servers.

    Gabrie

    [Not quite.  VT is an extension to the Intel processor’s instruction set.  Think of it as MMX for Virtualization.  (AMD has a similar instruction set extension called AMD-V or ‘Pacifica’ which we also use where applicable.)  The Microsoft Hypervisor relies on those instructions to do a lot of work for us, and simply won’t function without them, so no – the check cannot be disabled.

    You also cannot run Hyper-V inside a virtual machine.  It’s not meant to be a nested solution.  –  mikekol]

  2. Peter Menadue says:

    Hi there, great blog.

    Any way to remove the Virtual Server/PC Tools from a VHD if you ony have Server 2008 + Hyper-V?

    Scenario: Existing VHD, from say, Microsoft Technical Demo Kit, and just a Server 2008 with Hyper-V?

    Or do I have to find a Virtual Server somewhere, remove the old integration tools and then remount on Hyper-V?

    cheers,

    Peter

    [Hi Peter – if you have the newest version of the additions installed (sorry – I’m blanking on the version number right now), it may be possible to boot the VM and remove the additions in a Hyper-V VM.  Just make sure you have a backup of the VHD just in case.   – mikekol]