Bug 1378731 - Can boot guest successfully inside qemu if maxcpus don't match topology in -smp
Summary: Can boot guest successfully inside qemu if maxcpus don't match topology in -smp
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.3
Hardware: x86_64
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Guo, Zhiyi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 08:39 UTC by Guo, Zhiyi
Modified: 2017-10-05 21:13 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-05 21:12:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Guo, Zhiyi 2016-09-23 08:39:09 UTC 
Description of problem:
Can boot guest successfully inside qemu if maxcpus don't match topology in -smp

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-126.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Launch qemu with /usr/libexec/qemu-kvm -smp 8,maxcups=4
2.
3.

Actual results:
qemu can lauch successfully

Expected results:
qemu should report error

Additional info:
As we have such cases in both qemu-kvm/qemu-kvm-rhev test, maybe it's better to make basic case has same behavior in both qemu-kvm & qemu-kvm-rhev
Note You need to log in before you can comment on or make changes to this bug.