Bug 2139896

Summary: Requested TSC frequency outside tolerance range & TSC scaling not supported
Product: Container Native Virtualization (CNV) Reporter: Kedar Bidarkar <kbidarka>
Component: VirtualizationAssignee: Itamar Holder <iholder>
Status: CLOSED ERRATA QA Contact: Denys Shchedrivyi <dshchedr>
Severity: high Docs Contact:
Priority: high    
Version: 4.11.1CC: acardace, danken, dholler, dshchedr, iholder, sgott
Target Milestone: ---   
Target Release: 4.12.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hco-bundle-registry-containerv-4.12.0-736 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2151169 (view as bug list) Environment:
Last Closed: 2023-09-05 16:29:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2151169, 2174229    

Description Kedar Bidarkar 2022-11-03 18:26:59 UTC
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.

Comment 1 Dominik Holler 2022-11-11 08:16:43 UTC
Disabling reenlightenment seems to be a temporary work around:


kind: VirtualMachine
spec:
  template:
    spec:
      domain:
        features:
          hyperv:
            # reenlightenment: {}

Comment 6 Kedar Bidarkar 2022-11-21 14:42:44 UTC
We would be fixing this bug in 4.12.0 https://bugzilla.redhat.com/show_bug.cgi?id=2139896

Comment 9 Dan Kenigsberg 2022-12-22 15:00:48 UTC
I just bumped into this bug with 4.11.z. Do we plan to backport this fix? Is it hard/dangerous to do so?

Comment 10 Itamar Holder 2022-12-25 13:47:51 UTC
Hey @danken,

I've made a backport PR here: https://github.com/kubevirt/kubevirt/pull/8996.

Comment 11 Dan Kenigsberg 2022-12-25 13:49:55 UTC
Thanks. I hope it wasn't hard and isn't too dangerous.

Comment 14 Denys Shchedrivyi 2023-02-17 20:32:21 UTC
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

Comment 21 errata-xmlrpc 2023-09-05 16:29:19 UTC
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