Stuart, sorry I wasnt entirely clear in my last email 1) you can try the /sys/module/kvm_intel/parameters/preemption_timer
if the system is an intel CPU based Physcial server 2) if you have an amd System you may find the issue does not occur in that case 3) looking at the DMESG I see a KVM CPU in the VM config ... in proxmox you can set it to Host if the emulated kvm CPU is causing the issue with OpenBSD this is something to try and it may improve your sytem performance more generally (and hopefully help the times) Other people who have Proxmox 7.1 and have access to an AMD CPU based server if they can try running an OpenBSD VM on an Amd Processor based server to compare ( what I found in my experience wiht KVM and OpenBSD and Proxmox was the Drift issue / COnsole freeze only occured on Intel Based systems ... and the preemption_timer kernel setting in the Proxmox Linux Kernel sorted it On Thu, 14 Apr 2022 at 22:45, Tom Smyth <tom.sm...@wirelessconnect.eu> wrote: > > Stuart > > is your host on an Intel System ? > > I had an awful time with Proxmox 5.0 and 5.1 > > with clock drift and console freezes > > can you try to disable the following feature in the Proxmox Host kernel > > /sys/module/kvm_intel/parameters/preemption_timer > > https://www.mail-archive.com/misc@openbsd.org/msg158768.html > > > You can try change the CPU to VM to Host (or the lowest generation > Processor that is common to all your hosts in the cluster > Better acceleration with modern processeor > > Hope this helps > > > On Thu, 14 Apr 2022 at 22:37, Stuart Henderson > <stu.li...@spacehopper.org> wrote: > > > > I have some OpenBSD guests in Proxmox VE 7.1-7 (pve-qemu-kvm_6.1.0) and > > seeing pretty bad clock drift (50 seconds in ~7h uptime). ntpd can't cope > > with it. From boot: > > > > 2022-04-14T13:58:19.844Z ntpd[26996]: adjusting local clock by 1.745061s > > 2022-04-14T13:59:24.070Z ntpd[26996]: adjusting local clock by 1.504470s > > 2022-04-14T14:03:51.176Z ntpd[26996]: adjusting local clock by 2.430486s > > 2022-04-14T14:07:40.299Z ntpd[26996]: adjusting local clock by 2.411118s > > 2022-04-14T14:11:51.540Z ntpd[26996]: adjusting local clock by 3.173884s > > 2022-04-14T14:15:03.534Z ntpd[26996]: adjusting local clock by 3.109722s > > 2022-04-14T14:16:04.848Z ntpd[26996]: adjusting local clock by 3.185755s > > 2022-04-14T14:17:40.286Z ntpd[26996]: adjusting local clock by 3.575126s > > 2022-04-14T14:18:45.582Z ntpd[26996]: adjusting local clock by 4.231518s > > 2022-04-14T14:22:27.618Z ntpd[26996]: adjusting local clock by 4.231999s > > 2022-04-14T14:25:41.618Z ntpd[26996]: adjusting local clock by 4.844904s > > 2022-04-14T14:29:58.888Z ntpd[26996]: adjusting local clock by 4.451876s > > 2022-04-14T14:32:41.628Z ntpd[26996]: adjusting local clock by 5.250357s > > > > etc. No difference whether qemu-ga is used or not. No difference between > > passing through the real cpu type (i.e. cpu=host, Ryzen 5650G in this case) > > and passing through as "common KVM processor". The guest does detect and > > use pvclock(4). > > > > $ sysctl kern.timecounter > > kern.timecounter.tick=1 > > kern.timecounter.timestepwarnings=0 > > kern.timecounter.hardware=pvclock0 > > kern.timecounter.choice=i8254(0) pvclock0(1500) acpihpet0(1000) > > acpitimer0(1000) > > > > Anyone have ideas of things I could try that are less wrong than > > running rdate from cron? Thanks. > > > > > > OpenBSD 7.1 (GENERIC.MP) #463: Thu Apr 7 12:48:15 MDT 2022 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 1056808960 (1007MB) > > avail mem = 1007554560 (960MB) > > random: good seed from bootblocks > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf58e0 (9 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: Common KVM processor, 3892.54 MHz, 0f-06-01 > > 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,CX16,x2APIC,HV,NXE,LONG,LAHF,CMPLEG > > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > > 64b/line 16-way L2 cache > > cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > > cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > cpu0: apic clock running at 1000MHz > > cpu1 at mainbus0: apid 1 (application processor) > > cpu1: Common KVM processor, 3892.11 MHz, 0f-06-01 > > cpu1: > > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,x2APIC,HV,NXE,LONG,LAHF,CMPLEG > > cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB > > 64b/line 16-way L2 cache > > cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > > cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped > > cpu1: smt 0, core 1, package 0 > > ioapic0 at mainbus0: apid 0 pa 0xfec00000, version 11, 24 pins > > acpihpet0 at acpi0: 100000000 Hz > > acpiprt0 at acpi0: bus 0 (PCI0) > > "ACPI0006" at acpi0 not configured > > acpipci0 at acpi0 PCI0 > > acpicmos0 at acpi0 > > "PNP0A06" at acpi0 not configured > > "PNP0A06" at acpi0 not configured > > "PNP0A06" at acpi0 not configured > > "QEMU0002" at acpi0 not configured > > "ACPI0010" at acpi0 not configured > > "QEMUVGID" at acpi0 not configured > > acpicpu0 at acpi0: C1(@1 halt!) > > acpicpu1 at acpi0: C1(@1 halt!) > > pvbus0 at mainbus0: KVM > > pvclock0 at pvbus0 > > pci0 at mainbus0 bus 0 > > pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 > > pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 > > pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel > > 0 wired to compatibility, channel 1 wired to compatibility > > pciide0: channel 0 disabled (no drives) > > atapiscsi0 at pciide0 channel 1 drive 0 > > scsibus1 at atapiscsi0: 2 targets > > cd0 at scsibus1 targ 0 lun 0: <QEMU, QEMU DVD-ROM, 2.5+> removable > > cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 > > uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11 > > piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int > > 9 > > iic0 at piixpm0 > > vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02 > > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > > virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Memory Balloon" rev 0x00 > > viomb0 at virtio0 > > virtio0: apic 0 int 11 > > virtio1 at pci0 dev 10 function 0 "Qumranet Virtio Storage" rev 0x00 > > vioblk0 at virtio1 > > scsibus2 at vioblk0: 1 targets > > sd0 at scsibus2 targ 0 lun 0: <VirtIO, Block Device, > > > sd0: 10240MB, 512 bytes/sector, 20971520 sectors > > virtio1: msix per-VQ > > virtio2 at pci0 dev 18 function 0 "Qumranet Virtio Network" rev 0x00 > > vio0 at virtio2: address c6:e5:7f:4f:5e:cf > > virtio2: msix shared > > ppb0 at pci0 dev 30 function 0 "Red Hat Qemu PCI-PCI" rev 0x00 > > pci1 at ppb0 bus 1 > > ppb1 at pci0 dev 31 function 0 "Red Hat Qemu PCI-PCI" rev 0x00 > > pci2 at ppb1 bus 2 > > isa0 at pcib0 > > isadma0 at isa0 > > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 > > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > > pckbd0 at pckbc0 (kbd slot) > > wskbd0 at pckbd0: console keyboard, using wsdisplay0 > > pms0 at pckbc0 (aux slot) > > wsmouse0 at pms0 mux 0 > > pcppi0 at isa0 port 0x61 > > spkr0 at pcppi0 > > usb0 at uhci0: USB revision 1.0 > > uhub0 at usb0 configuration 1 interface 0 "Intel UHCI root hub" rev > > 1.00/1.00 addr 1 > > uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet" > > rev 2.00/0.00 addr 2 > > uhidev0: iclass 3/0 > > ums0 at uhidev0: 3 buttons, Z dir > > wsmouse1 at ums0 mux 0 > > vscsi0 at root > > scsibus3 at vscsi0: 256 targets > > softraid0 at root > > scsibus4 at softraid0: 256 targets > > root on sd0a (cf14a346fbf0559d.a) swap on sd0b dump on sd0b > > fd0 at fdc0 drive 1: density unknown > > > > > > > > > -- > Kindest regards, > Tom Smyth. -- Kindest regards, Tom Smyth.
