Bug 1191385

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: Igor Mammedov <imammedo>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: drjones, hhuang, imammedo, juzhang, linchen, michen, mrezanin, pm-eus, rhodain, virt-maint, xfu, ypu
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-rhev-2.1.2-23.el7_1.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1162080 Environment:
Last Closed: 2015-03-12 13:37:23 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:55 UTC
This bug has been copied from bug #1162080 and has been proposed
to be backported to 7.1 z-stream (EUS).

Comment 4 FuXiangChun 2015-02-25 05:20:38 UTC
Reproduced bug with qemu-kvm-rhev-2.1.2-23.el7.x86_64 & win2012-64r2 guest.

Verified this bug with qemu-kvm-rhev-2.1.2-23.el7_1.1 & win2008r2 & win2012r2.

step:
hotplug 64 vcpu to guest via qmp.  all vcpus can be found in Task Manager.

so, This bug is fixed.

Comment 6 FuXiangChun 2015-02-25 08:19:29 UTC
Additional, QE tested some other scenarios for regression test. all scenarios works well.

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

Comment 9 errata-xmlrpc 2015-03-12 13:37:23 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-0677.html