We have a customer with VDA 2311 on Azure NC16as_T...
# citrix-workspaceapp
m
We have a customer with VDA 2311 on Azure NC16as_T4_v3 VMs with Windows 11 Multi User and the latest approved nvidia driver. A small part of the users complain about graphical issues, which show as blacked out parts on their screen. Can anybody give me a hint on how to tackle such an issue?
I've found the following link, could be an issue with Workspace app and nvidia GPUs in the customers PCs? https://community.citrix.com/forums/topic/252134-upgrade-to-workspace-239099-causing-graphics-artifacts-on-applications-launcher/
j
Did you modify the memory limit to the maximum in Citrix Policies? Also make sure that the endpoints have updated video drivers.
m
I have not set anything in that direction, as I was under the assumption, that this is not necessary anymore. @Carl Stalhood Writes:
Citrix Display Memory Limit setting has been deprecated. – No limit. Instead, the minimum amount of memory required is allocated to ensure the client’s display layout is fully accommodated. – Citrix Docs
Source: https://www.carlstalhood.com/euc-weekly-digest-december-23-2023/ Citrix Writes:
The Display Memory Limit setting has been deprecated. With this change, Citrix now no longer limits the display memory. Instead, the minimum amount of memory required is allocated to ensure the client’s display layout is fully accommodated.
Source: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/technical-overview/hdx.html#improve-the-image-quality-sent-to-user-devices And the DaaS Console states:
For VDA versions 2308 and prior, specify an amount in kilobytes from 128 to 4,194,303. When not specified, the setting defaults to
65536 kilobytes.
For VDA versions 2311 and later, specify any amount in kilobytes. When not specified, or when specified as 0, the setting defaults to
no maximum.
j
If you upgraded it may have grandfathered the 65k limit. I have just made it a standard practice to up that video memory. But usually that exhibits issues with misaligned mouse. Blank screens usually comes down to a local video driver, or a non-refreshing engine for the end users.
m
No upgrades, images are build and replaced by packer monthly. In my understanding, you don't have to touch that setting anymore with VDA2311+. Please correct me, if I'm wrong.
o
Correct. Memory is calculated automatically and will use what it can/should use for what it needs.
d
There is a know issue in 2402 which sounds related
Same issue is present in 2311 as well but i can only find it in the german translation
r
@Marco Hofmann a few questions: • Which Workspace App version? • What are the graphics policies set? • What is the endpoint? (Windows version / GPU etc) • Do you have a CDF trace? To come back to the Display memory limit @Jeff Riechers, this does ONLY apply if you do not have a GPU. If there is a GPU present on the VDA, the policy does not do anything. @Dennis Hirsch the H.265 444 issue will most likely show in a different way.
💯 1
m
@Rody Kossen Here are your answers: • Which Workspace App version? ◦ A mix of 2311.1 and 2403 TP (The TP fixes an issue with file copy disconnecting the session Case 82549280) • What are the graphics policies set? ◦ Visual Quality: Build to Lossless <- Your recommendation from our last meeting. ◦ Everything else is set to default • What is the endpoint? (Windows version / GPU etc) ◦ Windows 11 23H2 afaik ◦ A mix of Intel Iris Xe, a few RTX Cards and Intel HD Graphics 630 ◦ A few Laptops with discrete nvidia Graphics are not affected. • Do you have a CDF trace? ◦ No, the customers says it happens regularly, but doesn't know how to reproduce it on-demand.
r
Thanks @Marco Hofmann. I would check the GPU memory consumption on the VDA at the time of the issue. How many users are you putting on a single VM?
Also @Marco Hofmann can you ask the customer if they can use the snipping tool INSIDE the VDA to see if the problem is also there? This will capture the actual desktop image before we encode it 🙂 Which helps to determine if it's something in our encoding process
m
@Rody Kossen Thankfully we use Zabbix to monitor the GPU metrics 😄 We monitor with history: 1. GPU Free Memory 2. GPU Temperature 3. GPU Total Memory 4. GPU Used Memory 5. GPU Utilization 6. GPU Memory utilization 7. GPU Power The Graph shows GPU Memory utilization for the last 6 weeks, in never went higher than 71% peak. Before the project went live, we made stress tests with the customer and decided to never put more than 4 users on one machine, an therefore limited the Load Evaluator in Studio to max 4 sessions per VDA. I will task the customer to capture Snipping Tools Screenshots from inside and outside the desktops as soon as it occurs the next time! Very nice hint, thank you!
j
If they window, and then again fullscreen the session does it re-draw? Also are the endpoint graphics drivers up to date?
m
I also requested them to test that, thank you!
s
I'm the colleague of @Marco Hofmann and have some updates to your questions @Rody Kossen & @Jeff Riechers 1. Screenhots from inside the VDA and the client show the same artifacts. So the problem occurs on the VDA itself. 2. The artifacts vanish, when you go into window mode and then back to full screen.
m
VDA version changed to 2402 ServerOS in the meantime, if I‘m informed correctly on Windows 11 Multi User (hi from vacation 👋🏻 )
👋 1
s
VDA was still 2311 when the problem occured and the screenshots were taken.
m
🙈
r
@Marco Hofmann @Stephan Sprathoff are these issues still seen with 2402? If a screenshot taken inside the VDA show the same issue it might be a Windows or driver issue. Are the drivers up to date?
s
We are waiting for the customer to get back to us, if the issue occurs on 2402. The drivers are 538.15 (January 2024). I see there is a newer version already 551.78 (March 2024) . We will test that.
m
s
Yeah, just saw that. Will try these.
r
On-Prem there have been some issues with the T4: https://docs.nvidia.com/grid/16.0/grid-vgpu-release-notes-vmware-vsphere/index.html#bug-3973158-pixelation-on-windows-t4-vgpu-vm I think it's worthwhile to test the latest driver
m
So Actionplan would be to test VDA 2402 with driver 538.56 first.
👍 2
r
@Marco Hofmann @Stephan Sprathoff any update on the issue?
m
AFAIK the changes from the Action Plan are live, but the customer hasn’t responded, yet. @Stephan Sprathoff
✅ 1
s
The problem persist with latest azure nvidia drivers and vda 2402. The users can fix the issue temporarily by switching to window-mode and then back to fullscreen. @Rody Kossen
r
Hmm, I would recommend opening a support case with NVIDIA (probably via Microsoft) as well
m
Somehow I fear that the first question from MS would be: Does it also happen via RDP?
r
Can you share a CDF trace from the VDA when this is happening? Happy to look at it
s
Thank you for your continuous help! You probably need "All modules" traced, right?
r
Yes all is fine. Only Graphics modules is good enough as well