Bug 987725
Summary: | Guest should failed to be booted if specifying iops,bps as negative value | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Sibiao Luo <sluo> |
Component: | qemu-kvm | Assignee: | Fam Zheng <famz> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | acathrow, armbru, bsarathy, hhuang, juzhang, knoel, michen, minovotn, mkenneth, qzhang, sluo, svenkatr, virt-maint |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-rhev-0.12.1.2-2.398.el6 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | 890024 | Environment: | |
Last Closed: | 2013-11-22 00:39:12 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: | |
Embargoed: | |||
Bug Depends On: | 890024 | ||
Bug Blocks: |
Comment 1
Sibiao Luo
2013-07-24 02:19:34 UTC
Verify this issue on qemu-kvm-rhev-0.12.1.2-2.398.el6.x86_64. host info: # uname -r && rpm -q qemu-kvm-rhev 2.6.32-413.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.398.el6.x86_64 guest info: kernel-2.6.32-413.el6.x86_64 # /usr/libexec/qemu-kvm...-drive file=/home/RHEL6.5-20130814.n.0-6.5-Server.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial="QEMU-DISK1",bps=-1024000,iops=-100... qemu-kvm: -drive file=/home/RHEL6.5-20130814.n.0-6.5-Server.qcow2,if=none,id=drive-system-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop,serial=QEMU-DISK1,bps=-1024000,iops=-100: bps and iops values must be 0 or greater It fail to boot guest with specifying iops,bps as negative value, and qemu will quit with a friendly message reminds. Base on above, this issue has been fixed correctly, Move to verified status, please correct me if any problem. Best Regards, sluo 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. http://rhn.redhat.com/errata/RHSA-2013-1754.html |