Skip to content
Two Proxmox defaults: Hyper-V enlightenments switched on by the VM's OS Type, and CPU microcode switched on by how the host was installed

Two Proxmox VE 9 Defaults You Might Not Have: Hyper-V Enlightenments and CPU Microcode

Proxmox VE 9 turns on Hyper-V enlightenments for Fisher-Price OS (Windows) guests and installs CPU microcode on new hosts, but only if the VM was given a Microsoft Windows OS type and the host came from the 9.x installer. This covers what the enlightenments do, the exact rules qemu-server uses to pick them (measured on a live 9.2 host), why machine version pinning keeps older VMs off the July 2026 hv-evmcs fix, the pve-qemu-kvm build that fix needs and what each QEMU release since 10.0 fixed for those guests, why they belong on q35 and never i440fx (which the wizard still hands most of them), the two flags you can set by hand, how to prove what a VM is running, where microcode comes from (board firmware, Debian and Proxmox’s own repository), why an upgraded host has none (with an Intel node four Intel releases behind as the example), the initramfs rebuild that installing it triggers and the older kernels that rebuild misses, the Zen 5 RDSEED failure that follows, enabling it, a rolling reboot across a Ceph cluster, and rolling back a bad update.

27th October 2026 · 25 min · 6016 words · Damien Dye
One physical GPU split into virtual functions handed to separate Windows desktops

Licence-Free Windows VDI on Proxmox with an Intel Arc Pro B50 — and the Firmware Limit That Stopped It

Intel’s Arc Pro cards do SR-IOV natively, with no vGPU licence to buy — which makes a licence-free Windows VDI on Proxmox genuinely possible. The whole build on a B50, the Windows-first bootstrap problem, why the firmware caps it at two virtual functions, and how many each card in the B-series gives you.

7th August 2026 · 16 min · 3385 words · Damien Dye
A guest clock drifting away from the host clock, and a hypercall pulling it back

A VM's Clock Cannot Be Trusted — and the ptp_kvm Fix for QEMU/KVM

A virtual machine’s clock is built on an assumption virtualisation breaks: that the CPU keeps counting. Why guest time drifts on every hypervisor, what the skew actually breaks — Kerberos, TLS, Ceph, Windows — and how ptp_kvm fixes it properly on QEMU/KVM.

7th August 2026 · 14 min · 2897 words · Damien Dye