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 1024335 - Manpage doesn't document -drive rerror/werror/readonly
Summary: Manpage doesn't document -drive rerror/werror/readonly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Kevin Wolf
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1090362
TreeView+ depends on / blocked
 
Reported: 2013-10-29 12:30 UTC by Kevin Wolf
Modified: 2014-10-14 06:53 UTC (History)
11 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.420.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1090362 (view as bug list)
Environment:
Last Closed: 2014-10-14 06:53:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1490 0 normal SHIPPED_LIVE qemu-kvm bug fix and enhancement update 2014-10-14 01:28:27 UTC

Description Kevin Wolf 2013-10-29 12:30:07 UTC
The qemu manpage in RHEL 6 doesn't document the rerror/werror/readonly options
for -drive, even though these options are implemented. They should be added to
the manpage.

Comment 1 Miroslav Rezanina 2014-01-27 07:51:03 UTC
Fix included in qemu-kvm-0.12.1.2-2.420.el6

Comment 3 Chao Yang 2014-07-01 05:54:21 UTC
Steps to reproduce and verify this issue:
1. dump output of man qemu-kvm for fixed qemu-kvm and unfixed qemu-kvm
2. run diff on them

Tested with qemu-kvm-0.12.1.2-2.428.el6.x86_64 and qemu-kvm-0.12.1.2-2.415.el6.x86_64. Actual result is as below:

# diff -up qemu-kvm-man-old qemu-kvm-man
--- qemu-kvm-man-old	2014-07-01 13:49:01.385203252 +0800
+++ qemu-kvm-man	2014-07-01 13:43:02.638202102 +0800
@@ -168,6 +168,17 @@ OPTIONS
 	   addr=addr
 	       Specify the controller’s PCI address (if=virtio only).
 
+	   werror=action,rerror=action
+	       Specify which action to take on write and read errors. Valid
+	       actions are: "ignore" (ignore the error and try to continue),
+	       "stop" (pause QEMU), "report" (report the error to the guest),
+	       "enospc" (pause QEMU only if the host disk is full; report the
+	       error to the guest otherwise).  The default setting is
+	       werror=enospc and rerror=report.
+
+	   readonly
+	       Open drive file as read-only. Guest write attempts will fail.
+


As per above, this issue has been fixed.

Comment 4 errata-xmlrpc 2014-10-14 06:53:54 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.

http://rhn.redhat.com/errata/RHBA-2014-1490.html


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