Hide Forgot
Description of problem: MODE value should be 'bind' or 'connect', not 'tcp'. --serial unix,path=UNIXPATH,mode=MODE Unix socket (see unix(7). MODE has similar behavior and defaults as ’tcp’. Version-Release number of selected component (if applicable): python-virtinst-0.500.5-2.el6.noarch How reproducible: Always Steps to Reproduce: # man virt-install Actual results: Expected results: Additional info:
The man page is a little unclear, what it is saying is that --serial unix,mode= works exactly the same as --serial tcp,mode= I've clarified this upstream: http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=04d82eddfcf5e4cacd0c3fca06cb1f7512d841b3
Fixed in python-virtinst-0.600.0-1.el6
Could still reproduce this bug in the following componets: python-virtinst-0.600.0-1.el6. libvirt-0.9.4-0rc1.el6.x86_64 kernel-2.6.32-171.el6.x86_64 qemu-kvm-0.12.1.2-2.174.el6.x86_64 How reproducible: Always Steps to Reproduce: # man virt-install ... --serial unix,path=UNIXPATH,mode=MODE Unix socket, see unix(7). MODE has similar behavior and defaults as --serial tcp,mode=MODE ...
Regenerated man pages in python-virtinst-0.600.0-2.el6
I confired it with others, then found following is the final result. sorry about comment 5. Verified with the following components: libvirt-0.9.4-0rc1.2.el6.x86_64 kernel-2.6.32-171.el6.x86_64 python-virtinst-0.600.0-2.el6.noarch qemu-kvm-0.12.1.2-2.175.el6.x86_64 Steps: # man virt-install ... --serial unix,path=UNIXPATH,mode=MODE Unix socket, see unix(7). MODE has similar behavior and defaults as --serial tcp,mode=MODE ...
Thanks for confirming, should we put this bug into VERIFIED then? I think the other doc bugs need the same.
Move this to VERIFIED, according to comment 7.
Move the needinfo plag, according to comment 9. And set status of the other doc bugs from modified to verified.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
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-2011-1643.html