RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1294619 - Guest should failed to boot if set iops,bps to negative number
Summary: Guest should failed to boot if set iops,bps to negative number
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.8
Hardware: x86_64
OS: All
high
high
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-29 10:11 UTC by Qianqian Zhu
Modified: 2016-05-10 21:02 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.486.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 21:02:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0815 0 normal SHIPPED_LIVE qemu-kvm bug fix and enhancement update 2016-05-10 22:39:31 UTC

Description Qianqian Zhu 2015-12-29 10:11:28 UTC 
Description of problem:
Guest should failed to boot if set iops,bps to negative number

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-0.12.1.2-2.482.el6.x86_64
kernel-2.6.32-590.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Launch guest with:
/usr/libexec/qemu-kvm -name virtio -m 1024 -cpu Westmere,check -realtime mlock=off -smp 2 -global PIIX4_PM.disable_s4=1 -global PIIX4_PM.disable_s3=1 -boot order=c,menu=on -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x6 -drive file=/nfs/rhel6.7_virtio.qcow2,format=qcow2,if=none,id=block-virtio,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x8,drive=block-virtio,id=block-virtio,bootindex=1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -monitor stdio -vnc :4 -vga cirrus -drive file=/nfs/test20G.qcow2,if=none,cache=none,id=drive-ide0-1-0,format=qcow2,iops=-1,bps=-1
2.
3.

Actual results:
qemu launched successfully and no error prompt.
(qemu) info block
block-virtio: removable=0 io-status=ok file=/nfs/rhel6.7_virtio.qcow2 ro=0 drv=qcow2 encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
drive-ide0-1-0: removable=1 locked=0 tray-open=0 file=/nfs/test20G.qcow2 ro=0 drv=qcow2 encrypted=0 bps=-9223372036854775808 bps_rd=0 bps_wr=0 iops=-9223372036854775808 iops_rd=0 iops_wr=0


Expected results:
qemu prompt error like "bps and iops values must be 0 or greater" and then quit.

Additional info:
Tried same scenario with qemu-kvm-rhev-0.12.1.2-2.448.el6_6.3.x86_64, got expected prompt：
qemu-kvm: -drive file=/nfs/test20G.qcow2,if=none,cache=none,id=drive-ide0-1-0,format=qcow2,iops=-1,bps=-1: bps and iops values must be 0 or greater

Reproduced with qemu-kvm-rhev-0.12.1.2-2.477.el6.x86_64
Comment 5 Fam Zheng 2016-01-11 05:45:05 UTC 
RHEL 7.2 is okay, but not RHEV 7.2 (qemu-kvm-rhev). Please test that and clone this bug to qemu-kvm-rhev 7.3 if it's the case.
Comment 6 Qianqian Zhu 2016-01-11 09:21:35 UTC 
(In reply to Fam Zheng from comment #5)
> RHEL 7.2 is okay, but not RHEV 7.2 (qemu-kvm-rhev). Please test that and
> clone this bug to qemu-kvm-rhev 7.3 if it's the case.

Created Bug 1297334.
Comment 9 Jeff Nelson 2016-01-25 21:39:22 UTC 
Fix included in qemu-kvm-0.12.1.2-2.486.el6
Comment 12 Qianqian Zhu 2016-02-14 06:13:31 UTC 
Verified with:
qemu-kvm-rhev-0.12.1.2-2.486.el6.x86_64
kernel-2.6.32-584.el6.x86_64

Steps:
1.Launch guest with:
/usr/libexec/qemu-kvm -drive file=/mnt/RHEL-Server-6.7-64-virtio.qcow2,if=none,cache=none,id=drive-ide0-1-0,format=qcow2,iops=-1,bps=-1

Result:
qemu prompts proper info and quit:
qemu-kvm: -drive file=/mnt/RHEL-Server-6.7-64-virtio.qcow2,if=none,cache=none,id=drive-ide0-1-0,format=qcow2,iops=-1,bps=-1: bps/iops/max values must be within [0, 1000000000000000]
Comment 15 errata-xmlrpc 2016-05-10 21:02:21 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0815.html
Note You need to log in before you can comment on or make changes to this bug.