Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 14:07:10 +0200, Jiri Denemark wrote: > On Thu, May 12, 2022 at 13:32:38 +0200, Peter Krempa wrote: > > On Thu, May 12, 2022 at 13:30:57 +0200, Jiri Denemark wrote: [] > > > I guess the migration would just hang waiting for an event that never > > > comes. But I guess

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 13:32:38 +0200, Peter Krempa wrote: > On Thu, May 12, 2022 at 13:30:57 +0200, Jiri Denemark wrote: > > On Thu, May 12, 2022 at 12:41:57 +0200, Peter Krempa wrote: > > > On Thu, May 12, 2022 at 12:40:54 +0200, Peter Krempa wrote: > > > > On Thu, May 12, 2022 at 10:55:47

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 10:55:47AM +0200, Jiri Denemark wrote: > Every running QEMU process we are willing to reconnect (i.e., at least > 3.1.0) supports migration events and we can assume the capability is > already enabled since last time libvirt daemon connected to its monitor. > > Well, it's

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 13:30:57 +0200, Jiri Denemark wrote: > On Thu, May 12, 2022 at 12:41:57 +0200, Peter Krempa wrote: > > On Thu, May 12, 2022 at 12:40:54 +0200, Peter Krempa wrote: > > > On Thu, May 12, 2022 at 10:55:47 +0200, Jiri Denemark wrote: > > > > Every running QEMU process we are

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 12:41:57 +0200, Peter Krempa wrote: > On Thu, May 12, 2022 at 12:40:54 +0200, Peter Krempa wrote: > > On Thu, May 12, 2022 at 10:55:47 +0200, Jiri Denemark wrote: > > > Every running QEMU process we are willing to reconnect (i.e., at least > > > 3.1.0) supports migration

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 12:40:54 +0200, Peter Krempa wrote: > On Thu, May 12, 2022 at 10:55:47 +0200, Jiri Denemark wrote: > > Every running QEMU process we are willing to reconnect (i.e., at least > > 3.1.0) supports migration events and we can assume the capability is > > already enabled since

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 12:40:54 +0200, Peter Krempa wrote: > On Thu, May 12, 2022 at 10:55:47 +0200, Jiri Denemark wrote: > > Every running QEMU process we are willing to reconnect (i.e., at least > > 3.1.0) supports migration events and we can assume the capability is > > already enabled since

Re: [libvirt PATCH 4/4] qemu: Enable migration events only for fresh QEMU process

On Thu, May 12, 2022 at 10:55:47 +0200, Jiri Denemark wrote: > Every running QEMU process we are willing to reconnect (i.e., at least > 3.1.0) supports migration events and we can assume the capability is > already enabled since last time libvirt daemon connected to its monitor. > > Well, it's