On Sat, Dec 19, 2020 at 12:05:51AM +0100, Martin Kletzander wrote:
> 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.
If you /alw
On Fri, Dec 18, 2020 at 10:42:16PM +0100, Olaf Hering wrote:
Am Fri, 18 Dec 2020 21:09:45 +0100
schrieb Martin Kletzander :
I am guessing you want to `--migrateuri`, possibly with `--listen-address`.
Not sure if I really _want_ all these extra knobs. The intent is clear and
obvious, the conn
Am Fri, 18 Dec 2020 21:09:45 +0100
schrieb Martin Kletzander :
> I am guessing you want to `--migrateuri`, possibly with `--listen-address`.
Not sure if I really _want_ all these extra knobs. The intent is clear and
obvious, the connection needs to go to the specified host and/or IP address.
Bu
On Wed, Dec 16, 2020 at 08:34:29PM +0100, Olaf Hering wrote:
A naive 'virsh migrate --live domU xen+tcp://cross-over-ip' uses the ordinary
uplink instead of the requested IP address. According to the documentation an
additional option has to be specified to really use the other network
interfa
A naive 'virsh migrate --live domU xen+tcp://cross-over-ip' uses the ordinary
uplink instead of the requested IP address. According to the documentation an
additional option has to be specified to really use the other network
interface. However, neither 'tcp://cross-over-ip' nor 'xenmigr:cross-o
