http://192.168.180.206:8001/ 2026-05-13T03:22:53+00:00 http://192.168.180.206:8001/ http://192.168.180.206:8001/_media/wiki:dokuwiki.svg text/html 2020-10-06T08:12:29+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/vm:proxmox:kvm:windows:migrate_from_vb?rev=1601971949&do=diff Migrate from VirtualBox Migrate Windows 7/10 Virtual Box (Optional) Preparation Cleanup disc space and remove all unnecessary drivers: * uninstall Virtual Box Guest Additions * Download and run registry file: Mergeide.zip * Restart VM * sdelete -z c: d: e: text/html 2026-03-22T20:24:26+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/vm:proxmox:kvm:windows:mitigations?rev=1774211066&do=diff mitigations 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 … text/html 2026-02-03T10:38:27+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/vm:proxmox:kvm:windows:mssql?rev=1770115107&do=diff MS SQL move database files to optimized storage Recommended NTFS cluster size for MSSQL is 64kB. So ZFS's volblocksize also should be 64kB. Move MSSQL guest data files to dedicated VM disk. First create new VM disk: zfs create nvmpool/data/vm-703-disk-3 -b 64k -V 16G zfs set logbias=throughput nvmpool/data/vm-703-disk-3 qm disk rescan