On Tue, Jul 05, 2022 at 06:40:26PM +0200, Stuart Henderson wrote: > On 2022/07/05 11:22, Scott Cheloha wrote: > > On Tue, Jul 05, 2022 at 05:47:51PM +0200, Stuart Henderson wrote: > > > On 2022/07/04 21:06, Scott Cheloha wrote: > > > > 4. OpenBSD VMs on other hypervisors. > > > > > > KVM on proxmox VE 7.1-12 > > > > > > I force acpihpet0 on this; it defaults to pvclock which results in > > > timekeeping so bad that ntpd can't correct > > > > That is an interesting problem. Probably worth looking at pvclock(4) > > separately. > > > > > $ sysctl kern.timecounter > > > kern.timecounter.tick=1 > > > kern.timecounter.timestepwarnings=0 > > > kern.timecounter.hardware=acpihpet0 > > > kern.timecounter.choice=i8254(0) pvclock0(1500) acpihpet0(1000) > > > acpitimer0(1000) > > > > > > OpenBSD 7.1-current (GENERIC.MP) #45: Tue Jul 5 16:11:00 BST 2022 > > > st...@bamboo.spacehopper.org:/sys/arch/amd64/compile/GENERIC.MP > > > real mem = 8573001728 (8175MB) > > > avail mem = 8295833600 (7911MB) > > > random: good seed from bootblocks > > > mpath0 at root > > > scsibus0 at mpath0: 256 targets > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf58c0 (10 entries) > > > bios0: vendor SeaBIOS version > > > "rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org" date 04/01/2014 > > > bios0: QEMU Standard PC (i440FX + PIIX, 1996) > > > acpi0 at bios0: ACPI 1.0 > > > acpi0: sleep states S3 S4 S5 > > > acpi0: tables DSDT FACP APIC SSDT HPET WAET > > > acpi0: wakeup devices > > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > > acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat > > > cpu0 at mainbus0: apid 0 (boot processor) > > > cpu0: AMD Ryzen 5 PRO 5650G with Radeon Graphics, 3893.04 MHz, 19-50-00 > > > cpu0: > > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,CPCTR,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBRS,IBPB,STIBP,SSBD,IBPB,IBRS,STIBP,SSBD,VIRTSSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > > > > This machine doesn't have the ITSC flag, so we would never consider > > using the TSC as a timecounter. The sync test is not run, but that > > makes sense. > > > > ... is that expected? Should the machine have the ITSC flag? > > > > (I'm not familiar with Proxmox.) > > > > No idea to be honest. The cpu type is set to "host" so it should pass > things through, but perhaps it deliberately filters out ITSC. Mostly > wanted to point it out as a "doesn't make things worse" (and because > you specifically wanted tests on other VMs :)
Gotcha, that's okay then.
