This message was deleted.

Nevermind, after further investigation, it seems to be working even with the label cpumanager=false, so I don't need to worry about that. I think KubeVirt is the one messing with the label, but my VMs still seem to be pinned according to 'top', 'cat /var/lib/kubelet/cpu_manager_state' and taskset. The label only became an issue when I tried to set dedicatedCpuPlacement in the VM's config YAML and the VMs couldn't be scheduled, but I didn't set that on these new VMs and they are pinned fine.