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 1162080

Summary: "-numa node" option cause windows guest can not online hot-added CPUs
Product: Red Hat Enterprise Linux 7 Reporter: FuXiangChun <xfu>
Component: qemu-kvm-rhevAssignee: Igor Mammedov <imammedo>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: drjones, hhuang, huding, imammedo, juzhang, michen, mrezanin, rhodain, virt-maint, ypu
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-rhev-2.2.0-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1191384 1191385 (view as bug list) Environment:
Last Closed: 2015-12-04 16:20:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1188200, 1191384, 1191385    

Description FuXiangChun 2014-11-10 08:59:28 UTC 
Description of problem:
Boot win2008r2 & win2012r2 guest with "-numa node", then Hotplug vCPU to guest via QMP.  can not find hot-added cpus via Task Manager inside guest.  

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.2-6.el7.x86_64
3.10.0-196.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. /usr/libexec/qemu-kvm -name windows  -m 4G -smp 1,cores=1,threads=1,sockets=64,maxcpus=240 -numa node ....

2. Hotplug vCPU to guest via QMP

3. check Task Manager inside guest

Actual results:
can not find Hot-added cpus

Expected results:
should find at least 8.

Additional info:
1. As 968811 is fixed. so for RHEL7.1 guest didn't hit this issue.

2. QE tested qemu-kvm-1.5.3-60.el7.x86_64 and qemu-kvm-1.5.3-77.el7.x86_64, Both of them hit this issue. so it is not regression bug.

3. can find Hot-added CPUs in device management inside guest(no online).

4. As linux guest didn't hit this issue. only windows guest has this issue. so QE is not sure if it is a qemu-kvm's bug.
Comment 2 Igor Mammedov 2014-11-10 10:00:46 UTC 
I've also reproduced it, hot-added CPUs are actually seen by guest in device manager but not onlined/used by it until reboot.
Comment 3 Igor Mammedov 2015-02-03 10:53:16 UTC 
*** Bug 1188584 has been marked as a duplicate of this bug. ***
Comment 4 Igor Mammedov 2015-02-03 10:54:32 UTC 
fixed upstream: v2.2.0-rc2-30-gdd0247e
[dd0247e09a542d2a7ba6e390c70b5616edb9ec56] pc: acpi: mark all possible CPUs as enabled in SRAT
Comment 5 biaoxiangye 2015-02-06 01:52:27 UTC 
good job
Comment 8 huiqingding 2015-03-24 03:12:25 UTC 
Reproduce this bug using the following version:
qemu-kvm-rhev-2.1.2-23.el7.x86_64
kernel-3.10.0-232.el7.x86_64

Test steps:
1. boot a win2012r2 guest with 1 vcpu
/usr/libexec/qemu-kvm -name windows  -m 4G -smp 1,cores=1,threads=1,sockets=64,maxcpus=240 -numa node ....

2. Hotplug vCPU to guest via QMP
{"execute": "qmp_capabilities"}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id": 1  }}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id":2}}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id":3}}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id":4}}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id":5}}
{"return": {}}

3. check Task Manager inside guest

Actual results:
can not find Hot-added cpus.
Comment 9 huiqingding 2015-03-24 03:16:24 UTC 
Test this bug using the following version:
qemu-kvm-rhev-2.2.0-8.el7.x86_64
kernel-3.10.0-232.el7.x86_64

Tested guest:
win2012r2, win2008r2-64

Test steps:
1. boot a win2012r2/win2008r2-64 guest with 1 vcpu
/usr/libexec/qemu-kvm -name windows  -m 4G -smp 1,cores=1,threads=1,sockets=64,maxcpus=240 -numa node ....

2. Hotplug vCPU to guest via QMP
{"execute": "qmp_capabilities"}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id": 1  }}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id": 2  }}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id": 3  }}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id": 4  }}
{"return": {}}
{ "execute": "cpu-add", "arguments": { "id": 5  }}
{"return": {}}

3. check Task Manager inside guest

Actual results:
can find 6 cpus in "Task Manager".
Comment 11 huiqingding 2015-06-24 05:42:43 UTC 
Based on Comment 9, set this bug to VERIFIED.

Best regards,
Huiqing
Comment 13 errata-xmlrpc 2015-12-04 16:20:58 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-2546.html