Bug 999788
Summary: | qemu should give a more friendly prompt when didn't specify read-only for VMDK format disk | |||
---|---|---|---|---|
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, bsarathy, chayang, famz, flang, juzhang, michen, mkenneth, qzhang, stefanha, tlavigne, virt-maint, xfu | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | qemu-kvm-0.12.1.2-2.409.el6 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 999789 (view as bug list) | Environment: | ||
Last Closed: | 2013-11-21 07:12:07 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: | ||||
Bug Blocks: | 999789 |
Description
Sibiao Luo
2013-08-22 06:51:37 UTC
Verified this issue on qemu-kvm-0.12.1.2-2.410.el6.x86_64 with the same steps as comment #0. host info: # uname -r && rpm -q qemu-kvm 2.6.32-420.el6.x86_64 qemu-kvm-0.12.1.2-2.410.el6.x86_64 e.g:...-drive file=/mnt/my-data-disk.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,bus=pci.0,addr=0x7,drive=drive-data-disk,id=data-disk qemu-kvm: -drive file=/mnt/my-data-disk.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop: 'vmdk' can be only used as read-only device. /etc/qemu-ifdown: could not launch network script Results: after step 2, QEMU will quit and give a more friendly prompt message for users, like: "'vmdk' can be only used as read-only device". Base on above, this issue has been fixed correctly, move to VERIFIED status, please correct me if any mistake. 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-1553.html |