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.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0276.html
Description of problem: It is failed to start guest when the number of vcpu is different between <vcpu> and <cputune/> Version-Release number of selected component (if applicable): libvirt-0.10.1-1.el6.x86_64 qemu-kvm-0.12.1.2-2.305.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.# virsh list --all Id Name State ---------------------------------------------------- 18 rhel6.2 running 2. # virsh dumpxml rhel6.2 <domain type='kvm' id='27'> <vcpu placement='auto'>2</vcpu> ... </domain> 3.# virsh vcpupin rhel6.2 0 0 --config 4.# virsh destroy rhel6.2 Domain rhel6.2 destroyed 5.# virsh start rhel6.2 error: Failed to start domain rhel6.2 error: An error occurred, but the cause is unknown 6. # virsh dumpxml rhel6.2 <domain type='kvm' id='30'> <vcpu placement='auto'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> </cputune> 7.Check the log. 5442 2012-09-03 09:02:57.626+0000: 11144: debug : virCgroupRemoveRecursively:727 : Removing cgroup /cgroup/blkio/libvirt/qemu/rhel6.2/ 5443 2012-09-03 09:02:57.626+0000: 11144: error : virCgroupRemoveRecursively:730 : Unable to remove /cgroup/blkio/libvirt/qemu/rhel6.2/ (16) 5444 2012-09-03 09:02:57.626+0000: 11144: debug : virFileClose:72 : Closed fd 22 5445 2012-09-03 09:02:57.626+0000: 11144: debug : qemuProcessStop:4036 : Shutting down VM 'rhel6.2' pid=15145 flags=0 5446 2012-09-03 09:02:57.626+0000: 11144: debug : virFileClose:72 : Closed fd 22 5447 2012-09-03 09:02:57.626+0000: 11144: debug : qemuMonitorClose:788 : QEMU_MONITOR_CLOSE: mon=0x7f1134007460 refs=2 5448 2012-09-03 09:02:57.626+0000: 11144: debug : virEventPollRemoveHandle:175 : EVENT_POLL_REMOVE_HANDLE: watch=112 5449 2012-09-03 09:02:57.626+0000: 11144: debug : virEventPollRemoveHandle:188 : mark delete 8 24 5450 2012-09-03 09:02:57.626+0000: 11144: debug : virEventPollInterruptLocked:701 : Interrupting 5451 2012-09-03 09:02:57.626+0000: 11144: debug : virFileClose:72 : Closed fd 24 5452 2012-09-03 09:02:57.626+0000: 11144: debug : virObjectUnref:135 : OBJECT_UNREF: obj=0x7f1134007460 5453 2012-09-03 09:02:57.626+0000: 11144: debug : qemuProcessKill:3934 : vm=rhel6.2 pid=15145 flags=5 Actual results: It is failed to start guest when the number of vcpu is different between <vcpu> and <cputune/> Expected results: Successfully start it. Additional info: