Re: NetBSD on Linode

2024-10-23 Thread atomicules
On 14-Sep-2024 15:35:37, Jan Schaumann wrote: Hey, I just put together instructions for installing NetBSD on Linode: https://www.netmeister.org/blog/netbsd-on-linode.html Very belatedly replying, but been busy. Thanks for this! I've been running NetBSD on Linode for about 11 years now. It's

Re: NetBSD on Linode

2024-09-14 Thread Fekete Zoltán
Ekkor: 2024. szeptember 14. 21:35:37 CEST, Jan Schaumann írta: >Hey, > >I just put together instructions for installing NetBSD >on Linode: > >https://www.netmeister.org/blog/netbsd-on-linode.html > >This is still a once-per-instance effort[1], but other >than that, it works just fine. > >So if

Re: NetBSD on Linode kvm problems

2018-03-03 Thread Michael Parson
On Thu, 15 Feb 2018, Michael Parson wrote: On Sun, 11 Feb 2018, Michael Parson wrote: In any case, I've been up for nearly 48 hours with it being set to 'piixpm0' and haven't seen it slip or stall out yet. *fingers crossed* Just over 5 days of uptime and some time today it started to slip

Re: NetBSD on Linode kvm problems

2018-03-03 Thread atomicules
Just to follow-up here, because it's now been almost two weeks that everything has been running fine again (woohoo!). I wasn't interested in performing a scientific experiment to figure out what went wrong or what exactly fixed it, in the end I did: - Switched timecounter to ACPI-Safe. This w

Re: NetBSD on Linode kvm problems

2018-02-15 Thread Michael Parson
On Sun, 11 Feb 2018, Michael Parson wrote: In any case, I've been up for nearly 48 hours with it being set to 'piixpm0' and haven't seen it slip or stall out yet. *fingers crossed* Just over 5 days of uptime and some time today it started to slip behind. I'm now running with: kern.timecou

Re: NetBSD on Linode kvm problems

2018-02-11 Thread Michael Parson
On Fri, 9 Feb 2018, Michael Parson wrote: On Sat, 10 Feb 2018, Michael van Elst wrote: mpar...@bl.org (Michael Parson) writes: Ran this a couple of minutes ago: $ sudo sysctl -w kern.timecounter.hardware=clockinterrupt kern.timecounter.hardware: hpet0 -> clockinterrupt And my clock is a

Re: NetBSD on Linode kvm problems

2018-02-09 Thread Michael Parson
On Sat, 10 Feb 2018, Michael van Elst wrote: mpar...@bl.org (Michael Parson) writes: Ran this a couple of minutes ago: $ sudo sysctl -w kern.timecounter.hardware=clockinterrupt kern.timecounter.hardware: hpet0 -> clockinterrupt And my clock is already 4 minutes off :-/ Means your timer

Re: NetBSD on Linode kvm problems

2018-02-09 Thread Michael van Elst
mpar...@bl.org (Michael Parson) writes: >Ran this a couple of minutes ago: >$ sudo sysctl -w kern.timecounter.hardware=clockinterrupt >kern.timecounter.hardware: hpet0 -> clockinterrupt >And my clock is already 4 minutes off :-/ Means your timer interrupt is way off, that causes all short term

Re: NetBSD on Linode kvm problems

2018-02-09 Thread Michael Parson
Just got back from a reboot and saw this message... :) On Fri, 9 Feb 2018, atomicules wrote: On 09-Feb-2018 16:57:59, Michael Parson wrote: Ran this a couple of minutes ago: $ sudo sysctl -w kern.timecounter.hardware=clockinterrupt kern.timecounter.hardware: hpet0 -> clockinterrupt And my cl

Re: NetBSD on Linode kvm problems

2018-02-09 Thread atomicules
On 09-Feb-2018 16:57:59, Michael Parson wrote: Ran this a couple of minutes ago: $ sudo sysctl -w kern.timecounter.hardware=clockinterrupt kern.timecounter.hardware: hpet0 -> clockinterrupt And my clock is already 4 minutes off :-/ [From searching][1]: might be worth making the change in /et

Re: NetBSD on Linode kvm problems

2018-02-09 Thread Michael Parson
On Fri, 9 Feb 2018, atomicules wrote: Also, forgot to send this to the list earlier: --- Hi Michael, just to say that I've seen the same: https://twitter.com/atomicules/status/955750901381259264 https://twitter.com/atomicules/status/956466949168476160 I tried para-virtualised and it didn'

Re: NetBSD on Linode kvm problems

2018-02-09 Thread Michael Parson
On Fri, 9 Feb 2018, Michael van Elst wrote: mpar...@bl.org (Michael Parson) writes: I then noticed that my clock was way off. After about a week of running, the clock was 4 days(!) behind, even with ntpd running. ntpd won't correct a clock that appears to drift too fast. This I knew. I'm

Re: NetBSD on Linode kvm problems

2018-02-09 Thread atomicules
Also, forgot to send this to the list earlier: --- Hi Michael, just to say that I've seen the same: https://twitter.com/atomicules/status/955750901381259264 https://twitter.com/atomicules/status/956466949168476160 I tried para-virtualised and it didn't help and also ran into a nasty bug.

Re: NetBSD on Linode kvm problems

2018-02-09 Thread atomicules
Here's mine... On 09-Feb-2018 18:57:11, Michael van Elst wrote: Can you check what timecounter is used and switch to a different one? sysctl kern.timecounter.choice kern.timecounter.choice = TSC(q=-100, f=2500206200 Hz) clockinterrupt(q=0, f=100 Hz) piixpm0(q=1000, f=3579545 Hz) hpet0(q=200

Re: NetBSD on Linode kvm problems

2018-02-09 Thread Michael van Elst
mpar...@bl.org (Michael Parson) writes: >I then noticed that my clock was way off. After about a week of >running, the clock was 4 days(!) behind, even with ntpd running. ntpd won't correct a clock that appears to drift too fast. Can you check what timecounter is used and switch to a different