On Mon, Jun 29, 2020 at 7:23 AM Martin <martin...@protonmail.com> wrote: > > Hi list, > > I'm using Alpine-virt linux (headless linux with 40Mb initial *.iso size) > which has tsc issues. Alpine uses syslinux lightweight boot loader by > default. In order to enable tsc I've added tsc=reliable tsc=noirqtime to > /etc/update-extlinux.conf before console=ttyS0,115200 and updated it > accordingly.
You don't mention which Alpine and kernel version you're using. Also, you don't mention which OpenBSD version...-current or 6.7? Some major fixes just went into -current and look like they were in last night's amd64 snapshots. > > It seems no changes in tsc usage prior to /dev/rtc0 as boot log shows: > ... > * Setting system clock using the hardware clock [UTC] ...hwclock: select() to > /dev/rtc0 to wait for clock tick timed out > * Failed to set the system clock /dev/rtc0 has nothing to do with the tsc or clocksource. This looks like a separate issue and your guest isn't properly using the emulated mc146818 device. I'm guessing there are bigger issues here. > ... > > Does somebody know some way how set tsc as default clock source in Alpine > 5.4.43-1-virt guest? > Add the linux boot arg: clocksource=tsc But in all honesty, if you want better Linux guest stability, you'll need to use a -current snapshot. Regarding your comment about disks in your other email...what you saw with qcow2 vs raw probably has nothing to do with the emulated disks and everything to do with the stability improvements now in -current. -Dave