On Thu, Jan 02, 2025 at 08:21:11AM -0800, Richard Cochran wrote:

On Thu, Jan 02, 2025 at 05:11:01PM +0100, Peter Hilber wrote:

quoted

For sure. But the aim of this proposal is to have an interoperable time
synchronization solution for VMs through a Virtio device. So the idea is
to include metrics, if a consensus on their usefulness can be reached.
AFAIU it is difficult to bypass the kernel for Virtio devices.

Providing clock metrics only makes sense when there is some choice to
be made based on those metrics.  If the "limited" VM guests don't even
have networking, then they have no choice but to accept the time from
the VM host, right?  In which case, the metrics do not provide any
benefit to the guest.

Or what am I missing?

The proposal is not limited to guests with no networking.

Guests *might* not have internet access (might not be "internetworked").
Even then, guests can still interact with the environment (so metrics
can be important) and might decide to reduce features when the metrics
are too bad.

Thanks for the comments,

Peter