On Mon, Mar 19, Jim Fehlig wrote:
While working on the {Begin,End}API improvements I noticed a few problems in the migration code. The first two are trival, but the third describes a problem I encountered while testing, and provides a potential fix. See the patch for more details.
I tried these changes with master. Without them the receiving side reports this: Mär 20 08:53:06 macintyre-old libvirtd[1275]: 2018-03-20 07:53:06.161+0000: 1317: error : virSocketAddrParseInternal:121 : Cannot parse socket address 'macintyre-old.arch.suse.de': Name or service not known Mär 20 08:53:06 macintyre-old libvirtd[1275]: 2018-03-20 07:53:06.162+0000: 1317: error : virNetSocketNewListenTCP:389 : Unable to bind to port: Cannot assign requested address Mär 20 08:53:06 macintyre-old libvirtd[1275]: 2018-03-20 07:53:06.162+0000: 1317: error : libxlDomainMigrationPrepare:759 : operation failed: Fail to create socket for incoming migration With them just the parse error disappeared: Mär 20 09:35:52 macintyre-old libvirtd[4527]: 2018-03-20 08:35:52.521+0000: 4531: error : virNetSocketNewListenTCP:389 : Unable to bind to port: Cannot assign requested address Mär 20 09:35:52 macintyre-old libvirtd[4527]: 2018-03-20 08:35:52.521+0000: 4531: error : libxlDomainMigrationPrepare:758 : operation failed: Fail to create socket for incoming migration Not sure why it fails just for me. Olaf