Bug 689761

Summary:	(null) in generated '-chardev udp' line if XML omits parameters
Product:	Red Hat Enterprise Linux 6	Reporter:	Nan Zhang <nzhang>
Component:	libvirt	Assignee:	Daniel Veillard <veillard>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	dallan, dyuan, eblake, llim, mzhan, ydu, zhpeng
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	libvirt-0.9.4-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 10:58:07 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 11:47:17 UTC

Description of problem:
As man page described, manually set the default HOST with ’127.0.0.1’ will cause error.

--serial udp,host=CONNECT_HOST: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:2222

Actual results:
Starting install...
ERROR    internal error process exited while connecting to monitor: getaddrinfo((null),(null)): Servname not supported for ai_socktype
inet_dgram_opts failed
chardev: opening backend "udp" failed

Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
  virsh --connect qemu:///system start test1
otherwise, please restart your installation.

Expected results:
no errors

Additional info:

Comment 1 Cole Robinson 2011-03-22 20:38:08 UTC

Looks like a libvirt bug actually. Patch sent upstream:

https://www.redhat.com/archives/libvir-list/2011-March/msg01038.html

Comment 2 RHEL Program Management 2011-04-04 02:05:54 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 Dave Allan 2011-06-10 03:23:49 UTC

DV, did this ever get committed?

Comment 4 Daniel Veillard 2011-08-10 07:17:46 UTC

No and we are still having the problem.
I changed the patch to address the comments, and posted the new version:

https://www.redhat.com/archives/libvir-list/2011-August/msg00335.html

Daniel

Comment 5 Daniel Veillard 2011-08-11 10:16:00 UTC

upstream commit d30d5726507fd59a87127eb22075cfcb4482f9df

Daniel

Comment 7 zhpeng 2011-08-17 10:45:11 UTC

Hi,
I have reproduced the bug with :
libvirt-0.8.7-14.el6.x86_64
python-virtinst-0.500.5-3.el6.noarch

And i have verified on the latest version on:
python-virtinst-0.600.0-2.el6.noarch
libvirt-0.9.4-4.el6.x86_64

The steps are as follows:

1, download the iso # cd /var/lib/libvirt/boot # wget http://download.englab.nay.redhat.com/pub/fedora/linux/releases/14/Live/i686/Fedora-14-i686-Live-Desktop.iso
2, create a domain, and vnc-viewer popup, and the guest machine boot from fedora iso. 
# 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:2222

Starting install...
Allocating 'test1.img' | 6.0 GB 00:00
Creating domain... | 0 B 00:00

3, close the vnc-viewer, Terminal shows:
Domain installation still in progress. You can reconnect to
the console to complete the installation process.

And now it's expected results. The test is pass.

Comment 8 dyuan 2011-08-17 11:00:48 UTC

Moved it to VERIFIED according to comment 7.

Comment 9 errata-xmlrpc 2011-12-06 10:58:07 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-1513.html