Created attachment 1667797 [details] logs Description of problem:vdsm.log reports CPU controller errors even if the VM is started. Version-Release number of selected component (if applicable): http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-23 How reproducible: always Steps to Reproduce: 1. Create VM on the base of latest-rhel-guest-image-8.1-infra template. 2. Run-once on host Actual results: VM starts though in vdsm there are a lot of errors reported : 020-03-05 16:39:15,077+0200 ERROR (jsonrpc/6) [virt.vm] (vmId='44db4be9-a5a5-491d-b254-7036a5a704e8') Operation failed (vm:4788) Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 4765, in setCpuTunePeriod self._dom.setSchedulerParameters({'vcpu_period': int(period)}) File "/usr/lib/python3.6/site-packages/vdsm/virt/virdomain.py", line 101, in f ret = attr(*args, **kwargs) 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 2555, in setSchedulerParameters if ret == -1: raise libvirtError ('virDomainSetSchedulerParameters() failed', dom=self) libvirt.libvirtError: Requested operation is not valid: cgroup CPU controller is not mounted 2020-03-05 16:39:15,077+0200 INFO (jsonrpc/6) [api.virt] FINISH setCpuTunePeriod return={'status': {'code': 62, 'message': 'Requested operation is not valid: cgroup CPU controller is not mounted'}} from=::1,60536, vmId=44db4be9-a5a5-491d-b254-7036a5a704e8 (api:54) Expected results: no libvirt errors on VM start Additional info:
thanks to phrdina's investigation, this is bug 1808940
verified in http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-27
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.