Description of problem: We see this issue while creating a Windows10 VM on cnv2-engineering We see the status message: server error. command SyncVMI failed: "LibvirtError(Code=67, Domain=10, Message=''unsupported configuration: Requested TSC frequency 1699998000 Hz is outside tolerance range ([2099473001, 2100522999] Hz) around host frequency 2099998000 Hz and TSC scaling is not supported by the host CPU'') Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Windows10 VM on cnv2-engineering 2. 3. Actual results: VM fails to start with message: "LibvirtError(Code=67, Domain=10, Message=''unsupported configuration: Requested TSC frequency 1699998000 Hz is outside tolerance range ([2099473001, 2100522999] Hz) around host frequency 2099998000 Hz and TSC scaling is not supported by the host CPU'') Expected results: VM starts successfully. Additional info: But looking at this, it should already have been fixed https://gitlab.com/libvirt/libvirt/-/issues/188 Surprisingly we see this issue still with 4.11.1.
Disabling reenlightenment seems to be a temporary work around: kind: VirtualMachine spec: template: spec: domain: features: hyperv: # reenlightenment: {}
We would be fixing this bug in 4.12.0 https://bugzilla.redhat.com/show_bug.cgi?id=2139896
I just bumped into this bug with 4.11.z. Do we plan to backport this fix? Is it hard/dangerous to do so?
Hey @danken, I've made a backport PR here: https://github.com/kubevirt/kubevirt/pull/8996.
Thanks. I hope it wasn't hard and isn't too dangerous.
Verified on CNV 4.12.1-40 We should document that there is a known limitation of mixed clusters with non-scalable nodes: https://bugzilla.redhat.com/show_bug.cgi?id=2151169#c9
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 4.12.6 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:4982