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 1191384 - "-numa node" option cause windows guest can not online hot-added CPUs
Summary: "-numa node" option cause windows guest can not online hot-added CPUs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.1
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1162080
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-11 08:45 UTC by Libor Miksik
Modified: 2015-03-11 02:18 UTC (History)
13 users (show)

Fixed In Version: qemu-kvm-1.5.3-60.el7_0.12
Doc Type: Bug Fix
Doc Text:
Clone Of: 1162080
Environment:
Last Closed: 2015-03-09 08:58:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.