Bug 999789
Summary: | qemu should give a more friendly prompt when didn't specify read-only for VMDK format disk | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | 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: | 7.0 | CC: | bsarathy, chayang, famz, flang, hhuang, jcody, juzhang, michen, mkenneth, mrezanin, qzhang, rbalakri, sluo, stefanha, virt-maint, xfu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-1.5.3-67.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 999788 | Environment: | |
Last Closed: | 2015-03-05 08:01:22 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: | 999788 | ||
Bug Blocks: |
Comment 1
Sibiao Luo
2013-08-22 06:56:03 UTC
Part with mentioned error was rewritten, can you please retest the bz and test the error message state? (In reply to Miroslav Rezanina from comment #2) > Part with mentioned error was rewritten, can you please retest the bz and > test the error message state? Retried it with the latest qemu-kvm version that it will give a message prompt "vmdk: Operation not supported". But still not as expected, you should refer to bug 999788#c7 that should give message prompt like: vmdk' can be only used as read-only device. host info: 3.10.0-41.el7.x86_64 qemu-kvm-1.5.3-13.el7.x86_64 e.g:...-drive file=/home/vmdk-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 -vnc :1 -monitor stdio qemu-kvm: -drive file=/home/vmdk-data-disk.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop: could not open disk image /home/vmdk-data-disk.vmdk: Operation not supported Best Regards, sluo Upstream 2.0 has the following message: qemu-system-x86_64: -drive file=/stor/image/turnkey-moinmoin-12.0-squeeze-x86.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop: could not open disk image /stor/image/turnkey-moinmoin-12.0-squeeze-x86.vmdk: Driver 'vmdk' can only be used for read-only devices Moving to POST and waiting for rebase. Fix included in qemu-kvm-1.5.3-67.el7 Verify this issue on qemu-kvm-rhev-2.1.2-5.el7.x86_64 and qemu-kvm-1.5.3-75.el7.x86_64. host info: # uname -r && rpm -q qemu-kvm-rhev 3.10.0-191.el7.x86_64 qemu-kvm-rhev-2.1.2-5.el7.x86_64 e.g:...-drive file=/home/vmdk-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 Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. qemu-kvm: -drive file=/home/vmdk-data-disk.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop: could not open disk image /home/vmdk-data-disk.vmdk: Driver 'vmdk' can only be used for read-only devices ################################################### host info: # uname -r && rpm -q qemu-kvm 3.10.0-191.el7.x86_64 qemu-kvm-1.5.3-75.el7.x86_64 e.g:...-drive file=/home/vmdk-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 Warning: option deprecated, use lost_tick_policy property of kvm-pit instead. qemu-kvm: -drive file=/home/vmdk-data-disk.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop: could not open disk image /home/vmdk-data-disk.vmdk: Driver 'vmdk' can only be used for read-only devices 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. https://rhn.redhat.com/errata/RHSA-2015-0349.html |