Hide Forgot
Description of problem: As virt-install man page described, using 'bind_port' with udp serial, but failure was occurred. --serial udp,host=CONNECT_HOST:PORT,bind_port=BIND_HOST:BIND_PORT Version-Release number of selected component (if applicable): libvirt-0.8.7-13.el6.x86_64 python-virtinst-0.500.5-2.el6.noarch How reproducible: Always Steps to Reproduce: # virt-install -n test1 -r 512 -f /var/lib/libvirt/images/test1.img -s 6 -c /var/lib/libvirt/boot/Fedora-14-i686-Live-Desktop.iso --vnc --serial udp,host=127.0.0.1:4555,bind_port=127.0.0.1:4556 Actual results: ERROR Error in serial device parameters: Unknown options ['bind_port'] Expected results: no error. Additional info:
The man page was just wrong in this case, the correct parameter name is 'bind_host'. I've fixed the docs upstream: http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=4b53899460e04dcc64fde40cb2fec7791fdd9b90
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Deferring to 6.2
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: # virt-install -n demo -r 512 -f /var/lib/libvirt/images/demo.img -s 5 -c /dev/cdrom --vnc --serial udp,host=127.0.0.1:4555,bind_port=127.0.0.1:4556 Actual results: ERROR Error in serial device parameters: Unknown options ['bind_port'] Expected results: no error.
Regenerated man pages in python-virtinst-0.600.0-2.el6
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: # virt-install -n test -r 512 -f /var/lib/libvirt/images/test.img -s 5 -c /dev/cdrom --vnc --serial udp,host=127.0.0.1:4555,bind_port=127.0.0.1:4556 Starting install... Allocating 'test.img' | 5.0 GB 00:00 Creating domain... | 0 B 00:00 Guest installation complete... restarting guest ... # virsh dumpxml test ... <serial type='udp'> <source mode='bind' host='127.0.0.1' service='4556'/> <source mode='connect' host='127.0.0.1' service='4555'/> <target port='0'/> <alias name='serial0'/> </serial> ...
(In reply to comment #8) > 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: > # virt-install -n test -r 512 -f /var/lib/libvirt/images/test.img -s 5 -c > /dev/cdrom --vnc --serial udp,host=127.0.0.1:4555,bind_port=127.0.0.1:4556 Sorry, i have copied the wrong command. The correct is as shown belown: # virt-install -n test -r 512 -f /var/lib/libvirt/images/test.img -s 5 -c /dev/cdrom --vnc --serial udp,host=127.0.0.1:4555,bind_host=127.0.0.1:4556 and we could see the following content in the man page: #man virt-install ... --serial udp,host=CONNECT_HOST:PORT,bind_host=BIND_HOST:BIND_PORT ... > Starting install... > Allocating 'test.img' | 5.0 GB 00:00 > Creating domain... | 0 B 00:00 > Guest installation complete... restarting guest > ... > # virsh dumpxml test > ... > <serial type='udp'> > <source mode='bind' host='127.0.0.1' service='4556'/> > <source mode='connect' host='127.0.0.1' service='4555'/> > <target port='0'/> > <alias name='serial0'/> > </serial> > ...
According to comment 9, move the status 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