Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 748703

Summary: Error in the libvirt log when starting VM via RHEV-M
Product: Red Hat Enterprise Linux 6 Reporter: Mike Cao <bcao>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: abaron, acathrow, ajia, bazulay, bcao, iheim, juzhang, michen, mzhan, rwu, shuang, weizhan, ykaul
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-25 09:34:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mike Cao 2011-10-25 05:14:08 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
# rpm -q kernel libvirt vdsm qemu-kvm spice-server
kernel-2.6.32-209.el6.x86_64
libvirt-0.9.4-19.el6.x86_64
vdsm-4.9-96.1.el6.x86_64
qemu-kvm-0.12.1.2-2.200.el6.x86_64
spice-server-0.8.2-4.el6.x86_64
RHEV Manager for Servers and Desktops :3.0.0_0001-40.el6

How reproducible:
100%

Steps to Reproduce:
1.on the host #mount -t cgroup -o cpu none /cgroup/
2.start a VM via virt-manager
3.#on the host #tail -f /var/log/vdsm/libvirt.log
  
Actual results:
After step3.it shows following msg:
11:08:43.719: 13973: error : virNetClientProgramDispatchError:170 : Requested operation is not valid: cgroup CPU controller is not mounted
			<driver cache="none" error_policy="stop" io="threads" name="qemu" type="raw"/>


Expected results:
no cgroup error printed 

Additional info:
I am not sure whether it is a libvirt bug or vdsm bug ,move it to the right component if I were wrong .
Comment 2 Mike Cao 2011-10-25 06:55:19 UTC 
 (In reply to comment #1)
> All RPMs but VDSM are updated. Please update your VDSM as well and retry.

Update vdsm to vdsm-4.9-110.el6.x86_64 still hit this issue ,

Based on above ,re-open this Bug .
Comment 4 Dan Kenigsberg 2011-10-25 07:15:28 UTC 
Why are you mounting cgroup manually? Isn't cgroup service on when you boot?

How come you can even start a VM via virt-manager? When Vdsm is installed, running VMs via non-Vdsm managers is blocked with sasl and unsupported.

Please provide the needed info and reopen the bug if you also fail to start VMs from RHEV-M.
Comment 5 Mike Cao 2011-10-25 07:41:01 UTC 
(In reply to comment #4)
> Why are you mounting cgroup manually? Isn't cgroup service on when you boot?
> 

I tried both all reports cgroup error in libvirt.log 

> How come you can even start a VM via virt-manager? When Vdsm is installed,
> running VMs via non-Vdsm managers is blocked with sasl and unsupported.

sorry ,the step2 should be :start VM via RHEV-M 

> 
> Please provide the needed info and reopen the bug if you also fail to start VMs
> from RHEV-M.
the VM could be started via RHEV-M ,but there are cgroup error logs which described in comment #0 in /var/log/vdsm/libvirt.log
Comment 6 Mike Cao 2011-10-25 07:41:39 UTC 
Hi, Dan 

Based on comment #5, May I re-open this bug ?

Best Regards,
Mike
Comment 7 Dan Kenigsberg 2011-10-25 08:59:00 UTC 
sure - I specifically asked you to reopen the bug if it's unrelated to virt-manager.

However, you did not answer my question: Is cgroup service on when you boot? What's chkconfig --list cgroup.

If it is only a logging issue, with no functional effect, I do not see it fixed for 6.2. But please discuss this with libvirt guys.
Comment 8 Mike Cao 2011-10-25 09:34:11 UTC 
(In reply to comment #7)
> sure - I specifically asked you to reopen the bug if it's unrelated to
> virt-manager.
> 
> However, you did not answer my question: Is cgroup service on when you boot?
> What's chkconfig --list cgroup.

Referring to the docs http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Resource_Management_Guide/ch-Using_Control_Groups.html
 ,the services is disabled on boot  
#chkconfig --list |grep cgconfig
cgconfig       	0:off	1:off	2:off	3:off	4:off	5:off	6:off

After #chkconfig --level 345 cgconfig on ,then reboot the guest  ,the issue has gone. 

Thanks for pointing this !
Mike
> 
> If it is only a logging issue, with no functional effect, I do not see it fixed
> for 6.2. But please discuss this with libvirt guys.
Comment 9 Mike Cao 2011-10-25 09:34:55 UTC 
based on comment #8 ,close this Bug