Here my VM config :
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 8
efidisk0: datastore1:vm-116-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: none,media=cdrom
machine: pc-q35-8.1
memory: 32768
meta: creation-qemu=7.1.0,ctime=1673962676
name: XXXXXXXXXXXX
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr1
numa: 1
ostype: win11
scsi0: datastore1:vm-116-disk-1,cache=writeback,discard=on,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=4c3d90cd-9a00-449b-be71-37bd8327c2e6
sockets: 2
tablet: 0
tpmstate0: datastore1:vm-116-disk-2,size=4M,version=v2.0
vmgenid: a9f85d0e-d80d-40ef-b891-71d37cb57f00
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 8
efidisk0: datastore1:vm-116-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide2: none,media=cdrom
machine: pc-q35-8.1
memory: 32768
meta: creation-qemu=7.1.0,ctime=1673962676
name: XXXXXXXXXXXX
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr1
numa: 1
ostype: win11
scsi0: datastore1:vm-116-disk-1,cache=writeback,discard=on,iothread=1,size=100G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=4c3d90cd-9a00-449b-be71-37bd8327c2e6
sockets: 2
tablet: 0
tpmstate0: datastore1:vm-116-disk-2,size=4M,version=v2.0
vmgenid: a9f85d0e-d80d-40ef-b891-71d37cb57f00
Thanks for your comment.
Bash:
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-11
proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3
proxmox-kernel-6.5: 6.5.13-3
pve-kernel-5.15.143-1-pve: 5.15.143-1
pve-kernel-5.15.131-2-pve: 5.15.131-3
pve-kernel-5.15.131-1-pve: 5.15.131-2
pve-kernel-5.15.116-1-pve: 5.15.116-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.3
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.5
libpve-cluster-perl: 8.0.5
libpve-common-perl: 8.1.1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.6
libpve-network-perl: 0.9.6
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.1.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
openvswitch-switch: 3.1.0-2+deb12u1
proxmox-backup-client: 3.1.5-1
proxmox-backup-file-restore: 3.1.5-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.5
pve-cluster: 8.0.5
pve-container: 5.0.9
pve-docs: 8.1.5
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.1
pve-qemu-kvm: 8.1.5-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.1.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve1
Bash:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 48 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Vendor ID: AuthenticAMD
BIOS Vendor ID: Advanced Micro Devices, Inc.
Model name: AMD EPYC 7452 32-Core Processor
BIOS Model name: AMD EPYC 7452 32-Core Processor CPU @ 2.3GHz
BIOS CPU family: 107
CPU family: 23
Model: 49
Thread(s) per core: 2
Core(s) per socket: 32
Socket(s): 2
Stepping: 0
Frequency boost: enabled
CPU(s) scaling MHz: 83%
CPU max MHz: 2350.0000
CPU min MHz: 1500.0000
BogoMIPS: 4690.86
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4
_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsb
ase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decod
eassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca
Virtualization features:
Virtualization: AMD-V
Caches (sum of all):
L1d: 2 MiB (64 instances)
L1i: 2 MiB (64 instances)
L2: 32 MiB (64 instances)
L3: 256 MiB (16 instances)
NUMA:
NUMA node(s): 2
NUMA node0 CPU(s): 0-31,64-95
NUMA node1 CPU(s): 32-63,96-127
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Retbleed: Mitigation; untrained return thunk; SMT enabled with STIBP protection
Spec rstack overflow: Mitigation; Safe RET
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; Retpolines, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Srbds: Not affected
Tsx async abort: Not affected
Bash:
Linux psi-pve-01 6.5.13-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.13-3 (2024-03-20T10:45Z) x86_64 GNU/LinuxCWT Makes a good point, you can also increase the virtual graphical memory allocated to the server. However, the "best" available graphical performance improvement would be with a passthrough GPU. Second to that would be a GPU owned by the hypervisor and then virtualized to the VM (or multiple VMs, which is the benefit of having it owned by the hypervisor instead of directly passed through to a single VM). This is known as VirGL, by the way. Very exciting times to have VirGL around...
Another consideration: https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices Consider reviewing the Devices section of Computer Management for missing drivers. Your VM appears to be configured optimally from the second post you made in this thread, nothing else strikes me as odd. Excel on Windows Server and LibreOffice Calc on Ubuntu Terminal Server hosts have always had artefacts in my experience, however, you may also find a few OS-specific changes on your RDS Server can help:
Cheers,
Tmanok
Another consideration: https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices Consider reviewing the Devices section of Computer Management for missing drivers. Your VM appears to be configured optimally from the second post you made in this thread, nothing else strikes me as odd. Excel on Windows Server and LibreOffice Calc on Ubuntu Terminal Server hosts have always had artefacts in my experience, however, you may also find a few OS-specific changes on your RDS Server can help:
- Try reducing 3D effects, adjusting visual effects, and disabling unnecessary animations.
- In Group Policy, there are specific settings for RDS servers to improve graphics performance. See below:
- You can try the Citrix Optimizer Tool for RDS Servers (works on PVE as well): https://support.citrix.com/article/CTX224676/citrix-optimizer-tool
- Alternatively, you can try the VMWare Horizon Tool instead but Citrix is better known for being "all about RDS & VDI".
- There's also a bug with WS2022, see Bin Tang's answer (scroll down) to delete a useless file causing massive performance issues: https://learn.microsoft.com/en-us/a...r-2022-and-teams-bloats-hkey-local-machinesys this has helped a lot of users.
Cheers,
Tmanok
Last edited:
In addition to the points mentioned by @Tmanok you can restrict the RDP transport protocol to TCP only via GPO:
Computer Configuration / Administrative Templates/ Windows Components/ Remote Desktop Services/ Remote Desktop Session Host/ Connections/ "Select RDP transport protocols" -> TCP only
And remember that changes in hardware (VirtIO GPU) become only effective when the VM is powered off. If only rebooted, hardware changes are not applied.
Some thoughts on TCP vs. UDP, UDP will always perform better for low latency requirements.
https://www.rdpsoft.com/blog/remote-desktop-protocol/rdp-udp-transport-azure/
Cheers,
Tmanok
https://www.rdpsoft.com/blog/remote-desktop-protocol/rdp-udp-transport-azure/
Cheers,
Tmanok