Re: [libvirt] [PATCH 2/2] util: introduce virSocketAddrParseAny

2018-04-05 Thread Jim Fehlig
On 04/05/2018 02:55 PM, Jim Fehlig wrote: On 03/29/2018 11:27 AM, John Ferlan wrote: On 03/26/2018 04:29 PM, Jim Fehlig wrote: When preparing for migration, the libxl driver creates a new TCP listen socket for the incoming migration by calling virNetSocketNewListenTCP, passing the

Re: [libvirt] [PATCH 2/2] util: introduce virSocketAddrParseAny

2018-04-05 Thread Jim Fehlig
On 03/29/2018 11:27 AM, John Ferlan wrote: On 03/26/2018 04:29 PM, Jim Fehlig wrote: When preparing for migration, the libxl driver creates a new TCP listen socket for the incoming migration by calling virNetSocketNewListenTCP, passing the destination host name. virNetSocketNewListenTCP calls

Re: [libvirt] [PATCH 2/2] util: introduce virSocketAddrParseAny

2018-03-29 Thread John Ferlan
On 03/26/2018 04:29 PM, Jim Fehlig wrote: > When preparing for migration, the libxl driver creates a new TCP listen > socket for the incoming migration by calling virNetSocketNewListenTCP, > passing the destination host name. virNetSocketNewListenTCP calls > virSocketAddrParse to check if the

[libvirt] [PATCH 2/2] util: introduce virSocketAddrParseAny

2018-03-26 Thread Jim Fehlig
When preparing for migration, the libxl driver creates a new TCP listen socket for the incoming migration by calling virNetSocketNewListenTCP, passing the destination host name. virNetSocketNewListenTCP calls virSocketAddrParse to check if the host name is a wildcard address, in which case it