VMware Horizon Community
respodu
Enthusiast
Enthusiast

Zero Client Crashing with vGPU and two monitors

Whenever we try to connect to a vGPU enabled pool with two monitors the Zero Client (Wyse P25) crashes and reboots. If the pool is set to refresh then you will never be able to login.


I set the pool to not refresh and I'm able to login. The issue is specific to two monitors if i use only one the connection works properly on the first attempt.




06/05/2015, 09:13:08.011> LVL:0 RC:   0    IMG_FRONTEND :Calling open display in Tera2 mode.

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x5

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY3, flags 0x1

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY4, flags 0x0

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008

06/05/2015, 09:13:08.011> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: Try VMW 0 NoWDDM 0, force win32 0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: connecting to driver: NV displays available 2 NVFBC disabled 0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: profiling disabled.

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY1, flags 0x5

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device VMware SVGA 3D, name \\.\DISPLAY2, flags 0x0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString VMware SVGA 3D

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY3, flags 0x1

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device NVIDIA GRID K140Q, name \\.\DISPLAY4, flags 0x0

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> dd.DeviceString NVIDIA GRID K140Q

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDPDD Chained DD, name \\.\DISPLAYV1, flags 0x200008

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Encoder Mirror Driver, name \\.\DISPLAYV2, flags 0x200008

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> SVGADevTapCountDisplays: new device RDP Reflector Display Driver, name \\.\DISPLAYV3, flags 0x200008

06/05/2015, 09:13:08.012> LVL:0 RC:   0          EXTERN :svga_devtap ==> vmwDisplays 2, nvDisplays 2, amdDisplays 0

06/05/2015, 09:13:08.088> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:08.088> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 2560 x 1600 

06/05/2015, 09:13:08.088> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:2560 cy:1600 leftMost:0 topMost:0

06/05/2015, 09:13:08.089> LVL:0 RC:   0          EXTERN :svga_devtap ==> The default path is C:\Windows\Syswow64\NvFBC.dll

06/05/2015, 09:13:08.352> LVL:2 RC:   0        MGMT_KMP :>>> Rxed SET_KBD_LOCALE: language=0x0409 layout=0x0000

06/05/2015, 09:13:08.352> LVL:1 RC:   0        MGMT_KMP :>> Feature status with errcode 0x0000ff00 received

06/05/2015, 09:13:08.354> LVL:2 RC:   0        MGMT_KMP :>>> Rxed SET_KBD_RATE: interval=33 delay=250

06/05/2015, 09:13:08.367> LVL:1 RC:   0          SERVER :InputDevTap_GetKeyboardState @ timer: LEDs = 0xFFFFFFFF ==> 0x00

06/05/2015, 09:13:08.367> LVL:1 RC:   0          SERVER :InputDevTap_GetKeyboardState @ timer: typematic [delay 0 ==> 250] [rate 0 ==> 33]

06/05/2015, 09:13:08.865> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC reports capture is NOT possible,          trying to enable capture device

06/05/2015, 09:13:08.868> LVL:0 RC:   0          EXTERN :svga_devtap ==> NVBackend::EnableNvFBC. CreateProcess MontereyEnable error 2

06/05/2015, 09:13:08.970> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:08.970> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 2560 x 1600 

06/05/2015, 09:13:08.971> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:2560 cy:1600 leftMost:0 topMost:0

06/05/2015, 09:13:09.073> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:09.073> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1280 x 960 

06/05/2015, 09:13:09.073> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1280 cy:960 leftMost:0 topMost:0

06/05/2015, 09:13:10.339> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:10.339> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1280 x 800 

06/05/2015, 09:13:10.339> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1280 cy:800 leftMost:0 topMost:0

06/05/2015, 09:13:10.599> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:10.645> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 1280 x 960 

06/05/2015, 09:13:10.649> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:1280 cy:960 leftMost:0 topMost:0

06/05/2015, 09:13:10.721> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32WindowProc Handling WM_DISPLAYCHANGE on thread 0x6d4

06/05/2015, 09:13:10.721> LVL:0 RC:   0          EXTERN :input_devtap ==> WindowMonitorEnumProc - enumerated monitor: (0, 0) 2560 x 1600 

06/05/2015, 09:13:10.721> LVL:0 RC:   0          EXTERN :input_devtap ==> InputDevTapWin32UpdateDisplays cx:2560 cy:1600 leftMost:0 topMost:0

06/05/2015, 09:13:11.339> LVL:0 RC:   0          EXTERN :svga_devtap ==> NVBackend::EnableNvFBC. CreateProcess succeeded

06/05/2015, 09:13:11.556> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC - Fixed capture by enabling NvFBC

06/05/2015, 09:13:11.556> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: using NvFBC version 0

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: can't find monitor for display \\.\DISPLAY3

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: NvFBC can't get adapter ID from name \\.\DISPLAY3

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: UpdateDisplayWatcher ERROR

06/05/2015, 09:13:11.562> LVL:0 RC:   0          EXTERN :svga_devtap ==> svgadevtap: usermode backend init failed

06/05/2015, 09:13:11.562> LVL:0 RC:-500    IMG_FRONTEND :cSW_HOST_FRONTEND::open_display - Error attaching to SVGADevTap, error 1: Failed

06/05/2015, 09:13:11.562> LVL:0 RC:-500        MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. 10 retries remaining. Trying again...

Reply
0 Kudos
7 Replies
Yorick1
Contributor
Contributor

Hi Respodu,

we got the same issue on our environment. We have the effect ,when we trying log on from a zeroclient with dual-Display to a vGPU-enabled Pool, the Zero Client crashes. The Loggon-Process to the VM goes on in the Background and so we are able to log on  after couple of time.

Have you found a solution for your Problem?

ZeroClient t310 Firmware 4.7.1 or 4.8.0

Nvidia k1 grid_K120Q

Esxi 6.0.0

View 6.1.1

Reply
0 Kudos
respodu
Enthusiast
Enthusiast

I've been unable to solve this issue.

Reply
0 Kudos
klibo87
Contributor
Contributor

We have the same Issue in our environment!

vGPU, K1, Horizon View 6.1.1 and vSphere 6.0. Teradici FW 4.8

Reply
0 Kudos
respodu
Enthusiast
Enthusiast

I've opened a support case with VMware.

Let see what they come up with but by judging from my previous few tickets I've opened on vSphere/View/vRops.... its a bug...

Reply
0 Kudos
Linjo
Leadership
Leadership

I remember a similar case I had, the solution was to upgrade the firmware on the GPU. Tried that?

(You probably have to open a case with the vendor (HP, DELL, IBM) to get the latest firmware.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
respodu
Enthusiast
Enthusiast

it was a problem with the zero client if you change the default display topology it causes the issue.

Reply
0 Kudos
Rain3359
Contributor
Contributor

Hi respodu

Is the problem solved? I met the same problem!

Reply
0 Kudos