Re: [libvirt] virNetSocketNewListenTCP tries just one address

2018-04-15 Thread Olaf Hering
On Wed, Mar 28, Olaf Hering wrote: > > How can libvirt tell whether this is a misconfiguration of DNS or host's > > interfaces? > By simply cycling through the 'runp' list to see if any bind() succeeds? This change fixes /etc/sysconfig/network/ifcfg-br0:BOOTPROTO='dhcp4' for me. Just keep going

Re: [libvirt] virNetSocketNewListenTCP tries just one address

2018-03-28 Thread Olaf Hering
On Tue, Mar 27, Ján Tomko wrote: > It cannot, but the admin of the network should be able to control both. The admin must not control my (test) host, nor must I control the DNS server in the network. But there are likely cases where the admin for DNS and libvirtd is the same person. > How can

Re: [libvirt] virNetSocketNewListenTCP tries just one address

2018-03-27 Thread Ján Tomko
On Tue, Mar 27, 2018 at 11:18:10AM +0200, Olaf Hering wrote: On Tue, Mar 27, Ján Tomko wrote: Why does your hostname resolve to an unavailable address? How can the DNS server possibly know how a host has configured itself? It cannot, but the admin of the network should be able to control

Re: [libvirt] virNetSocketNewListenTCP tries just one address

2018-03-27 Thread Olaf Hering
On Tue, Mar 27, Ján Tomko wrote: > Why does your hostname resolve to an unavailable address? How can the DNS server possibly know how a host has configured itself? In this case I had BOOTPROTO='dhcp4' instead of 'dhcp' in /etc/sysconfig/network/ifcfg-br0 due to all the migration issues I'm

Re: [libvirt] virNetSocketNewListenTCP tries just one address

2018-03-27 Thread Ján Tomko
On Tue, Mar 27, 2018 at 09:57:13AM +0200, Olaf Hering wrote: To rescue this bug from the noise in a subthread: If a hostname resolves to more than one address and the host currently configured itself for just IPv4, doing a bind() to some IPv6 address will fail. As a result an error is returned

Re: [libvirt] virNetSocketNewListenTCP tries just one address

2018-03-27 Thread Daniel P . Berrangé
On Tue, Mar 27, 2018 at 09:57:13AM +0200, Olaf Hering wrote: > To rescue this bug from the noise in a subthread: > > If a hostname resolves to more than one address and the host currently > configured itself for just IPv4, doing a bind() to some IPv6 address > will fail. As a result an error is

[libvirt] virNetSocketNewListenTCP tries just one address

2018-03-27 Thread Olaf Hering
To rescue this bug from the noise in a subthread: If a hostname resolves to more than one address and the host currently configured itself for just IPv4, doing a bind() to some IPv6 address will fail. As a result an error is returned instead of continuing with the next item in 'runp'. > Mär 20