Bug 701580

Summary: Guests shouldn't boot up successfully when wrong parameters are set
Product: Red Hat Enterprise Linux 5 Reporter: Min Deng <mdeng>
Component: kvmAssignee: Virtualization Maintenance <virt-maint>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 5.7CC: bcao, gcosta, juzhang, michen, mkenneth, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-17 17:28:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Min Deng 2011-05-03 09:27:11 UTC 
Description of problem:
Guests shouldn't boot up successfully when wrong parameters are set
Version-Release number of selected component (if applicable):
Kernel&KVM
2.6.18-259.el5
kvm-83-232.el5
How reproducible:
According to KVM' help we can know -
-m megs set virtual RAM size to megs MB [default=128]
-smp n[,cores=cores][,threads=threads][,sockets=sockets]
 
Steps to Reproduce:
1.boot up guest with the following command -
  /usr/libexec/qemu-kvm -rtc-td-hack -usbdevice tablet -no-hpet -drive file=/home/5u7.raw,if=virtio,boot=on,werror=stop,cache=none,format=raw,media=disk -cpu qemu64,+sse4.2 -smp 4 -m 4G,sockets=2,cores=1,threads=2 -net nic,macaddr=00:12:24:57:a8:2e,model=virtio,vlan=0 -net tap,script=/etc/qemu-ifup,vlan=0 -uuid `uuidgen` -boot c -balloon none -notify all -spice port=8001,disable-ticketing -monitor stdio -qxl 1

  
Actual results:
Socket&Cores&threads parameters should follow '-smp 4' not '-m 4G',but the guest still can boot up without any warnings.

Expected results:
Warning is needed here.



Additional info:
Comment 1 Glauber Costa 2011-05-17 17:28:23 UTC 
We don't support directly launching of qemu. libvirt should always drive it.

So wrong passing of parameters is not a concern.