Hi friends, I have a strange issue with some a fe...
# citrix-vad
r
Hi friends, I have a strange issue with some a few of my PVS desktops. We are currently on Proxmox as hypervisor and for some reason one or two sessions per day are stopped working. (Of 2000) The VDI gets unregistered in Citrix and the vdi itself is unresponsive. There is CPU, memory connectivity and very little network connectivity (bytes). The vdi itself is unresponsive and not pingable. Windows 11, single session. 2507. Clients: workspace on chrome OS It’s always during lunchbreak. And sometimes approximately 10 minutes after the user logged on to their session. We have ruled out storage issues. Eventwr on the VDIs shows nothing. Director sees the vdi as online but no responsiveness Doing mem dumps and see some issue with usb devices. But nothing further, not dived in this yet. We have been down the rabbit hole disabling network adapter optimizations (offloading etc.) We have this with and without netscaler. Has anyone experience this? Anyone have any other leads to follow?
d
Is the write cache disk filling up?
⤴️ 2
r
Thanks! But 17 procent in use 😞
Some extra info. It occurs when the user locks and session and comes back
d
any chance you’re running backups using proxmox backups… they can stop the machine when the backup runs
r
Hi @Devin McCubbins, thanks. No, the vdi's aren't backupped :-)
d
figured it was worth lobbing out there
i'm very interested what you find it to be.. but don’t have any more ideas at the moment
r
Ye, me too. 😉 just 2/3 of 2000 vm's. different vms, different users. Persistent eventlogs don't give any clue
d
i only run prox in my lab.. just started using it… was specifically curious about how it handled a real workload… (had the backup issue myself which is why i chimed in)
so cool to hear someone out there has a real workload on it
🙌 1
m
Is FAS in use here? I know weird things have happened in the past when users try to lock a session and then get prompted for username and password to unlock it
It sounds like it could be a combination of locking the session and timeouts, where the delivery controller thinks the user isn't logged in after unlocking and then unregisters the machine
r
Hi @Mike Streetz (O_P), no FAS for this connection. Is there any way to check if this is the case?
a
What Proxmox CPU type is configured on the VDIs?
Maybe it's a different problem but yesterday we experienced issues with servers randomly freezing when the Proxmox CPU type of the VM was set to host.
r
Hi! We have x86-64-v3 currently set.
👍 1
Which reminds me that we have upgraded it from v2.
m
You would want to check event logs and see what's happening between the screen locking and the session going unregistered, like is it a power saving time out and it's trying to go to sleep for instance. Are there power management settings on the CVAD side, like auto scale or reboot/shutdown after use?