none
[WSV,W2K8-RTM] Hyper-V Problem: Cannot start VM 'Cannot find file', VMBus driver failure

    Question

  • ASRock SATA GLAN Board, latest revision bios 2.60 with vitualization support.

    4gb DDR RAM

    AMD Athlon X2 4600+

     

    I've performed several installations of Windows Server 2008, carefully obeying the 'Do not change locale' restriction. I'm finding however that when I attempt to start a VM I'm getting an error mentioning VMBus and 'Cannot find the file specified', along with some GUID-like numbers.

     

    There are no errors in the Hyper-V log, though perfmon is showing I have hyper-v partition support and I'm seeing the 'Hyper-V' initialized successfully events. What I am finding though is that in device manager, VMBus is unable to start with a code 12 error (insufficient system resources).

     

    This error has been found by several of my peers and collegues who've tried hyper-v on similar systems. Any idea on how t resolve it?

    Saturday, February 09, 2008 5:54 PM

Answers

All replies

  • Done some serious poking with the Process explorer to try and find what files I'm missing. Turns out the answer is 'none'.

     

    I've found that 'file' it's trying to access is only a file in a very limited sense. It's actually referring to HKCR\CLSID\{D41A1872-3740-41CE-A1EE-4522AB82F991} in the registry. This none other than the CLSID for the failing VMBus device.

     

    The question is now: How can I determine why VMBus is sad, and how can I make it happy? Smile 

    Sunday, February 10, 2008 9:06 PM
  • Since this forum is failing to provide either a potential avenue of investigation (and based, on what appears to some other questions in this vein that were asked here, that likewise went unanswered), is there a means for me to raise this issue elsewhere?

     

    I want to drive some deployments of Hyper-V based virtualization and I'm finding it hard to accept that three out of five machines just dont play nicely with it in the local environment.

    Wednesday, February 13, 2008 10:28 PM
  •  

    Steven - can you use the CPU-Z tool from http://www.cpuid.com to output the CPU information, and post a screenshot somewhere?
    Thursday, February 14, 2008 4:48 PM
  • Steven,

     

    You could also try posting to http://connect.microsoft.com/WindowsServerFeedback though the site seems more along the lines of 'Feedback' & 'Suggestions' rather than a 'Bug-Tracking' database though it could be worth a shot or not.

    Code Snippet

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\CLSID\{D41A1872-3740-41CE-A1EE-4522AB82F991}]
    @="VmbusVdev"
    "AppID"="{D695FDFD-ECBF-4A23-AB9A-4E54D83A2387}"

    [HKEY_CLASSES_ROOT\CLSID\{D41A1872-3740-41CE-A1EE-4522AB82F991}\InprocServer32]
    @="C:\\Windows\\System32\\vmbusvdev.dll"
    "ThreadingModel"="Free"

    [HKEY_CLASSES_ROOT\CLSID\{D41A1872-3740-41CE-A1EE-4522AB82F991}\ProgID]
    @="VmbusVDev"

     

     

    That is an export of the CLSID you mention from my server here. The file is in C:\Windows\System32 and has a digital signature December 9th 2007 4:00:07PM and is Build 6.0.600.17101 and a screenshot of the permissions if any of this helps.

     

    Cheers,

     

    Stephen Edgar

    Friday, February 15, 2008 8:40 PM
  •     That is odd. Are you running the RTM build in both the host and the vm? I would expect the vmbus driver in the vm to be 6001.18000 . That is what my server 2008 standard x64 has, and it is also the one I needed to install to get Integration Components running in Vista SP1 x64 as a vm.

     

    Stephen, what version of the vmbus driver do you see in your vm? Did the integration components install automatically?

     

    Saturday, February 16, 2008 12:51 AM
  • If you have a close look we are running Windows Server 2008 6.0.6001.18000 RTM Build of the Server, though we are still only running Hyper-V Beta Build 6.0.6001.17101. So at first glance the VMBus shows 6.0.6001.18000 but when you click Driver Details and have a closer look at each specific file that makes up the drivers they are all build 6.0.6001.17101.

     

    Screenshot for VMBus on Parent OS & Driver/File Version Listing from C:\Windows\system32\vmguest.iso in Child VM (All OS's are x64 RTM)

     

    Cheers,

     

    Stephen Edgar

     

    EDIT: Updated Screenshots

     

    Saturday, February 16, 2008 1:43 AM
  • We are currently investigating this problem - but have no particular guidance on how to get around this problem at this point in time.

     

    Cheers,

    Ben

    Tuesday, February 19, 2008 7:29 PM