Bug 689721

Summary: virt-install: default HOST value is blank in guest XML desc when set HOST value with none
Product: Red Hat Enterprise Linux 6 Reporter: Nan Zhang <nzhang>
Component: python-virtinstAssignee: Cole Robinson <crobinso>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dyuan, hjiang, llim
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
No description necessary
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 16:16:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nan Zhang 2011-03-22 09:33:38 UTC
Description of problem:
As the virt-install usage described, default HOST value is ’127.0.0.1’ if no HOST value specified. But I found the host value is blank in guest XML description after install.

--serial tcp,host=HOST:PORT,mode=MODE,protocol=PROTOCOL

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 --disk path=/var/lib/libvirt/images/test1.img,size=6,io=threads -c /var/lib/libvirt/boot/Fedora-14-i686-Live-Desktop.iso --vnc --serial tcp,host=:2222,mode=bind

# virsh dumpxml test1
  
Actual results:
    <serial type='tcp'>
      <source mode='bind' host='' service='2222'/>
      <protocol type='raw'/>
      <target port='0'/>
      <alias name='serial0'/>
    </serial>

Expected results:
    <serial type='tcp'>
      <source mode='bind' host='127.0.0.1' service='2222'/>
      <protocol type='raw'/>
      <target port='0'/>
      <alias name='serial0'/>
    </serial>

Additional info:

Comment 1 Cole Robinson 2011-03-22 19:08:27 UTC
Thanks for the report, fixed upstream:

http://git.fedorahosted.org/git?p=python-virtinst.git;a=commit;h=c29adac71e545b8b6eb1ac9c0662bd1b22e3803b

Comment 2 RHEL Program Management 2011-04-04 01:48:05 UTC
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.

Comment 3 Cole Robinson 2011-04-07 15:35:44 UTC
Since I don't think this is a regression and not commonly used functionality, moving to 6.2

Comment 4 RHEL Program Management 2011-04-07 15:43:48 UTC
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.

Comment 5 Cole Robinson 2011-07-28 15:34:10 UTC
Fixed in python-virtinst-0.600.0-1.el6

Comment 7 Huming Jiang 2011-08-02 08:32:34 UTC
Verified on the following components;
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

Steps:
# virt-install -n test1 -r 512 --disk path=/var/lib/libvirt/images/test1.img,size=6,io=threads -c /dev/cdrom --vnc --serial tcp,host=:2222,mode=bind

# virsh dumpxml test1
...
    <serial type='tcp'>
      <source mode='bind' host='127.0.0.1' service='2222'/>
      <protocol type='raw'/>
      <target port='0'/>
      <alias name='serial0'/>
    </serial>
...

Comment 8 Cole Robinson 2011-11-07 16:50:51 UTC
    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

Comment 9 errata-xmlrpc 2011-12-06 16:16:04 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-2011-1643.html