This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 601494 - qemu-io: No permission to write image
qemu-io: No permission to write image
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Kevin Wolf
Virtualization Bugs
: Regression
Depends On:
Blocks: Rhel5KvmTier2
  Show dependency treegraph
Reported: 2010-06-08 01:27 EDT by Amos Kong
Modified: 2015-05-24 20:05 EDT (History)
9 users (show)

See Also:
Fixed In Version: kvm-83-183.el5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-01-13 18:35:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description Amos Kong 2010-06-08 01:27:03 EDT
Description of problem:

I created a image and write it by qemu-io, touched a error msg "write failed: Permission denied".

# qemu-img create -f qcow2 test.qcow2 10G
Formatting 'test.qcow2', fmt=qcow2, size=10485760 kB
# ls -l test.qcow2 
-rw-r--r-- 1 root root 262144 Jun  8 12:49 test.qcow2
# qemu-io test.qcow2
qemu-io> write 0 2M -P 65
write failed: Permission denied

Version-Release number of selected component (if applicable):
host kernel: 2.6.18-200.el5
# rpm -qa |grep kvm
# rpm -qf /usr/bin/qemu-io

How reproducible:

Steps to Reproduce:
1.create a image
# qemu-img create -f qcow2 test.qcow2 10G
2.write it by qemu-io
# qemu-io test.qcow2
qemu-io> write 0 2M -P 65
Comment 1 Kevin Wolf 2010-06-11 06:48:54 EDT
Bisected to 69f1606d ("read-only: BDRV_O_FLAGS changes, default now is read-only").
Comment 7 Amos Kong 2010-09-17 00:54:59 EDT
Could not reproduce this bug with kvm-83-193.el5
Moving to VERIFIED
Comment 9 errata-xmlrpc 2011-01-13 18:35:56 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.