| Summary: | Guest should failed to boot if set iops,bps to negative number | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Qianqian Zhu <qizhu> |
| Component: | qemu-kvm | Assignee: | Fam Zheng <famz> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.8 | CC: | ailan, chayang, jen, mkenneth, qizhu, rbalakri, salmy, virt-maint |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | qemu-kvm-0.12.1.2-2.486.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-10 21:02:21 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
Qianqian Zhu
2015-12-29 10:11:28 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. (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. Fix included in qemu-kvm-0.12.1.2-2.486.el6 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] 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 |