Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1779161

Summary: HP VM could not be started if TSC scaling is not supported by the host CPU.
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Tomasz BaraƄski <tbaransk>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: bugs, rbarry, tbaransk
Target Milestone: ovirt-4.4.0Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.40.7, ovirt-engine-4.4.0 gitb5b5c99ca2f Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 20:02:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log
none
log for re-tested scenario
none
vdsm log for re-tested scenario in 4.4.0-17 none

Description Polina 2019-12-03 12:41:38 UTC
Created attachment 1641659 [details]
engine.log

Description of problem: HP VM fails to start if host doesn't support TSC.

Version-Release number of selected component (if applicable):
http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-5

How reproducible: always


Steps to Reproduce:
1.configure VM as HP 
2.start on host not supporting tsc
 virsh -r capabilities | grep "counter name='tsc'"
      <counter name='tsc' frequency='2300000000' scaling='no'/>


Actual results: fails to start


Expected results: VM must be started


Additional info:

Comment 1 Polina 2020-01-28 14:37:00 UTC
tested on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-17 . the bug is still there

Comment 2 Polina 2020-02-04 14:18:49 UTC
Created attachment 1657567 [details]
log for re-tested scenario

Tomasz, I attached the log for the re-tested scenario in 4.4.0-17. please see at the end , the VM golden_env_mixed_virtio_3

Comment 3 Polina 2020-02-04 14:29:04 UTC
Created attachment 1657578 [details]
vdsm log for re-tested scenario in 4.4.0-17


attached vdsm.log for the re-tested scenario. please see from the line :

2020-02-04 16:07:15,090+0200 ERROR (vm/8df439a8) [virt.vm] (vmId='8df439a8-63a1-423e-8c55-6f1555945f02') The vm start process failed (vm:834)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 768, in _startUnderlyingVm
    self._run()
  File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2570, in _run
    dom.createWithFlags(flags)
  File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1265, in createWithFlags
    if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
libvirt.libvirtError: unsupported configuration: Requested TSC frequency 2299000000 Hz does not match host (2299998000 Hz) and TSC scaling is not supported by the host CPU
2020-02-04 16:07:15,090+0200 INFO  (vm/8df439a8) [virt.vm] (vmId='8df439a8-63a1-423e-8c55-6f1555945f02') Changed state to Down: unsupported configuration: Requested TSC frequency 2299000000 Hz does not match host (2299998000 Hz) and TSC scaling is not supported by the host CPU (code=1) (vm:1592)

Comment 4 Polina 2020-02-05 20:12:51 UTC
Hi Tomasz, re-tested on the latest build http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-18. the same problem.

Comment 8 Polina 2020-03-25 21:22:36 UTC
verifying  on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-26

Comment 9 Sandro Bonazzola 2020-05-20 20:02:55 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.