Bug 991377 - boot guest with maxcpu=255 successfully but actually max number of vcpu is 160
boot guest with maxcpu=255 successfully but actually max number of vcpu is 160
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm (Show other bugs)
6.5
Unspecified Unspecified
low Severity low
: rc
: ---
Assigned To: Virtualization Maintenance
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-02 05:36 EDT by Chao Yang
Modified: 2013-08-12 15:11 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 996258 (view as bug list)
Environment:
Last Closed: 2013-08-12 15:11:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chao Yang 2013-08-02 05:36:56 EDT
Description of problem:
Booted a guest with "-smp 8,sockets=2,cores=2,threads=2,maxcpus=256", qeumu-kvm quit with "Unsupported number of maxcpus".
But while adjusted maxcpus to 255, guest booted up successfully. It misleads users into believing the maxcpu we support in rhel 6 is 255, actually it is 160 instead.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.382.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Marcelo Tosatti 2013-08-12 15:11:58 EDT
Bug does not meet RHEL6.x inclusion criteria:
opened BZ 996258 as a clone for RHEL7.

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