For me the timekeeping was visible after some uptime (few days to a bit over a
week) where the clock was off by 30 minutes two many hours. ntpd could of
course no longer correct that.
So if the machines are up for that long just running date should show this
problem.
If that's not it I guess
* Hrvoje Popovski [2018-10-23 22:46]:
> On 23.10.2018. 21:41, Florian Obser wrote:
> > I'm currently on vacation and can't look into this soon.
> >
> > One thing that comes to mind: do these machines keep proper time or are
> > they having issues with timer interrupts stopping because of too
On 23.10.2018. 21:41, Florian Obser wrote:
> I'm currently on vacation and can't look into this soon.
>
> One thing that comes to mind: do these machines keep proper time or are they
> having issues with timer interrupts stopping because of too new KVM version
> and missing hypervisor flag
I'm currently on vacation and can't look into this soon.
One thing that comes to mind: do these machines keep proper time or are they
having issues with timer interrupts stopping because of too new KVM version and
missing hypervisor flag (someone with access to a real computer please chip in
Hello,
AS57335 operates a 49 node anycast instance exclusively running OpenBSD. All
instances are hosted virtual machines (aka "VPS" instances) and all are
running a recent snapshot (kern.version=OpenBSD 6.4-current (GENERIC.MP) #381:
Mon Oct 22 22:18:48 MDT 2018). Eleven of these nodes exhibit
