On Wed, Dec 16, 2020 at 08:34:29PM +0100, Olaf Hering wrote: I am think not sure exactly what is the setup, but I am guessing you want to `--migrateuri`, possibly with `--listen-address`. For more details see virsh manual page and https://libvirt.org/migration.html ;)

On Fri, Dec 18, 2020 at 10:42:16PM +0100, Olaf Hering wrote: The thing is that there are multiple connections being made (unless you use tunnelled migration) between the client and hosts (or hosts between themselves with peer2peer migration), however the connection string you are using in your command is only specifying how should virsh (or, in case of peer2peer, the source host) connect to the destination for the libvirt connection, not the other connections made between hypervisors. I agree it is not that straightforward. We could default to listening on the ip/host in the libvirt connection, however there are various setups that could break by this and the need for more knobs would not go away anyway. Migration is very complicated thing when you need to handle many special cases. Believe me when I say that libvirt makes it *way* easier than what is happening under the hood despite how many knobs it offers. If you have anything else than the most basic setup you might need to make the extra step. One thing to add, though. If you would rather configure the destination in a way that its hostname resolves to the IP you would prefer for the migration it might be enough to make this work the simple way around. Hope that helps, Martin