Bug 503712 - libvirtd does not listen by default to IPv6
Summary: libvirtd does not listen by default to IPv6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-02 11:28 UTC by Bernie Innocenti
Modified: 2010-03-16 17:20 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-26 15:15:23 UTC
Embargoed:

Attachments (Terms of Use)

Description Bernie Innocenti 2009-06-02 11:28:20 UTC 
Description of problem:
In order to get libvirtd to listen on IPv6, you have to manually
set 'listen_addr = "::"' in /etc/libvirt/libvirtd.conf.  By default,
it listens only on 0.0.0.0 (IPv4).

Version-Release number of selected component (if applicable):
libvirt-0.6.2-11.fc11.x86_64

How reproducible:
always

Steps to Reproduce:
netstat -A inet6 -lnp | grep libvirtd
  
Actual results:
no output

Expected results:
tcp        0      0 :::16509                    :::*                        LISTEN      23321/libvirtd      
tcp        0      0 :::16514                    :::*                        LISTEN      23321/libvirtd      


Additional info:
Comment 1 Daniel Berrangé 2009-06-02 11:52:58 UTC 
Looks like getaddrinfo() is returning the IPv4 address before the IPv6 address, and since Linux defaults to net.ipv6.bindv6only=0, when libvirtd tries to listen on the IPv6 address  it fails with EADDRINUSE.  I really don't know why it isn't returning the IPv6 address first during the lookup.
Comment 2 Daniel Berrangé 2009-06-02 12:00:33 UTC 
Data point: Works correctly on RHEL-5. Fails on Fedora 9 & 11
Comment 3 Daniel Berrangé 2009-11-13 11:20:36 UTC 
Fix pushed upstream

http://www.redhat.com/archives/libvir-list/2009-November/msg00386.html
Comment 4 Daniel Berrangé 2009-11-26 15:15:23 UTC 
Fixed in 0.7.4 release
Note You need to log in before you can comment on or make changes to this bug.