Bug 1129975 - The online cpu number is not equal to vcpu number which is specified in guest's configure file when create windows guest
Summary: The online cpu number is not equal to vcpu number which is specified in guest...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen
Version: 5.11
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-14 06:14 UTC by Lingfei Kong
Modified: 2017-04-18 21:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-18 21:58:38 UTC


Attachments (Terms of Use)

Description Lingfei Kong 2014-08-14 06:14:00 UTC
Description of problem:
When create windows guest on intel or amd host, the online cpu number is not equal to vcpu number which is specified in guest's configure file, this problem do not happen on all type of windows guest.
I check this with Win7, Win2008, Win2008r2, WinXP, WinVista, Win2012r2, Win2003 on Intel and AMD host, here are the test results(create guest with vcpus=4)
                                                        AMD Host                                                          Intel Host
WIn7                                       4 vcpus online                                                    1 vcpus online
WinXP                                    2 vcpus online                                                    2 vcpus online
Win2008                                 4 vcpus online                                                    4 vcpus online
Win2008r2                             4 vcpus online                                                    4 vcpus online
WinVista                                 4 vcpus online                                                    2 vcpus online
Win2-12r2                              4 vcpus online                                                    4 vcpus online
Win2003                                 1 vcpus online                                                    1 vcpus online

As rhel5.11 is the last rhel5 release and now at the end of  rhel5.11 release, also this bug is not a critical or regression bug, so it maybe not worth fixing it, just file it for documented purpose. 


Version-Release number of selected component (if applicable):
Guest: Win7
kernel-xen-2.6.18-398.el5
xen-3.0.3-144.el5

How reproducible:
100%

Steps to Reproduce:
1. Install rhel5.11 xen host on Intel or AMD machine
2. Create Windows guest with vcpus=4, take Win7 for example:
#xm cr hvm-win7-64-1.cfg vcpus=4
3. After the guest is completely startup, check the vcpu list:
#xm vcpu-list 7
Name                              ID VCPUs   CPU State   Time(s) CPU Affinity
hvm-win7-64-1                      7     0     0   -b-      29.9 any cpu
hvm-win7-64-1                      7     1     -   --p       0.0 any cpu
hvm-win7-64-1                      7     2     -   --p       0.0 any cpu
hvm-win7-64-1                      7     3     -   --p       0.0 any cpu

4. Check active vcpu number in windows guest:
"Start Task Manager" -> "Performance" -> Double click "CPU Usage"

Actual results:
Only one vcpu is online:
#xm vcpu-list 7
Name                              ID VCPUs   CPU State   Time(s) CPU Affinity
hvm-win7-64-1                      7     0     0   -b-      29.9 any cpu
hvm-win7-64-1                      7     1     -   --p       0.0 any cpu
hvm-win7-64-1                      7     2     -   --p       0.0 any cpu
hvm-win7-64-1                      7     3     -   --p       0.0 any cpu

Only one active cpu when check in windows guest

Expected results:
All the vcpus should be online, i.e. no '--p' and there are 4 active vcpus in windows guest

Additional info:
I can see all the vcpus in guest's 'Device Manager'

Comment 2 Chris Williams 2017-04-18 21:58:38 UTC
Red Hat Enterprise Linux 5 shipped it's last minor release, 5.11, on September 14th, 2014. On March 31st, 2017 RHEL 5 exited Production Phase 3 and entered Extended Life Phase. For RHEL releases in the Extended Life Phase, Red Hat  will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only.  If the customer purchases the Extended Life-cycle Support (ELS), certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release will be provided.  For more details please consult the Red Hat Enterprise Linux Life Cycle Page:
https://access.redhat.com/support/policy/updates/errata

This BZ does not appear to meet ELS criteria so is being closed WONTFIX. If this BZ is critical for your environment and you have an Extended Life-cycle Support Add-on entitlement, please open a case in the Red Hat Customer Portal, https://access.redhat.com ,provide a thorough business justification and ask that the BZ be re-opened for consideration of an errata. Please note, only certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release can be considered.


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