> If your clock drift is worse than that, your clock is broken. Which
> alas is the case for vm.
I agree with this statement.
About 20 years ago, I defined the minimum system we attempt to run well
on as IPL32 or I32LP64, with a MMU.
Soon this was redefined as with an FPU as well, after which I
On 2017-07-18, tomr wrote:
> In playing with vmd, I'm unable to get the guest's ntpd to sync to its
> upstream ntp (whether that's the host ntpd or poot.ntp.org). The guest
> is losing about 1 second for every 2 that pass.
To build a bridge between this question and Mike's reply:
This problem ha
On Tue, Jul 18, 2017 at 08:45:04PM +1000, tomr wrote:
> Good time-of-day,
>
> In playing with vmd, I'm unable to get the guest's ntpd to sync to its
> upstream ntp (whether that's the host ntpd or poot.ntp.org). The guest
> is losing about 1 second for every 2 that pass. I'm using a recent
> snaps
Good time-of-day,
In playing with vmd, I'm unable to get the guest's ntpd to sync to its
upstream ntp (whether that's the host ntpd or poot.ntp.org). The guest
is losing about 1 second for every 2 that pass. I'm using a recent
snapshot on both host and guest on a 1st gen thinkpad X1 carbon (dmesgs
4 matches
Mail list logo
