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.
Description of problem:
Boot guest with -cpu 4,maxcpus=8, then hot add vcpu. from monitor, we can see that we can hot add more than 8 vcpus. in guest, guest can recognize maxcpus.from guest of view,this is ok,however,from monitor view,it's not very good.
Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.257.el6.x86_64
seabios-0.6.1.2-13.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Boot guest -cpu 4,maxcpus=8
2.Hot add vcpu
3.(qemu) info cpus
* CPU #0: pc=0xffffffff810377cb (halted) thread_id=10742
CPU #1: pc=0xffffffff810377cb (halted) thread_id=10743
CPU #2: pc=0xffffffff810377cb (halted) thread_id=10744
CPU #3: pc=0xffffffff810377cb (halted) thread_id=10745
CPU #4: pc=0xffffffff810377cb (halted) thread_id=10844
CPU #5: pc=0xffffffff810377cb (halted) thread_id=10845
CPU #6: pc=0xffffffff810377cb (halted) thread_id=11219
CPU #7: pc=0xffffffff810377cb (halted) thread_id=11221
CPU #8: pc=0x00000000fffffff0 thread_id=11223
CPU #9: pc=0x00000000fffffff0 thread_id=11225
CPU #10: pc=0x00000000fffffff0 thread_id=11426
CPU #11: pc=0x00000000fffffff0 thread_id=11427
Actual results:
After step3,as you can see,more than 8 vcpu
Expected results:
Should give a friendly message that tell user can not hot add vcpu more than maxcpus number.
Additional info:
In guest,guest can recognize maxcpus number at most, from guest point,it's ok.
to fix it we need sanity check for maxcpus and bug 807512 are about the same. So I'll dup it to bug 807512
*** This bug has been marked as a duplicate of bug 807512 ***