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
>
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.
smime.p7s
Description: S/M
On Wed, Jul 24, 2024 at 06:22:42PM +0100, David Woodhouse wrote:
> From: David Woodhouse
>
> The vmclock device addresses the problem of live migration with
> precision clocks. The tolerances of a hardware counter (e.g. TSC) are
> typically around ±50PPM. A guest will use NTP/PTP/PPS to disciplin
From: David Woodhouse
The vmclock device addresses the problem of live migration with
precision clocks. The tolerances of a hardware counter (e.g. TSC) are
typically around ±50PPM. A guest will use NTP/PTP/PPS to discipline that
counter against an external source of 'real' time, and track the pre
From: David Woodhouse
The vmclock device addresses the problem of live migration with precision
clocks. The tolerances of a hardware counter (e.g. TSC) are typically
around ±50PPM. We use NTP/PTP/PPS to discipline that counter against an
external source of 'real' time, and track the precise frequ
