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 999789 - qemu should give a more friendly prompt when didn't specify read-only for VMDK format disk
Summary: qemu should give a more friendly prompt when didn't specify read-only for VMD...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 999788
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 06:52 UTC by Sibiao Luo
Modified: 2015-03-05 08:01 UTC (History)
16 users (show)

Fixed In Version: qemu-kvm-1.5.3-67.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 999788
Environment:
Last Closed: 2015-03-05 08:01:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0349 0 normal SHIPPED_LIVE Important: qemu-kvm security, bug fix, and enhancement update 2015-03-05 12:27:34 UTC

Comment 1 Sibiao Luo 2013-08-22 06:56:03 UTC 
host info:
# uname -r && rpm -q qemu-kvm
3.10.0-3.el7.x86_64
qemu-kvm-1.5.2-4.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
qemu-kvm: -drive file=/home/vmdk-data-disk.vmdk,if=none,id=drive-data-disk,format=vmdk,cache=none,werror=stop,rerror=stop: 'vmdk' invalid format
/etc/qemu-ifdown: could not launch network script
Comment 2 Miroslav Rezanina 2013-11-06 06:05:30 UTC 
Part with mentioned error was rewritten, can you please retest the bz and test the error message state?
Comment 3 Sibiao Luo 2013-11-06 07:08:20 UTC 
(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
Comment 4 Fam Zheng 2014-04-18 06:33:45 UTC 
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.
Comment 7 Jeff Nelson 2014-08-08 16:54:59 UTC 
Fix included in qemu-kvm-1.5.3-67.el7
Comment 9 Sibiao Luo 2014-10-31 05:11:00 UTC 
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
Comment 11 errata-xmlrpc 2015-03-05 08:01:22 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/RHSA-2015-0349.html
Note You need to log in before you can comment on or make changes to this bug.