Bug 701580 - Guests shouldn't boot up successfully when wrong parameters are set
Summary: Guests shouldn't boot up successfully when wrong parameters are set
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-03 09:27 UTC by Min Deng
Modified: 2011-05-17 17:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-17 17:28:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


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