EDITED: moved to Horizon forum
EDITED: problem summary
Problem summary:
Windows 7 x64 VDI guests default to VMware VGA display adapter instead of using the NVIDIA k120q adapter
Windows 7 x64 VDI guests fall back to the VMware SVGA adapter at LOGIN, but correctly use the NVIDIA K120Q at RECONNECT
See entry (7) Below which is the accurate problem description
VMware support case filed
NVIDIA bug case filed
We have deployed new compute using HP Gen9 hosts with NVIDIA GRID K1 cards installed
This is on vSphere 6.0U2 Horizon View 6.2.0
The GRID VIB has been installed and the drivers installed in the guest OS which is Win 7 Pro x64
We have deployed new Tera2 endpoint clients, specifically DELL WYSE 5030
We have tried using later edition View Agent; and tried reinstalled the NVIDIA drivers
We have tried modifying the DELL endpoint display topologies
This is driving me nuts and I am falling way behind on delivery of a solution
Screenshots below show what is happening, and detail what has been installed on the guest
When using Horizon Direct Access, we can successfully change the display settings and it kind of seems to work - but as soon as the guest desktop is logged off and login again, it once again reverts from the NVIDIA and back to VMware display adapter.
Any ideas for further troubleshooting would be very gratefully received.
Thank you
Now that this issue is to be passed to VMware engineering, I have decided to press ahead with our desktop migration to new compute without NVIDIA GRID, thus rendering this forum post otiose.
We will continue the support case and we may 'phase in' some Grid-enabled desktops as & when new members of staff join or there is a natural demand for the creation of new desktops, but as we cannot make it work with the existing desktops at this time, we accept defeat for our current deployment. If we ever find a solution, I'll post it here.
Thank you Sam @ VMware Support for giving this a go. Appreciate your time. An honourable mention for Rachel @ the NVidia forums who tried to be helpful.
I would like to thank the Community - but no one helped, so I won't.
I have had to bite my tongue and restrain myself from expressing my personal opinion as to how this experience reflects on the K1 GRID solution in its current incarnation.
EDIT: Currently, on the test VDI, even logging in on a PC desktop using Horizon Client, will NOT bring the machine online with the NVIDIA adapter
Have tried uninstalling NVIDIA drives, uninstalling Agent, installing Agent and then reinstalling NVIDIA drivers, in the guest O/S
This has made no difference
How do you make your Win7 guest OS _____use_____ the NVidia adapter????????????????????????????????? :smileyangry:
PCOIP log:
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 SERVER :Resolution Set does not support VMwareResolutionSet_SetLogLevel, skipping ...
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 IMG_FRONTEND :Calling open display in Tera2 mode.
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x5
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x8
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> vmwDisplays 1, nvDisplays 0, amdDisplays 0
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 1 NoWDDM 0, force win32 0
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 0 NVFBC disabled 0
2016-07-22T22:25:37.401+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: profiling disabled.
2016-07-22T22:25:37.402+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: Found driver verion 11
2016-07-22T22:25:37.402+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: active backend: WDDM
2016-07-22T22:25:37.402+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: handshake WDDM
2016-07-22T22:25:37.402+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> found: driver:0.11 build-3774095, client:0.11 build-3951922
2016-07-22T22:25:37.402+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> svgadevtap: svga driver API version:0.11 build-3774095, driver version: 1.46 ("8.15.01.0046"), build-3774095
2016-07-22T22:25:37.403+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> SVGADevTap_Attach2: inRdsSession 0 sessionId 2
2016-07-22T22:25:37.403+01:00> LVL:0 RC: 0 EXTERN :svga_devtap ==> maxAppFrameRate = 30
2016-07-22T22:25:37.660+01:00> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0xecc
2016-07-22T22:25:37.660+01:00> LVL:0 RC: 0 EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1024 x 768
2016-07-22T22:25:37.843+01:00> LVL:2 RC: 0 MGMT_KMP :>>> Rxed SET_MULTIPLE_LOCALE: num_locales=1 lang[0]=0xA9 layout[0]=0x0
2016-07-22T22:25:37.939+01:00> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1024 cy:768 leftMost:0 topMost:0
2016-07-22T22:25:37.941+01:00> LVL:0 RC: 0 EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0xecc
2016-07-22T22:25:37.943+01:00> LVL:0 RC: 0 EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1920 x 1080
2016-07-22T22:25:37.943+01:00> LVL:1 RC: 0 MGMT_KMP :>> Feature status with errcode 0x0000ff00 received
2016-07-22T22:25:37.943+01:00> LVL:2 RC: 0 MGMT_KMP :>>> Rxed SET_KBD_RATE: interval=33 delay=437
UPDATE : tried with a new Horizon Pool - makes no difference
UPDATE : tried changing the number of displays in the virtual machine hardware settings - makes no difference
:smileyangry:
From the NVIDIA docs:
Use Windows screen resolution control panel to make the second display, identified as "2" and corresponding to NVIDIA vGPU, to be the active display and select the
Show desktop only on 2 option. Click Apply to accept the configuration.
You may need to click on the
Detect button for Windows to recognize the display connected to NVIDIA vGPU.
Note
: if the VMware Horizon/View agent is installed in the VM, the NVIDIA GPU is automatically selected in preference to the SVGA device.
So the NVIDA GPU should be automatically selected - but this does not happen - why?
:smileyconfused:
HELP
UPDATE: I have checked the GRID firmware with NVidia-smi, and it is right up to date and everything looks normal on the server side.... wtf am I doing wrong???
UPDATE: tried kb2125291
To ensure Teradici enabled for NVIDIA
This has made no difference
UPDATE
Carrying forward testing using a PC with Horizon Client installed is now producing very strange, if not consistent and repeatable, results.
Connect to View Server > Login > VDI uses VMware SVGA
Log Off > Login > VDI uses VMware SVGA
But...
Connect to View Server > Login > VDI uses VMware SVGA
Disconnect > Login > VDI uses NVIDIA k120q
Disconnect > Login > VDI uses NVIDIA k120q
Log Off > Login > VDI uses VMware SVGA
So... summarily, any login pursuant to either a reboot or log off, and the VDI uses the VMware SVGA adapter; whereas any login pursuant to a disconnect uses the NVIDIA.
Conceptually, the problem seems to be linked somehow to the login process
This is truly, truly bizarre
UPDATED:
1) tried creating a new user (ergo, new user profile) in the VDI, with local administrative privileges:- makes no difference, symptoms are the same
2) confirmed that testing on the DELL thin client produces the same outcomes as testing on a PC client with Horizon View Client. It does, therefore this is an issue with the VDI guest, not the clients
3) tried disabling items in msconfig,exe, in case of any conflicts. Did not help, symptoms remain the same
4) tried running the VMware Optimization tool (bit of a long-shot). Did not help, symptoms remain the same
5) Reviewed Event logs on the VDI. Do not see anything obvious that may be contributing to the issue
6) Posted this problem on the NVIDIA GRID Community forums.
UPDATE
Have removed the AV package (Webroot) to see if it makes any difference - it does not - the symptoms remain the same
Have used PROCMON to try to understand what is different between the Login picture and the Reconnect picture, but nothing is standing out
Problem remains the same:
Login > No NVIDIA
Reconnect > NVIDIA
:smileyconfused:
UPDATE
Having scanned through the Process Tree in ProcMon, and done another review of the Event log, I am at this point entirely bereft of ideas as to how to troubleshoot and resolve this.
Does anybody have any clues? I'll settle for the smallest grain of hope at this point.
Also, does anyone know where we go for support on a case like this? Is it to NVIDIA or to VMware?
thanks
UPDATE: a support case has been raised with VMware .... but I'm still desperately urgent for troubleshooting ideas if anyone has them... thanks
UPDATE:
tried experimenting by disabling the VMware display adapter from the NVIDIA-enabled desktop
I suspected this was a bad idea but thought, "why not? - nothing to lose"
It didn't improve the situation, it only made it worse. Once the VDI had re-booted, everything defaults back to the Microsoft VGA adapter, rather than defaulting to the NVIDIA.
So yea..... it's an "obvious" solution to the problem but it doesn't work :smileyplain:
hhhhhhhhhheeeeeeeeeeeeeeeeeeellllllllllllllllllpppppppppppppppppppppppp argh :smileysilly::smileyminus::smileyangry::smileyconfused:
UPDATE:
tried a different experiment, this time by disabling the Monitor device linked to the VMware SVGA display while connected to the NVIDIA-enabled desktop
This did not help; symptoms remain the same, i.e.
Login --> SVGA
Reconnect --> NVIDIA
Just a question for the sake of clarity and to ease my mind so that I don't go insane.
What I am expecting to happen when this K1 GRID VIEW system is working properly:
Could anyone who is using a GRID K1 set up in a production environment just confirm for me that this is possible?
Without wanting to sound facetious by my tone, I just want to ensure that in buying GRID K1-enabled servers, I've not accidentally stepped in to a well-marketed, over-hyped beta program where things don't actually work (yet) have I? This would be a nightmare scenario, and I just want to make sure I haven't proverbially shot myself in the foot....... i.e. this can actually be done, right?
This is a serious, honest question - I'm not being sarcastic.
Can anyone confirm by way of actual, real experience?
Thanks
UPDATE:
tried CTX201804, which was referenced at the NVIDIA forums - this did not help - original symptoms still persist.
UPDATE:
Now submitted as BUG at NVIDIA under bug reference number #160724-000143
UPDATE: found some alternative drivers on the NVidia site listed as "GRID series"
Tried these, but they won't even install in the VDI
Clearly the driver we have is the "right" one, it just doesn't work properly.