meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
vm:proxmox:kvm:windows:mitigations [2025/01/09 07:34] – niziakvm:proxmox:kvm:windows:mitigations [2026/10/13 19:08] (current) – niziak
Line 1: Line 1:
 ====== mitigations ====== ====== mitigations ======
  
-I've noticed that switching from ''kvm64'' CPU to ''x86-64-v2-AES'' or ''host'' slows down Windows guest insanely.+I've noticed that switching from ''kvm64'' CPU to ''x86-64-v2-AES'' or ''host'' slows down Windows guest insanely on Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz host. 
 + 
 +The ''flush_l1d'' flag in Proxmox (often passed when using ''cpu type=host'') is a security mitigation against L1 Terminal Fault (L1TF/Foreshadow) side-channel attacks. While important for security, it can significantly degrade performance, particularly in Windows VMs, resulting in high memory read latency and reduced performance in tasks like AI model loading or 3D applications 
 + 
 +Choose CPU: 
 +  * ''ivybridge'' CPU mark 4236. Memory mark: 1899. User experience slower than ''kvm64'' 
 +  * ''ivybridge-IBRS'' - (Adds only ''spec-ctrl'') for security. CPU mark 4202. Memory mark: 1935. 
 +  * ''x86-64-v2-AES'' CPU mark: 4081. Memory mark: 1906. 
 +  * ''kvm64'' CPU mark: 4030. Memory mark: 1931. 
 +  * ''host'' + ''hv-passthrough''- pass HyperV flags to guest to let him know that it runs under VM. CPU mark 4249. Memory mark: 1899. 
 +  * ''host'' - **insanely slow!!!** CPU mark 2750 
 + 
 +Benchmark 2 (new Proxmox, No numa, pinned to 8 cores - every 2nd to skip HT -  from 1 socket) 
 +  * ''kvm64,flags=+aes;-md-clear;-spec-ctrl'' - CPU mark: 3713, Memory mark: 2093   
 +  * ''IvyBridge,flags=+aes;-md-clear;-spec-ctrl''  - CPU mark: 3864, Memory mark: 1984 
 + 
 +Benchmark 3 (new Proxmox, numa 2x8, pinned to cores - every 2nd to skip HT) 
 +  * ''host,flags=+aes;-md-clear;-spec-ctrl'' - CPU mark: 2588, Memory mark: 2039  
 +  * ''IvyBridge-IBRS,flags=+aes;-md-clear;-spec-ctrl'' - CPU mark: 4295, Memory mark: 2065 
 + 
 +<file ini /etc/pve/qemu-server/xxx.conf> 
 +args: -cpu host,hv-passthrough 
 +</file> 
 + 
 + 
 +The ''spec-ctrl'' KVM feature is a CPU flag passed to virtual machines (VMs) to enable indirect branch restricted speculation (IBRS) and indirect branch prediction barrier (IBPB) support, mitigating Spectre v2 vulnerabilities. It allows guests to utilize hardware-level security, requiring microcode/BIOS updates on the host 
 + 
 + 
 +  * [[https://forum.proxmox.com/threads/the-reasons-for-poor-performance-of-windows-when-the-cpu-type-is-host.163114/|The Reasons for poor performance of Windows when the CPU type is host]]
  
 Mitigations can be disabled in Windows guest using this tool: Mitigations can be disabled in Windows guest using this tool:
Line 7: Line 35:
 [[https://www.grc.com/inspectre.htm|InSpectre]] [[https://www.grc.com/inspectre.htm|InSpectre]]
  
 +Or:
 +<code powershell>
 +reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverride /t REG_DWORD /d 3 /f
 +reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v FeatureSettingsOverrideMask /t REG_DWORD /d 3 /f
 +</code>
  
-Another slowing-down feature: "Core isolation: memory integrity”+===== Win10 on old Xeon =====
  
-<code reg> +Very good performance: 
-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity +<file ini /etc/pve/qemu-server/100.conf> 
-</code>+affinity: 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 
 +cores: 8 
 +numa: 1 
 +cpu: IvyBridge-IBRS,flags=+aes;-md-clear;-spec-ctrl 
 +</file>