On Wed, Jul 24, 2024 at 07:45:31PM +0100, David Woodhouse wrote: > On Wed, 2024-07-24 at 13:29 -0400, Michael S. Tsirkin wrote: > > > > Isn't the existing vmgenid sufficient for this disruption marker > > and if not, why? > > No, VMGENID handles snapshotting and cloning of virtual machines, but > it explicitly *doesn't* change on live migration.
Ah, good point. I note the marker will always trigger on a snapshot though, so there's some overlap. -- MST
