On Thu, 02 Nov 2023 16:21:28 +0000, Paul Durrant wrote: > Unless explicitly told to do so (by passing 'clocksource=tsc' and > 'tsc=stable:socket', and then jumping through some hoops concerning > potential CPU hotplug) Xen will never use TSC as its clocksource. > Hence, by default, a Xen guest will not see PVCLOCK_TSC_STABLE_BIT set > in either the primary or secondary pvclock memory areas. This has > led to bugs in some guest kernels which only become evident if > PVCLOCK_TSC_STABLE_BIT *is* set in the pvclocks. Hence, to support > such guests, give the VMM a new Xen HVM config flag to tell KVM to > forcibly clear the bit in the Xen pvclocks. > > [...] Applied to kvm-x86 xen (and not on a Friday!), thanks! [1/1] KVM x86/xen: add an override for PVCLOCK_TSC_STABLE_BIT https://github.com/kvm-x86/linux/commit/6d7228352609 -- https://github.com/kvm-x86/linux/tree/next