On Tue, 2021-03-16 at 09:02 +0100, Jan Beulich wrote: > On 16.03.2021 03:10, Dylanger Daly wrote: > > I just wanted to close this off and let everyone know the issue > > ended up being a faulty/misconfigured HPET clock. > > > > Appending `clocksource=tsc tsc=unstable hpetbroadcast=0` to Xen's > > CMDLINE totally fixed my issue, I assume Xen was detecting TSC may > > have been 'off' and was trying to recover/self-correct? > > I find this a very confusing combination of command line options. > In particular "tsc=unstable" clears one of the feature prereqs > (TSC_RELIABLE) that are required for "clocksource=tsc" to take > any effect, afaict. I therefore would conclude that you're not > actually running with TSC as the clock source. > Right. Also, isn't hpetbroadcast set to 0 by default already?
Dario -- Dario Faggioli, Ph.D http://about.me/dario.faggioli Virtualization Software Engineer SUSE Labs, SUSE https://www.suse.com/ ------------------------------------------------------------------- <<This happens because _I_ choose it to happen!>> (Raistlin Majere)
signature.asc
Description: This is a digitally signed message part
