Hide Forgot
+++ This bug was initially created as a clone of Bug #1419898 +++ +++ This bug was initially created as a clone of Bug #1419897 +++ Description of problem: qemu-info.html section "3.5.1 Commands" documents __com.redhat_screendump instead of __com.redhat_qxl_screendump Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. View usr/share/doc/qemu-kvm-0.12.1.2/qemu-doc.html 2. Search for _screendump 3. Actual results: Search finds ‘__com.redhat_screendump id filename’ Save screen from qxl device id into PPM image filename. Expected results: Should instead find ‘__com.redhat_qxl_screendump id filename’ Save screen from qxl device id into PPM image filename. Additional info: The typo is in qemu-monitor.hx. --- Additional comment from Markus Armbruster on 2017-02-07 06:09:59 EST --- The typo has moved from qemu-monitor.hx to in hmp-commands.hx.
Another doc bug: ‘__com.redhat_drive_add’ Create a drive similar to -device if=none. This should be "similar to -drive if=none".
Fix included in qemu-kvm-rhev-2.8.0-4.el7
$ git diff qemu-kvm-rhev-2.6.0-28.el7_3.9/usr/share/doc/qemu-kvm/qemu-doc.html qemu-kvm-rhev-2.9.0-2.el7/usr/share/doc/qemu-kvm/qemu-doc.html -<dt><samp>__com.redhat_screendump <var>id</var> <var>filename</var></samp></dt> -<dd><a name="index-_005f_005fcom_002eredhat_005fscreendump"></a> +<dt><samp>__com.redhat_qxl_screendump <var>id</var> <var>filename</var></samp></dt> +<dd><a name="index-_005f_005fcom_002eredhat_005fqxl_005fscreendump"></a> <dt><samp>__com.redhat_drive_add</samp></dt> <dd><a name="index-_005f_005fcom_002eredhat_005fdrive_005fadd"></a> -<p>Create a drive similar to -device if=none. -</p></dd> -<dt><samp>pci_del</samp></dt> -<dd><a name="index-pci_005fdel"></a> -<p>Hot remove PCI device. +<p>Create a drive similar to -drive if=none. </p></dd> <dt><samp>pcie_aer_inject_error</samp></dt> <dd><a name="index-pcie_005faer_005finject_005ferror"></a> Setting VERIFIED per above.
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://access.redhat.com/errata/RHSA-2017:2392