Bug 1191384

Summary: "-numa node" option cause windows guest can not online hot-added CPUs
Product: Red Hat Enterprise Linux 7 Reporter: Libor Miksik <lmiksik>
Component: qemu-kvm-rhevAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED EOL QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: drjones, hhuang, imammedo, jkurik, juzhang, knoel, michen, pm-eus, qiguo, rhodain, virt-maint, xfu, ypu
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.3-60.el7_0.12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1162080 Environment:
Last Closed: 2015-03-09 08:58:11 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:
Bug Depends On: 1162080    
Bug Blocks:    

Description Libor Miksik 2015-02-11 08:45:27 UTC 
This bug has been copied from bug #1162080 and has been proposed
to be backported to 7.0 z-stream (EUS).
Comment 3 Miroslav Rezanina 2015-02-19 10:52:51 UTC 
Fix included in qemu-kvm-1.5.3-60.el7_0.12
Comment 5 Qian Guo 2015-02-26 07:13:10 UTC 
Reproduced bug with qemu-kvm-rhev-1.5.3-60.el7_0.10.x86_64 & win2012-64r2 guest.

Verified this bug with qemu-kvm-rhev-1.5.3-60.el7_0.12.x86_64 & win2008r2 & win2012r2.

step:
hotplug vcpus to 240, all vcpus can be found in Task Manager.

so, This bug is fixed.

Additional info:

1.During verify this bug, following senarios are coverd:
S1. reboot guest after hotplug vcpu 

S2. shutdown guest after hotplug vcpu

S3. hotplug 240 vcpu to guest
    can see all vcpus in task manager for win2012r2 guest.

S4. hotplug existing vcpu

S5. hotplug vcpu number >Max support(240) 

S6. hotplug illegal vcpu number

2.Test RHEL7.1 guest, works well, from dmesg can get the hotplug and online logs, and no error found, the vcpus are added successfully.
Comment 7 Jan Kurik 2015-03-09 08:58:11 UTC 
The advisory has been dropped,
RHEL-7.0 is now EOL.