none
RemoteFX: Guest OS Driver Issue

    Question

  • Hi All,

    I have used this forum a lot but this is my first post (I usually find the answer I need).... exciting times!

    I have just created a Hyper-V server with Server 2008 R2 and set up a virtual desktop pool. All is working well. I have now moved on to trying to get RemoteFX working to improve the end-user experience. Here is my setup:

    • Server 2008 R2 Enterprise SP1: Hyper-V server
    • Windows 7 Enterprise SP1: virtual guest OS (Hyper-V integration services installed)
    • Nvidia NVS 300 physical GPU installed in host with latest driver (DirectX 11 support and WDDM 1.1 driver installed)
    • Physical host server is using 2 Intel Xeon E5506 quad core CPUs (SLAT enabled)


    I feel confident that I have met all of the prerequisites for RemoteFX. I'm aware that I am not using one of Nvidia or AMD's offically listed GPUs for RemoteFX but the spec of my card still meets the requirements needed for RemoteFX.

    RemoteFX is installed onto the host server and I have added the 'RemoteFX 3D Video Adapter' to the virtual machine. The virtual machine boots up fine and I can log in...... but this is where it gets interesting...........

    At this point I am led to believe that the guest OS should start installing the driver for RemoteFX... but it doesn't. It does nothing. In 'Device Manager' I have TWO 'unknown devices' and my GPU is listed as 'Standard VGA Adapter'. If I remove the 'RemoteFX 3D Video Adapter' from the virtual machine and reboot, the two 'unknown devices' disappear and the GPU changes to 'Microsoft Virtual Machine Bus Video Device'...... so these unknown devices are clearly associated with RemoteFX.

    So my question: why is the guest OS not installing the correct RemoteFX driver? I have been on this for hours so I am going to be so grateful to anybody who can help.

    Thanks
    Nick




    Monday, May 20, 2013 10:36 PM

Answers

  • I managed to get it working.

    I created another virtual machine using 64bit Windows 7 and it picked the RemoteFX driver up straight away. I wonder if, for certain drivers, if the host machine is 64bit, then the guest VM has to be 64bit also.....? I wouldn't have thought this should be the case but it worked for me!

    • Marked as answer by nick3young Wednesday, May 22, 2013 10:32 AM
    Wednesday, May 22, 2013 10:32 AM

All replies

  • Hi,

    Since you mentioned guest VM device manager displays unknown device, so RemoteFx device is detect in guest VM, just the driver issue.

    You may try to upgrade integration service and then restart Hyper-V guest VM and check the result.

    For more information please refer to following MS articles:

    RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012
    http://social.technet.microsoft.com/wiki/contents/articles/16652.remotefx-vgpu-setup-and-configuration-guide-for-windows-server-2012.aspx#Requirements_for_RemoteFX_vGPU


    Lawrence

    TechNet Community Support

    Tuesday, May 21, 2013 6:59 AM
    Moderator
  • Thanks for the response Lawrence.

    Yes, you're quite correct - the guest os is detecting the remotefx device so it must be a driver issue. Also, the GPU is a new addition to the server which I purchased for this purpose. Before I installed this new card, the virtual machines wouldn't even start with an 'incompatible GPU' error in the event log. I no longer get this with the NVS 300.

    However, I believe I am on the latest version of the integrations services on both the host and the VM. I am using version 6.1.7601.17514.... is this the correct version for Server 2008 R2 SP1? From what I gather, the only way to officially change the version of the integration services is to use a different server OS completely (e.g. Server 2012.... which isn't happening!).

    The article in your post is brilliant, but it hasn't solved my problem unfortunately. Any more ideas?

    Thanks again.

    Tuesday, May 21, 2013 11:15 AM
  • I managed to get it working.

    I created another virtual machine using 64bit Windows 7 and it picked the RemoteFX driver up straight away. I wonder if, for certain drivers, if the host machine is 64bit, then the guest VM has to be 64bit also.....? I wouldn't have thought this should be the case but it worked for me!

    • Marked as answer by nick3young Wednesday, May 22, 2013 10:32 AM
    Wednesday, May 22, 2013 10:32 AM