Re: Message WARNING: CHECK AND RESET THE DATE! in kvm guests
On Tue, Jun 02, 2020 at 08:28:13AM +, Carlos Lopez wrote: > Hi Otto, > > After some days without problems, it has happened again: > > root on sd0a (912329c5d9d2b184.a) swap on sd0b dump on sd0b > WARNING: clock gained 3 days > WARNING: CHECK AND RESET THE DATE! > > With version 6.6 I never had these problems. I am using default conf for > ntpd, but some errors appears: If you read what I wrote earlier, this is not a problem. ntpd sets the time ok, so nothing to worry about. -Otto > > Jun 2 06:32:01 obsdfw ntpd[91858]: ntp engine ready > Jun 2 06:32:01 obsdfw ntpd[91858]: constraint reply from 9.9.9.9: offset > 1.298291 > Jun 2 06:32:03 obsdfw ntpd[91858]: cancel settime because dns probe failed > Jun 2 06:32:03 obsdfw savecore: no core dump > Jun 2 06:32:04 obsdfw ftp-proxy[73808]: listening on 127.0.0.1 port 8021 > Jun 2 06:32:08 obsdfw ntpd[91858]: constraint reply from 216.58.211.36: > offset 1.270038 > Jun 2 06:32:29 obsdfw ntpd[91858]: peer 162.159.200.123 now valid > Jun 2 06:32:30 obsdfw ntpd[91858]: peer 162.159.200.1 now valid > Jun 2 06:32:30 obsdfw ntpd[91858]: peer 147.156.7.18 now valid > Jun 2 06:32:32 obsdfw ntpd[91858]: peer 162.159.200.123 now valid > Jun 2 06:32:33 obsdfw ntpd[91858]: reply from 147.156.7.26: not synced > (alarm), next query 3184s > Jun 2 06:33:04 obsdfw ntpd[91858]: peer 147.156.7.18 now invalid > Jun 2 06:33:27 obsdfw ntpd[61176]: adjusting local clock by 1.707163s > Jun 2 06:33:50 obsdfw ntpd[91858]: peer 147.156.7.18 now valid > Jun 2 06:35:06 obsdfw ntpd[61176]: adjusting local clock by 1.212163s > Jun 2 06:37:18 obsdfw ntpd[61176]: adjusting local clock by 0.559285s > Jun 2 06:39:28 obsdfw ntpd[91858]: clock is now synced > Jun 2 06:39:28 obsdfw ntpd[91858]: constraint reply from 9.9.9.9: offset > -0.872650 > Jun 2 06:39:28 obsdfw ntpd[91858]: constraint reply from 216.58.211.36: > offset -0.880034 > Jun 2 07:02:16 obsdfw ntpd[61176]: adjusting clock frequency by -0.447350 to > 4.954650ppm > Jun 2 07:25:37 obsdfw ntpd[91858]: peer 147.156.7.26 now valid > Jun 2 07:28:08 obsdfw ntpd[61176]: adjusting clock frequency by -0.050205 to > 4.904445ppm > Jun 2 07:34:08 obsdfw ntpd[91858]: reply from 147.156.7.26: not synced > (alarm), next query 3170s > Jun 2 08:25:24 obsdfw ntpd[91858]: reply from 147.156.7.18: not synced > (alarm), next query 3154s > > Ntpctl -s all output: > 5/5 peers valid, constraint offset -1s, clock synced, stratum 4 > > peer >wt tl st next poll offset delay jitter > 162.159.200.123 time.cloudflare.com > * 1 10 3 28s 33s 1.520ms 2.347ms 0.712ms > 162.159.200.123 from pool pool.ntp.org > * 1 10 3 29s 32s 1.530ms 2.394ms 0.406ms > 147.156.7.26 from pool pool.ntp.org > 1 10 2 10s 34s 0.081ms20.071ms 0.387ms > 162.159.200.1 from pool pool.ntp.org > 1 10 3 11s 30s 1.502ms 2.442ms 0.134ms > 147.156.7.18 from pool pool.ntp.org > 1 10 2 3005s 3154s 1.199ms19.994ms 0.321ms > > On 25/05/2020, 10:20, "Otto Moerbeek" wrote: > > On Mon, May 25, 2020 at 07:53:47AM +, Carlos Lopez wrote: > > > Hi all, > > > > After upgrading four kvm guests to OpenBSD 6.7, I see the following > messages when these guests starts: > > > > WARNING: clock gained 2 days > > WARNING: CHECK AND RESET THE DATE! > > This means the clock compared to the last mounted filesystem time differ. > > Show what ntpd is doing after boot (see /var/log/daemon). If ntpd sets > the time ok, there is nothing further to be done. It's just a warning > that the kernel initially isn't sure about the time. > > -Otto > > > > > All four guests are fully patched. Dmesg output: > > > > OpenBSD 6.7 (GENERIC) #1: Sat May 16 16:07:20 MDT 2020 > > > r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > > real mem = 788389888 (751MB) > > avail mem = 752021504 (717MB) > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5af0 (9 entries) > > bios0: vendor SeaBIOS version "1.11.1-4.module+el8.1.0+4066+0f1aadab" > date 04/01/2014 > > bios0: Red Hat KVM > > acpi0 at bios0: ACPI 3.0 > > acpi0: sleep states S5 > > acpi0: tables DSDT FACP APIC MCFG > > acpi0: wakeup devices > > acpitimer0 at acpi0: 3579545 Hz, 24 bits > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: Intel Core Processor (Broadwell), 1900.30 MHz, 06-3d-02 > > cpu0: >
Re: Message WARNING: CHECK AND RESET THE DATE! in kvm guests
Hi Otto, After some days without problems, it has happened again: root on sd0a (912329c5d9d2b184.a) swap on sd0b dump on sd0b WARNING: clock gained 3 days WARNING: CHECK AND RESET THE DATE! With version 6.6 I never had these problems. I am using default conf for ntpd, but some errors appears: Jun 2 06:32:01 obsdfw ntpd[91858]: ntp engine ready Jun 2 06:32:01 obsdfw ntpd[91858]: constraint reply from 9.9.9.9: offset 1.298291 Jun 2 06:32:03 obsdfw ntpd[91858]: cancel settime because dns probe failed Jun 2 06:32:03 obsdfw savecore: no core dump Jun 2 06:32:04 obsdfw ftp-proxy[73808]: listening on 127.0.0.1 port 8021 Jun 2 06:32:08 obsdfw ntpd[91858]: constraint reply from 216.58.211.36: offset 1.270038 Jun 2 06:32:29 obsdfw ntpd[91858]: peer 162.159.200.123 now valid Jun 2 06:32:30 obsdfw ntpd[91858]: peer 162.159.200.1 now valid Jun 2 06:32:30 obsdfw ntpd[91858]: peer 147.156.7.18 now valid Jun 2 06:32:32 obsdfw ntpd[91858]: peer 162.159.200.123 now valid Jun 2 06:32:33 obsdfw ntpd[91858]: reply from 147.156.7.26: not synced (alarm), next query 3184s Jun 2 06:33:04 obsdfw ntpd[91858]: peer 147.156.7.18 now invalid Jun 2 06:33:27 obsdfw ntpd[61176]: adjusting local clock by 1.707163s Jun 2 06:33:50 obsdfw ntpd[91858]: peer 147.156.7.18 now valid Jun 2 06:35:06 obsdfw ntpd[61176]: adjusting local clock by 1.212163s Jun 2 06:37:18 obsdfw ntpd[61176]: adjusting local clock by 0.559285s Jun 2 06:39:28 obsdfw ntpd[91858]: clock is now synced Jun 2 06:39:28 obsdfw ntpd[91858]: constraint reply from 9.9.9.9: offset -0.872650 Jun 2 06:39:28 obsdfw ntpd[91858]: constraint reply from 216.58.211.36: offset -0.880034 Jun 2 07:02:16 obsdfw ntpd[61176]: adjusting clock frequency by -0.447350 to 4.954650ppm Jun 2 07:25:37 obsdfw ntpd[91858]: peer 147.156.7.26 now valid Jun 2 07:28:08 obsdfw ntpd[61176]: adjusting clock frequency by -0.050205 to 4.904445ppm Jun 2 07:34:08 obsdfw ntpd[91858]: reply from 147.156.7.26: not synced (alarm), next query 3170s Jun 2 08:25:24 obsdfw ntpd[91858]: reply from 147.156.7.18: not synced (alarm), next query 3154s Ntpctl -s all output: 5/5 peers valid, constraint offset -1s, clock synced, stratum 4 peer wt tl st next poll offset delay jitter 162.159.200.123 time.cloudflare.com * 1 10 3 28s 33s 1.520ms 2.347ms 0.712ms 162.159.200.123 from pool pool.ntp.org * 1 10 3 29s 32s 1.530ms 2.394ms 0.406ms 147.156.7.26 from pool pool.ntp.org 1 10 2 10s 34s 0.081ms20.071ms 0.387ms 162.159.200.1 from pool pool.ntp.org 1 10 3 11s 30s 1.502ms 2.442ms 0.134ms 147.156.7.18 from pool pool.ntp.org 1 10 2 3005s 3154s 1.199ms19.994ms 0.321ms On 25/05/2020, 10:20, "Otto Moerbeek" wrote: On Mon, May 25, 2020 at 07:53:47AM +, Carlos Lopez wrote: > Hi all, > > After upgrading four kvm guests to OpenBSD 6.7, I see the following messages when these guests starts: > > WARNING: clock gained 2 days > WARNING: CHECK AND RESET THE DATE! This means the clock compared to the last mounted filesystem time differ. Show what ntpd is doing after boot (see /var/log/daemon). If ntpd sets the time ok, there is nothing further to be done. It's just a warning that the kernel initially isn't sure about the time. -Otto > > All four guests are fully patched. Dmesg output: > > OpenBSD 6.7 (GENERIC) #1: Sat May 16 16:07:20 MDT 2020 > r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > real mem = 788389888 (751MB) > avail mem = 752021504 (717MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5af0 (9 entries) > bios0: vendor SeaBIOS version "1.11.1-4.module+el8.1.0+4066+0f1aadab" date 04/01/2014 > bios0: Red Hat KVM > acpi0 at bios0: ACPI 3.0 > acpi0: sleep states S5 > acpi0: tables DSDT FACP APIC MCFG > acpi0: wakeup devices > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel Core Processor (Broadwell), 1900.30 MHz, 06-3d-02 > cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,3DNOWP,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,ARAT,XSAVEOPT,MELTDOWN > 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
Re: Message WARNING: CHECK AND RESET THE DATE! in kvm guests
On Mon, May 25, 2020 at 07:53:47AM +, Carlos Lopez wrote: > Hi all, > > After upgrading four kvm guests to OpenBSD 6.7, I see the following messages > when these guests starts: > > WARNING: clock gained 2 days > WARNING: CHECK AND RESET THE DATE! This means the clock compared to the last mounted filesystem time differ. Show what ntpd is doing after boot (see /var/log/daemon). If ntpd sets the time ok, there is nothing further to be done. It's just a warning that the kernel initially isn't sure about the time. -Otto > > All four guests are fully patched. Dmesg output: > > OpenBSD 6.7 (GENERIC) #1: Sat May 16 16:07:20 MDT 2020 > r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC > real mem = 788389888 (751MB) > avail mem = 752021504 (717MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5af0 (9 entries) > bios0: vendor SeaBIOS version "1.11.1-4.module+el8.1.0+4066+0f1aadab" date > 04/01/2014 > bios0: Red Hat KVM > acpi0 at bios0: ACPI 3.0 > acpi0: sleep states S5 > acpi0: tables DSDT FACP APIC MCFG > acpi0: wakeup devices > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel Core Processor (Broadwell), 1900.30 MHz, 06-3d-02 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,3DNOWP,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,ARAT,XSAVEOPT,MELTDOWN > 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 > ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins > acpimcfg0 at acpi0 > acpimcfg0: addr 0xb000, bus 0-255 > acpiprt0 at acpi0: bus 0 (PCI0) > acpicpu0 at acpi0: C1(@1 halt!) > "ACPI0006" at acpi0 not configured > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpicmos0 at acpi0 > "PNP0A06" at acpi0 not configured > "PNP0A06" at acpi0 not configured > "QEMU0002" at acpi0 not configured > "ACPI0010" at acpi0 not configured > cpu0: using Broadwell MDS workaround > pvbus0 at mainbus0: KVM > pvclock0 at pvbus0 > pci0 at mainbus0 bus 0 > Pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x00 > vga1 at pci0 dev 1 function 0 "Red Hat QXL Video" rev 0x04 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) > ppb0 at pci0 dev 2 function 0 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci1 at ppb0 bus 1 > virtio0 at pci1 dev 0 function 0 "Qumranet Virtio 1.x Network" rev 0x01 > vio0 at virtio0: address 00:50:56:f3:d8:1f > virtio0: msix shared > ppb1 at pci0 dev 2 function 1 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci2 at ppb1 bus 2 > virtio1 at pci2 dev 0 function 0 "Qumranet Virtio 1.x Network" rev 0x01 > vio1 at virtio1: address 00:50:56:b8:2b:4a > virtio1: msix shared > ppb2 at pci0 dev 2 function 2 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci3 at ppb2 bus 3 > virtio2 at pci3 dev 0 function 0 "Qumranet Virtio 1.x Console" rev 0x01 > virtio2: no matching child driver; not configured > ppb3 at pci0 dev 2 function 3 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci4 at ppb3 bus 4 > virtio3 at pci4 dev 0 function 0 "Qumranet Virtio 1.x Storage" rev 0x01 > vioblk0 at virtio3 > scsibus1 at vioblk0: 2 targets > sd0 at scsibus1 targ 0 lun 0: > sd0: 16384MB, 512 bytes/sector, 33554432 sectors > virtio3: msix shared > ppb4 at pci0 dev 2 function 4 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci5 at ppb4 bus 5 > virtio4 at pci5 dev 0 function 0 vendor "Qumranet", unknown product 0x1045 > rev 0x01 > viomb0 at virtio4 > virtio4: apic 0 int 22 > ppb5 at pci0 dev 2 function 5 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci6 at ppb5 bus 6 > virtio5 at pci6 dev 0 function 0 "Qumranet Virtio 1.x RNG" rev 0x01 > viornd0 at virtio5 > virtio5: apic 0 int 22 > ppb6 at pci0 dev 2 function 6 vendor "Red Hat", unknown product 0x000c rev > 0x00: apic 0 int 22 > pci7 at ppb6 bus 7 > pcib0 at pci0 dev 31 function 0 "Intel 82801IB LPC" rev 0x02 > ahci0 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x02: msi, AHCI 1.0 > scsibus2 at ahci0: 32 targets > ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x02: apic 0 int 16 > iic0 at ichiic0 > isa0 at pcib0 > isadma0 at isa0 > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > pckbc0 at
Message WARNING: CHECK AND RESET THE DATE! in kvm guests
Hi all, After upgrading four kvm guests to OpenBSD 6.7, I see the following messages when these guests starts: WARNING: clock gained 2 days WARNING: CHECK AND RESET THE DATE! All four guests are fully patched. Dmesg output: OpenBSD 6.7 (GENERIC) #1: Sat May 16 16:07:20 MDT 2020 r...@syspatch-67-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 788389888 (751MB) avail mem = 752021504 (717MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5af0 (9 entries) bios0: vendor SeaBIOS version "1.11.1-4.module+el8.1.0+4066+0f1aadab" date 04/01/2014 bios0: Red Hat KVM acpi0 at bios0: ACPI 3.0 acpi0: sleep states S5 acpi0: tables DSDT FACP APIC MCFG acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel Core Processor (Broadwell), 1900.30 MHz, 06-3d-02 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,ABM,3DNOWP,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,ARAT,XSAVEOPT,MELTDOWN 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 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xb000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1(@1 halt!) "ACPI0006" at acpi0 not configured acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0A06" at acpi0 not configured "PNP0A06" at acpi0 not configured "QEMU0002" at acpi0 not configured "ACPI0010" at acpi0 not configured cpu0: using Broadwell MDS workaround pvbus0 at mainbus0: KVM pvclock0 at pvbus0 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x00 vga1 at pci0 dev 1 function 0 "Red Hat QXL Video" rev 0x04 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb0 at pci0 dev 2 function 0 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci1 at ppb0 bus 1 virtio0 at pci1 dev 0 function 0 "Qumranet Virtio 1.x Network" rev 0x01 vio0 at virtio0: address 00:50:56:f3:d8:1f virtio0: msix shared ppb1 at pci0 dev 2 function 1 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci2 at ppb1 bus 2 virtio1 at pci2 dev 0 function 0 "Qumranet Virtio 1.x Network" rev 0x01 vio1 at virtio1: address 00:50:56:b8:2b:4a virtio1: msix shared ppb2 at pci0 dev 2 function 2 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci3 at ppb2 bus 3 virtio2 at pci3 dev 0 function 0 "Qumranet Virtio 1.x Console" rev 0x01 virtio2: no matching child driver; not configured ppb3 at pci0 dev 2 function 3 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci4 at ppb3 bus 4 virtio3 at pci4 dev 0 function 0 "Qumranet Virtio 1.x Storage" rev 0x01 vioblk0 at virtio3 scsibus1 at vioblk0: 2 targets sd0 at scsibus1 targ 0 lun 0: sd0: 16384MB, 512 bytes/sector, 33554432 sectors virtio3: msix shared ppb4 at pci0 dev 2 function 4 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci5 at ppb4 bus 5 virtio4 at pci5 dev 0 function 0 vendor "Qumranet", unknown product 0x1045 rev 0x01 viomb0 at virtio4 virtio4: apic 0 int 22 ppb5 at pci0 dev 2 function 5 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci6 at ppb5 bus 6 virtio5 at pci6 dev 0 function 0 "Qumranet Virtio 1.x RNG" rev 0x01 viornd0 at virtio5 virtio5: apic 0 int 22 ppb6 at pci0 dev 2 function 6 vendor "Red Hat", unknown product 0x000c rev 0x00: apic 0 int 22 pci7 at ppb6 bus 7 pcib0 at pci0 dev 31 function 0 "Intel 82801IB LPC" rev 0x02 ahci0 at pci0 dev 31 function 2 "Intel 82801I AHCI" rev 0x02: msi, AHCI 1.0 scsibus2 at ahci0: 32 targets ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x02: apic 0 int 16 iic0 at ichiic0 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo 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 vscsi0 at root scsibus3 at vscsi0: 256 targets softraid0 at root scsibus4 at softraid0: 256 targets root on sd0a (91a26d47938d3239.a) swap on sd0b dump on sd0b WARNING: clock gained 2 days WARNING: CHECK AND RESET THE DATE! Do I need to reconfigure something in OpenBSD? Regards, C. L. Martinez
