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.
---Problem Description---
Command "virsh setvcpus <domainname> <vcpucount>" is not working.
# virsh list
Id Name State
----------------------------------
28 R6-64 running
29 R6-32 running
33 rhel5.6-32 running
37 SLES11-32 running
# virsh setvcpus 37 3
error: internal error unable to execute QEMU command 'cpu_set': The command cpu_set has not been found
---uname output---
Linux phx3.in.ibm.com 2.6.32-118.el6.x86_64 #1 SMP Tue Feb 22 11:15:55 EST 2011 x86_64 x86_64 x86_64
GNU/Linux
Machine Type = HS22
---Debugger---
A debugger is not configured
---Steps to Reproduce---
1. Start a guest OS giving virsh command: virsh create <xml-file-name>
2. Once the guest is started, give the command : virsh setvcpus <domainname> <cpu-count>
---KVM Component Data---
Userspace tool common name: virsh
The userspace tool has the following bit modes: 64 bit
Userspace rpm: libvirt-0.8.7-7.el6.x86_64
Userspace tool obtained from project website: na
1.Server architecture(s) (please list all effected) (x86/POWER6/Z/etc.):
x86
2.Server type (9117-MMA/HS20/s390/etc.):
HS22
3.General component (desktop/kernel/base OS/dev tools/etc.):
virsh
4.Other components involved (ixgbe/java/emulex/etc.):
no
5.Does the server have the latest GA firmware?
yes
6.Has the problem been shown to occur on more than one system?
yes
7.Is a tested patch available?
no
If yes to the above, has it been approved upstream?
8.What is the latest official Red Hat build on which this bug has been
seen?
6.1 Alpha
-------
This looks identical to https://bugzilla.redhat.com/show_bug.cgi?id=533138, Should this work in 6.1
Alpha?
This is a limitation in the qemu monitor commands - qemu support for CPU hotplug is not yet fully functional. Libvirt can't do any better than what qemu provides, and qemu isn't slated to fix things until RHEL 6.2 when bug 562886 is fixed.
*** This bug has been marked as a duplicate of bug 533138 ***