Hide Forgot
Description Typo in virt-install manual on RHEL6, should use "an"instead of "and" in format option description. Version: # rpm -qa python-virtinst libvirt python-virtinst-0.600.0-18.el6.noarch libvirt-0.10.2-29.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. #man virt-install format ... With libvirt 0.8.3 and later, this option should be specified if reusing and existing disk image, since libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image. 2. Check the virt-install manual on rhel7 # rpm -qa libvirt virt-manager libvirt-1.1.1-10.el7.x86_64 virt-manager-0.10.0-4.el7.noarch #man virt-install format ... With libvirt 0.8.3 and later, this option should be specified if reusing an existing disk image, since libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image. Actual results: Typo of "reusing and existing disk image" is listed in virt-install manual on RHEL6, not on RHEL7. Expected results: List "reusing an existing disk image" in virt-install manual on RHEL6. Additional info:
Reproduce with python-virtinst-0.600.0-18.el6.noarch. Verified with package: python-virtinst-0.600.0-20.el6.noarch steps: # man virt-install format ... With libvirt 0.8.3 and later, this option should be specified if reusing an existing disk image, since libvirt does not autodetect storage format as it is a potential security issue. For example, if reusing an existing qcow2 image, you will want to specify format=qcow2, otherwise the hypervisor may not be able to read your disk image. No typo of "reusing and existing disk image" showed,so move to verified.
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-1444.html