A Proxmox user account describes improving desktop responsiveness by changing a VM’s generic CPU type to host to expose the physical processor’s instructions, and using a SPICE client instead of browser-based noVNC. CPU-setting benefits vary by workload, and host mode restricts live migration between different CPUs. SPICE requires a separate client, while VirtIO-GPU may suit modern Linux or Wayland better than QXL. This is a personal case rather than a quantitative benchmark, so each change should be compared against compatibility requirements, the guest operating system and graphics configuration.
Back to Tech
Proxmox desktop VM tuning calls for checking CPU type and display transport
Single-host optimization can conflict with portability across different CPUs, so settings should match the workload.