Bug 1378731

Summary:	Can boot guest successfully inside qemu if maxcpus don't match topology in -smp
Product:	Red Hat Enterprise Linux 7	Reporter:	Guo, Zhiyi <zhguo>
Component:	qemu-kvm	Assignee:	Eduardo Habkost <ehabkost>
Status:	CLOSED DEFERRED	QA Contact:	Guo, Zhiyi <zhguo>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	ailan, chayang, jinzhao, juzhang, knoel, michen, ngu, rbalakri, virt-maint, xfu, zhguo
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-05 21:12:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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