package: linux-image-5.10.0-15-arm64
version: 5.10.120-1

i am running virtualbox 6.1.34 from the virtualbox.org repo on a debian
11.3 host. the guest also runs debian 11.3.

when both host and guest run the latest stable kernel 5.10.0-15
(5.10.120-1) i get random process crashes in the guest when having
significant i/o for longer than a few seconds on the host.

i.e., when i do a

  # mv <large file> <destination>

or even a

  # md5sum <large file>

or anything that causes significant i/o traffic on the host, the guest
first starts with complaining:

Jul 01 20:44:49 vmguest kernel: hrtimer: interrupt took 21312191 ns
Jul 01 20:45:20 vmguest kernel: clocksource: timekeeping watchdog on CPU0:
kvm-clock wd-wd read-back delay of 816732ns
Jul 01 20:45:20 vmguest kernel: clocksource: wd-tsc-wd read-back delay of
2540783ns, clock-skew test skipped!

and eventually guest processes start to randomly crash, e.g.:

Jun 30 20:17:01 vmguest kernel: traps: sh[250946] general protection fault
ip:7fb0c341708e sp:7ffec3154378 error:0 in
libc-2.31.so[7fb0c33a6000+14b000]
Jul 01 00:00:02 vmguest kernel: traps: hostname[253617] general protection
fault ip:7f905f2b24a6 sp:7fff44a30e30 error:0 in
libc-2.31.so[7f905f299000+14b000]
Jul 01 00:53:01 vmguest kernel: traps: wget[254290] general protection
fault ip:7f934bc23fda sp:7ffd716954d0 error:0 in
libtasn1.so.6.6.0[7f934bc1a000+c000]

if i switch to kernel 5.10.0-14 (5.10.113-1) on the host (the guest kernel
remains 5.10.0-15), then the random process crashes in the guest disappear,
although the complaints from hrtimer and clocksource still remain, but
significantly less often.

i started a thread in the 'debian-user' mailing list:
https://lists.debian.org/debian-user/2022/07/msg00043.html

thank you for looking into this!

greetings...

Hello,

I am also affected by this same bug.

I run Firefox in a virtual machine and if I am running the
5.10.0-15-amd64 kernel on the virtual host, then Firefox crashes
regularly in the virtual guest.

However, if I run the 5.10.0-14-amd64 kernel on the virtual host, then
I see no crashes.

In both cases the virtual guest is running the 5.10.0-15-amd64 kernel

This is on Debian Bullseye

VirtualBox packages are from Fasttrack
virtualbox       6.1.34-dfsg-3~fto11+1            amd64
virtualbox-dkms  6.1.34-dfsg-3~fto11+1            amd64
virtualbox-qt    6.1.34-dfsg-3~fto11+1            amd64

Kernels are the standard Debian kernels from stable (both host and
guest)
linux-image-5.10.0-14-amd64      5.10.113-1       amd64
linux-image-5.10.0-15-amd64      5.10.120-1       amd64

I have seen this issue on two separate systems, so I do not think it is
hardware related.

Happy to do any testing or provide any logs you can suggest.

Regards,

Richard

Control: reassign -1 src:linux 5.10.120-1
Control: tag -1 upstream moreinfo

This indeed looks like an upstream regression between 5.10.113 and 5.10.120.

What surprises me are the time gaps between those GPF messages, ~3.5h and 50m,
but not within the same second/minute. What happens between those time stamps?

If there are more messages around those GPF messages, it would be useful to
share those as well.

In Stable-Proposed-Updates there is a 5.10.127-1 version and it would be
useful to test whether the issue happens with that version too.

Hello,

I have installed the Stable-Proposed-Updates kernel on the virtual host
(linux-image-5.10.0-16-amd64 - 5.10.127-1) and I am still seeing
Firefox crashing frequently in a virtual guest running on this host.

I do not see any messages logged in kern.log when the whole of Firefox
crashes, but I do see the following messages when individual tabs in
Firefox crash (these tab crashes also happened with 5.10.0-15-amd64 -
5.10.120.1 but not with 5.10.0-14-amd64 - 5.10.113-1).

These are from the virtual guest however, not the host.  I do not see
any errors logged to kern.log on the host (even though that is the
system running the problematic kernel).

Jul  5 20:10:23 vwbbase kernel: [  342.977899] DOM Worker[4222]:
segfault at 7fd700942000 ip 00007fd72ba9a307 sp 00007fd71ce03cd0 error
4 in libxul.so[7fd7278dd000+5559000]
Jul  5 20:10:23 vwbbase kernel: [  342.977907] Code: c7 0f 84 48 ff ff
ff 4c 8d 77 38 4c 8d 6f 60 48 8d 6c 24 04 0f 1f 80 00 00 00 00 8b 53 38
49 63 c7 48 03 43 28 44 89 7c 24 04 <44> 8b 38 48 89 ee 4c 89 ef 89 10
4c 89 f2 e8 e6 9a ff ff 45 85 ff
Jul  5 20:13:52 vwbbase kernel: [  552.210131] traps: Web Content[4872]
general protection fault ip:7f0fa8c39426 sp:7ffe80eff5c0 error:0 in
libxul.so[7f0fa490e000+5559000]
Jul  5 20:13:54 vwbbase kernel: [  554.146579] traps: Web Content[5025]
general protection fault ip:7f7cf735b068 sp:7fffaffe93c0 error:0 in
libxul.so[7f7cf350e000+5559000]

Happy to do more testing and send more logs if it helps.

Regards,

Richard

on the host's /var/log/apt/term.log:

Log started: 2022-06-12  10:57:30
...
Preparing to unpack .../08-linux-image-5.10.0-15-amd64_5.10.120-1_amd64.deb
...
Unpacking linux-image-5.10.0-15-amd64 (5.10.120-1) ...
Preparing to unpack .../09-linux-image-amd64_5.10.120-1_amd64.deb ...
Unpacking linux-image-amd64 (5.10.120-1) over (5.10.113-1) ...
...
Setting up linux-image-5.10.0-15-amd64 (5.10.120-1) ...
...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-14-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-14-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-15-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-15-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.10.0-15-amd64
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.10.0-15-amd64
Found initrd image: /boot/initrd.img-5.10.0-15-amd64
Found linux image: /boot/vmlinuz-5.10.0-14-amd64
Found initrd image: /boot/initrd.img-5.10.0-14-amd64
Adding boot menu entry for EFI firmware configuration
done
...
Setting up linux-image-amd64 (5.10.120-1) ...
...
Log ended: 2022-06-12  10:58:50


so, the kernel was installed on 2022-06-12.


and for your request:

# cat <(gunzip -c /var/log/kern.log.{4,3,2}.gz) /var/log/kern.log{.1,} |
grep -B5 -E "hrtimer|clocksource|traps:|Code:|general|segfault"

Apr 18 22:24:41 vmguest kernel: [1669500.364257] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 64914ns
Apr 18 22:24:41 vmguest kernel: [1669500.364328] clocksource: wd-tsc-wd
read-back delay of 314448ns, clock-skew test skipped!
--
Apr 19 13:42:46 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Apr 19 13:42:46 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Apr 19 13:42:46 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Apr 19 13:42:46 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
236b8001, primary cpu clock
Apr 19 13:42:46 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 5303526299 cycles
Apr 19 13:42:46 vmguest kernel: [    0.000007] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Apr 19 13:42:46 vmguest kernel: [    0.180275] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Apr 19 13:42:46 vmguest kernel: [    0.180276] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Apr 19 13:42:46 vmguest kernel: [    0.180277] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Apr 19 13:42:46 vmguest kernel: [    0.180280] [mem 0x40000000-0xfebfffff]
available for PCI devices
Apr 19 13:42:46 vmguest kernel: [    0.180282] Booting paravirtualized
kernel on KVM
Apr 19 13:42:46 vmguest kernel: [    0.180288] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Apr 19 13:42:46 vmguest kernel: [    0.216877] ACPI: Core revision 20200925
Apr 19 13:42:46 vmguest kernel: [    0.217175] APIC: Switch to symmetric
I/O mode setup
Apr 19 13:42:46 vmguest kernel: [    0.217795] x2apic enabled
Apr 19 13:42:46 vmguest kernel: [    0.218367] Switched APIC routing to
physical x2apic.
Apr 19 13:42:46 vmguest kernel: [    0.221130] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Apr 19 13:42:46 vmguest kernel: [    0.221204] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1598c7dcb76, max_idle_ns:
440795222846 ns
--
Apr 19 13:42:46 vmguest kernel: [    0.349407] smpboot: Max logical
packages: 1
Apr 19 13:42:46 vmguest kernel: [    0.349411] smpboot: Total of 4
processors activated (11986.22 BogoMIPS)
Apr 19 13:42:46 vmguest kernel: [    0.355058] node 0 deferred pages
initialised in 4ms
Apr 19 13:42:46 vmguest kernel: [    0.355163] devtmpfs: initialized
Apr 19 13:42:46 vmguest kernel: [    0.355163] x86/mm: Memory block size:
128MB
Apr 19 13:42:46 vmguest kernel: [    0.357525] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Apr 19 13:42:46 vmguest kernel: [    0.709892] NetLabel:  unlabeled traffic
allowed by default
Apr 19 13:42:46 vmguest kernel: [    0.709892] PCI: Using ACPI for IRQ
routing
Apr 19 13:42:46 vmguest kernel: [    0.709892] PCI: pci_cache_line_size set
to 64 bytes
Apr 19 13:42:46 vmguest kernel: [    0.710019] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Apr 19 13:42:46 vmguest kernel: [    0.710030] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Apr 19 13:42:46 vmguest kernel: [    0.715223] clocksource: Switched to
clocksource kvm-clock
--
Apr 19 13:42:46 vmguest kernel: [    0.736766] AppArmor: AppArmor
Filesystem Enabled
Apr 19 13:42:46 vmguest kernel: [    0.736806] pnp: PnP ACPI init
Apr 19 13:42:46 vmguest kernel: [    0.736937] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Apr 19 13:42:46 vmguest kernel: [    0.737086] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Apr 19 13:42:46 vmguest kernel: [    0.738466] pnp: PnP ACPI: found 2
devices
Apr 19 13:42:46 vmguest kernel: [    0.753050] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Apr 19 13:42:46 vmguest kernel: [    0.754918] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Apr 19 13:42:46 vmguest kernel: [    0.755001] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Apr 19 13:42:46 vmguest kernel: [    0.755101] PCI: CLS 0 bytes, default 64
Apr 19 13:42:46 vmguest kernel: [    0.755242] Trying to unpack rootfs
image as initramfs...
Apr 19 13:42:46 vmguest kernel: [    1.488367] Freeing initrd memory:
27512K
Apr 19 13:42:46 vmguest kernel: [    1.488367] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1598c7dcb76, max_idle_ns: 440795222846 ns
Apr 19 13:42:46 vmguest kernel: [    1.498614] clocksource: Switched to
clocksource tsc
--
Apr 19 13:42:46 vmguest kernel: [    9.368813] FS-Cache: Netfs 'nfs'
registered for caching
Apr 19 13:42:46 vmguest kernel: [    9.410584] Key type dns_resolver
registered
Apr 19 13:42:47 vmguest kernel: [   10.186918] NFS: Registering the
id_resolver key type
Apr 19 13:42:47 vmguest kernel: [   10.186942] Key type id_resolver
registered
Apr 19 13:42:47 vmguest kernel: [   10.186944] Key type id_legacy
registered
Apr 19 21:15:26 vmguest kernel: [27158.418788] hrtimer: interrupt took
14731768 ns
Apr 20 11:00:00 vmguest kernel: [76610.431330] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 105910ns
Apr 20 11:00:00 vmguest kernel: [76610.431344] clocksource: wd-tsc-wd
read-back delay of 398215ns, clock-skew test skipped!
--
Apr 20 12:46:40 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Apr 20 12:46:40 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Apr 20 12:46:40 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Apr 20 12:46:40 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
192b8001, primary cpu clock
Apr 20 12:46:40 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 6838525047 cycles
Apr 20 12:46:40 vmguest kernel: [    0.000008] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Apr 20 12:46:40 vmguest kernel: [    0.220497] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Apr 20 12:46:40 vmguest kernel: [    0.220498] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Apr 20 12:46:40 vmguest kernel: [    0.220500] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Apr 20 12:46:40 vmguest kernel: [    0.220502] [mem 0x40000000-0xfebfffff]
available for PCI devices
Apr 20 12:46:40 vmguest kernel: [    0.220504] Booting paravirtualized
kernel on KVM
Apr 20 12:46:40 vmguest kernel: [    0.220510] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Apr 20 12:46:40 vmguest kernel: [    0.277792] ACPI: Core revision 20200925
Apr 20 12:46:40 vmguest kernel: [    0.278087] APIC: Switch to symmetric
I/O mode setup
Apr 20 12:46:40 vmguest kernel: [    0.279143] x2apic enabled
Apr 20 12:46:40 vmguest kernel: [    0.280325] Switched APIC routing to
physical x2apic.
Apr 20 12:46:40 vmguest kernel: [    0.287146] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Apr 20 12:46:40 vmguest kernel: [    0.287269] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x159649535e5, max_idle_ns:
440795218057 ns
--
Apr 20 12:46:40 vmguest kernel: [    0.429371] smpboot: Max logical
packages: 1
Apr 20 12:46:40 vmguest kernel: [    0.429376] smpboot: Total of 4
processors activated (11980.81 BogoMIPS)
Apr 20 12:46:40 vmguest kernel: [    0.431678] node 0 deferred pages
initialised in 4ms
Apr 20 12:46:40 vmguest kernel: [    0.443428] devtmpfs: initialized
Apr 20 12:46:40 vmguest kernel: [    0.443428] x86/mm: Memory block size:
128MB
Apr 20 12:46:40 vmguest kernel: [    0.443924] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Apr 20 12:46:40 vmguest kernel: [    1.044719] NetLabel:  unlabeled traffic
allowed by default
Apr 20 12:46:40 vmguest kernel: [    1.044731] PCI: Using ACPI for IRQ
routing
Apr 20 12:46:40 vmguest kernel: [    1.044735] PCI: pci_cache_line_size set
to 64 bytes
Apr 20 12:46:40 vmguest kernel: [    1.045096] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Apr 20 12:46:40 vmguest kernel: [    1.045110] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Apr 20 12:46:40 vmguest kernel: [    1.052636] clocksource: Switched to
clocksource kvm-clock
--
Apr 20 12:46:40 vmguest kernel: [    1.106321] AppArmor: AppArmor
Filesystem Enabled
Apr 20 12:46:40 vmguest kernel: [    1.106375] pnp: PnP ACPI init
Apr 20 12:46:40 vmguest kernel: [    1.109552] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Apr 20 12:46:40 vmguest kernel: [    1.109799] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Apr 20 12:46:40 vmguest kernel: [    1.113513] pnp: PnP ACPI: found 2
devices
Apr 20 12:46:40 vmguest kernel: [    1.151458] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Apr 20 12:46:40 vmguest kernel: [    1.157570] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Apr 20 12:46:40 vmguest kernel: [    1.157710] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Apr 20 12:46:40 vmguest kernel: [    1.157813] PCI: CLS 0 bytes, default 64
Apr 20 12:46:40 vmguest kernel: [    1.157956] Trying to unpack rootfs
image as initramfs...
Apr 20 12:46:40 vmguest kernel: [    3.199331] Freeing initrd memory:
27512K
Apr 20 12:46:40 vmguest kernel: [    3.199860] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x159649535e5, max_idle_ns: 440795218057 ns
Apr 20 12:46:40 vmguest kernel: [    3.261961] clocksource: Switched to
clocksource tsc
--
Apr 20 12:46:42 vmguest kernel: [   16.978148] SSE version of gcm_enc/dec
engaged.
Apr 20 12:46:42 vmguest kernel: [   17.151638] Key type dns_resolver
registered
Apr 20 12:46:45 vmguest kernel: [   19.746407] NFS: Registering the
id_resolver key type
Apr 20 12:46:45 vmguest kernel: [   19.746436] Key type id_resolver
registered
Apr 20 12:46:45 vmguest kernel: [   19.746438] Key type id_legacy
registered
Apr 20 22:08:57 vmguest kernel: [33751.678388] hrtimer: interrupt took
16026409 ns
Apr 21 11:25:41 vmguest kernel: [81556.085082] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 612957ns
Apr 21 11:25:41 vmguest kernel: [81556.099529] clocksource: wd-tsc-wd
read-back delay of 443951ns, clock-skew test skipped!
Apr 21 11:27:02 vmguest kernel: [81637.006239] clocksource: timekeeping
watchdog on CPU0: kvm-clock retried 2 times before success
Apr 21 11:36:09 vmguest kernel: [82184.581433] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 83678ns
Apr 21 11:36:09 vmguest kernel: [82184.581460] clocksource: wd-tsc-wd
read-back delay of 563812ns, clock-skew test skipped!
Apr 21 11:36:29 vmguest kernel: [82204.452880] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 89818ns
Apr 21 11:36:29 vmguest kernel: [82204.452887] clocksource: wd-tsc-wd
read-back delay of 402807ns, clock-skew test skipped!
Apr 21 11:44:48 vmguest kernel: [82703.403975] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 3750838ns
Apr 21 11:44:48 vmguest kernel: [82703.403986] clocksource: wd-tsc-wd
read-back delay of 6560338ns, clock-skew test skipped!
Apr 21 11:46:50 vmguest kernel: [82825.598483] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success
Apr 22 23:02:20 vmguest kernel: [209755.843767] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 60514ns
Apr 22 23:02:20 vmguest kernel: [209755.847223] clocksource: wd-tsc-wd
read-back delay of 478493ns, clock-skew test skipped!
Apr 22 23:16:51 vmguest kernel: [210626.508444] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 201186ns
Apr 22 23:16:51 vmguest kernel: [210626.540208] clocksource: wd-tsc-wd
read-back delay of 171061ns, clock-skew test skipped!
Apr 27 20:44:11 vmguest kernel: [633467.791962] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 59079ns
Apr 27 20:44:11 vmguest kernel: [633467.797574] clocksource: wd-tsc-wd
read-back delay of 504723ns, clock-skew test skipped!
Apr 30 22:02:23 vmguest kernel: [897359.907926] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 8445232ns
Apr 30 22:02:23 vmguest kernel: [897359.920838] clocksource: wd-tsc-wd
read-back delay of 180997ns, clock-skew test skipped!
--
May  3 11:14:24 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
May  3 11:14:24 vmguest kernel: [    0.000000] Hypervisor detected: KVM
May  3 11:14:24 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
May  3 11:14:24 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
19cba001, primary cpu clock
May  3 11:14:24 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 8027636013 cycles
May  3 11:14:24 vmguest kernel: [    0.000007] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
May  3 11:14:24 vmguest kernel: [    0.186810] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
May  3 11:14:24 vmguest kernel: [    0.186811] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
May  3 11:14:24 vmguest kernel: [    0.186812] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
May  3 11:14:24 vmguest kernel: [    0.186815] [mem 0x40000000-0xfebfffff]
available for PCI devices
May  3 11:14:24 vmguest kernel: [    0.186817] Booting paravirtualized
kernel on KVM
May  3 11:14:24 vmguest kernel: [    0.186823] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
May  3 11:14:24 vmguest kernel: [    0.223610] ACPI: Core revision 20200925
May  3 11:14:24 vmguest kernel: [    0.223896] APIC: Switch to symmetric
I/O mode setup
May  3 11:14:24 vmguest kernel: [    0.224541] x2apic enabled
May  3 11:14:24 vmguest kernel: [    0.225627] Switched APIC routing to
physical x2apic.
May  3 11:14:24 vmguest kernel: [    0.228455] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
May  3 11:14:24 vmguest kernel: [    0.228529] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x159649535e5, max_idle_ns:
440795218057 ns
--
May  3 11:14:24 vmguest kernel: [    0.376492] smpboot: Max logical
packages: 1
May  3 11:14:24 vmguest kernel: [    0.376497] smpboot: Total of 4
processors activated (11980.81 BogoMIPS)
May  3 11:14:24 vmguest kernel: [    0.380536] node 0 deferred pages
initialised in 4ms
May  3 11:14:24 vmguest kernel: [    0.390194] devtmpfs: initialized
May  3 11:14:24 vmguest kernel: [    0.390194] x86/mm: Memory block size:
128MB
May  3 11:14:24 vmguest kernel: [    0.395591] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
May  3 11:14:24 vmguest kernel: [    0.906497] NetLabel:  unlabeled traffic
allowed by default
May  3 11:14:24 vmguest kernel: [    0.906507] PCI: Using ACPI for IRQ
routing
May  3 11:14:24 vmguest kernel: [    0.906511] PCI: pci_cache_line_size set
to 64 bytes
May  3 11:14:24 vmguest kernel: [    0.908560] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
May  3 11:14:24 vmguest kernel: [    0.908574] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
May  3 11:14:24 vmguest kernel: [    0.921046] clocksource: Switched to
clocksource kvm-clock
--
May  3 11:14:24 vmguest kernel: [    0.968046] AppArmor: AppArmor
Filesystem Enabled
May  3 11:14:24 vmguest kernel: [    0.968098] pnp: PnP ACPI init
May  3 11:14:24 vmguest kernel: [    0.968251] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
May  3 11:14:24 vmguest kernel: [    0.968383] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
May  3 11:14:24 vmguest kernel: [    0.969832] pnp: PnP ACPI: found 2
devices
May  3 11:14:24 vmguest kernel: [    0.988561] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
May  3 11:14:24 vmguest kernel: [    0.993743] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
May  3 11:14:24 vmguest kernel: [    0.993827] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
May  3 11:14:24 vmguest kernel: [    0.993931] PCI: CLS 0 bytes, default 64
May  3 11:14:24 vmguest kernel: [    0.994041] Trying to unpack rootfs
image as initramfs...
May  3 11:14:24 vmguest kernel: [    2.343943] Freeing initrd memory:
27520K
May  3 11:14:24 vmguest kernel: [    2.344259] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x159649535e5, max_idle_ns: 440795218057 ns
May  3 11:14:24 vmguest kernel: [    2.375002] clocksource: Switched to
clocksource tsc
--
Jun 30 21:01:59 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jun 30 21:01:59 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Jun 30 21:01:59 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Jun 30 21:01:59 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
25eba001, primary cpu clock
Jun 30 21:01:59 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 10341938108 cycles
Jun 30 21:01:59 vmguest kernel: [    0.000007] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Jun 30 21:01:59 vmguest kernel: [    0.189590] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Jun 30 21:01:59 vmguest kernel: [    0.189591] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Jun 30 21:01:59 vmguest kernel: [    0.189593] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Jun 30 21:01:59 vmguest kernel: [    0.189596] [mem 0x40000000-0xfebfffff]
available for PCI devices
Jun 30 21:01:59 vmguest kernel: [    0.189598] Booting paravirtualized
kernel on KVM
Jun 30 21:01:59 vmguest kernel: [    0.189603] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Jun 30 21:01:59 vmguest kernel: [    0.250266] ACPI: Core revision 20200925
Jun 30 21:01:59 vmguest kernel: [    0.250592] APIC: Switch to symmetric
I/O mode setup
Jun 30 21:01:59 vmguest kernel: [    0.251356] x2apic enabled
Jun 30 21:01:59 vmguest kernel: [    0.252992] Switched APIC routing to
physical x2apic.
Jun 30 21:01:59 vmguest kernel: [    0.262484] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Jun 30 21:01:59 vmguest kernel: [    0.262623] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns:
440795260276 ns
--
Jun 30 21:01:59 vmguest kernel: [    0.413359] smpboot: Max logical
packages: 1
Jun 30 21:01:59 vmguest kernel: [    0.413363] smpboot: Total of 4
processors activated (11980.79 BogoMIPS)
Jun 30 21:01:59 vmguest kernel: [    0.613323] node 0 deferred pages
initialised in 176ms
Jun 30 21:01:59 vmguest kernel: [    0.634645] devtmpfs: initialized
Jun 30 21:01:59 vmguest kernel: [    0.634762] x86/mm: Memory block size:
128MB
Jun 30 21:01:59 vmguest kernel: [    0.639084] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Jun 30 21:01:59 vmguest kernel: [    1.364063] NetLabel:  unlabeled traffic
allowed by default
Jun 30 21:01:59 vmguest kernel: [    1.364063] PCI: Using ACPI for IRQ
routing
Jun 30 21:01:59 vmguest kernel: [    1.364063] PCI: pci_cache_line_size set
to 64 bytes
Jun 30 21:01:59 vmguest kernel: [    1.364063] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Jun 30 21:01:59 vmguest kernel: [    1.364063] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Jun 30 21:01:59 vmguest kernel: [    1.370689] clocksource: Switched to
clocksource kvm-clock
--
Jun 30 21:01:59 vmguest kernel: [    1.394936] AppArmor: AppArmor
Filesystem Enabled
Jun 30 21:01:59 vmguest kernel: [    1.394986] pnp: PnP ACPI init
Jun 30 21:01:59 vmguest kernel: [    1.395301] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Jun 30 21:01:59 vmguest kernel: [    1.395445] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Jun 30 21:01:59 vmguest kernel: [    1.396998] pnp: PnP ACPI: found 2
devices
Jun 30 21:01:59 vmguest kernel: [    1.420613] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Jun 30 21:01:59 vmguest kernel: [    1.454078] pci 0000:00:00.0: Limiting
direct PCI/PCI transfers
Jun 30 21:01:59 vmguest kernel: [    1.454133] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Jun 30 21:01:59 vmguest kernel: [    1.454217] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Jun 30 21:01:59 vmguest kernel: [    1.454348] PCI: CLS 0 bytes, default 64
Jun 30 21:01:59 vmguest kernel: [    1.454508] Trying to unpack rootfs
image as initramfs...
Jun 30 21:01:59 vmguest kernel: [    1.469835] hrtimer: interrupt took
12351564 ns
Jun 30 21:01:59 vmguest kernel: [    4.291644] Freeing initrd memory:
27520K
Jun 30 21:01:59 vmguest kernel: [    4.291948] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns: 440795260276 ns
Jun 30 21:01:59 vmguest kernel: [    4.307314] clocksource: Switched to
clocksource tsc
--
Jun 30 21:01:59 vmguest kernel: [   17.941195] FS-Cache: Netfs 'nfs'
registered for caching
Jun 30 21:01:59 vmguest kernel: [   18.130361] Key type dns_resolver
registered
Jun 30 21:02:01 vmguest kernel: [   19.813667] NFS: Registering the
id_resolver key type
Jun 30 21:02:01 vmguest kernel: [   19.813693] Key type id_resolver
registered
Jun 30 21:02:01 vmguest kernel: [   19.813695] Key type id_legacy
registered
Jun 30 21:03:09 vmguest kernel: [   87.784613] clocksource: timekeeping
watchdog on CPU2: kvm-clock retried 2 times before success
Jun 30 21:04:40 vmguest kernel: [  178.982190] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 578795ns
Jun 30 21:04:40 vmguest kernel: [  179.000189] clocksource: wd-tsc-wd
read-back delay of 837014ns, clock-skew test skipped!
Jun 30 21:05:09 vmguest kernel: [  208.317507] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 119372ns
Jun 30 21:05:09 vmguest kernel: [  208.360377] clocksource: wd-tsc-wd
read-back delay of 168699ns, clock-skew test skipped!
Jun 30 21:08:52 vmguest kernel: [  431.299703] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 408528ns
Jun 30 21:08:52 vmguest kernel: [  431.304386] clocksource: wd-tsc-wd
read-back delay of 396886ns, clock-skew test skipped!
Jun 30 21:10:26 vmguest kernel: [  525.302489] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 82515ns
Jun 30 21:10:26 vmguest kernel: [  525.302494] clocksource: wd-tsc-wd
read-back delay of 501074ns, clock-skew test skipped!
Jun 30 21:10:54 vmguest kernel: [  553.335980] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 179496ns
Jun 30 21:10:54 vmguest kernel: [  553.373937] clocksource: wd-tsc-wd
read-back delay of 168402ns, clock-skew test skipped!
Jun 30 21:12:20 vmguest kernel: [  638.840448] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 397233ns
Jun 30 21:12:20 vmguest kernel: [  638.843377] clocksource: wd-tsc-wd
read-back delay of 731772ns, clock-skew test skipped!
Jun 30 21:12:27 vmguest kernel: [  646.146626] traps: process[689] general
protection fault ip:55d883914160 sp:7fd082f44508 error:0 in
process[55d8838e5000+5a000]
Jun 30 21:13:00 vmguest kernel: [  679.324630] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 8183233ns
Jun 30 21:13:00 vmguest kernel: [  679.332598] clocksource: wd-tsc-wd
read-back delay of 3169836ns, clock-skew test skipped!
Jun 30 21:13:29 vmguest kernel: [  707.784499] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 239688ns
Jun 30 21:13:29 vmguest kernel: [  707.797488] clocksource: wd-tsc-wd
read-back delay of 527820ns, clock-skew test skipped!
Jun 30 21:16:45 vmguest kernel: [  903.785155] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 348363ns
Jun 30 21:16:45 vmguest kernel: [  903.831570] clocksource: wd-tsc-wd
read-back delay of 383978ns, clock-skew test skipped!
Jun 30 21:22:54 vmguest kernel: [ 1273.304614] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success
Jun 30 21:23:29 vmguest kernel: [ 1308.315670] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 372961ns
Jun 30 21:23:29 vmguest kernel: [ 1308.319047] clocksource: wd-tsc-wd
read-back delay of 601431ns, clock-skew test skipped!
Jun 30 21:25:31 vmguest kernel: [ 1430.307990] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 80224ns
Jun 30 21:25:31 vmguest kernel: [ 1430.375623] clocksource: wd-tsc-wd
read-back delay of 316532ns, clock-skew test skipped!
Jun 30 21:26:24 vmguest kernel: [ 1483.314997] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 107978ns
Jun 30 21:26:24 vmguest kernel: [ 1483.319977] clocksource: wd-tsc-wd
read-back delay of 1063977ns, clock-skew test skipped!
Jun 30 21:27:01 vmguest kernel: [ 1520.004507] traps: date[4170] general
protection fault ip:7f7b7280808e sp:7ffe68127fe8 error:0 in
libc-2.31.so[7f7b72797000+14b000]
Jun 30 21:28:37 vmguest kernel: [ 1615.619548] traps: ip[4582] general
protection fault ip:7fc301f254a6 sp:7ffc0b94a970 error:0 in
libc-2.31.so[7fc301f0c000+14b000]
Jun 30 21:34:46 vmguest kernel: [ 1984.789105] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 107544ns
Jun 30 21:34:46 vmguest kernel: [ 1984.813546] clocksource: wd-tsc-wd
read-back delay of 288830ns, clock-skew test skipped!
Jun 30 21:35:32 vmguest kernel: [ 2030.811393] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 70320ns
Jun 30 21:35:32 vmguest kernel: [ 2030.833827] clocksource: wd-tsc-wd
read-back delay of 132567ns, clock-skew test skipped!
Jun 30 21:40:27 vmguest kernel: [ 2325.889568] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 770209ns
Jun 30 21:40:27 vmguest kernel: [ 2325.891732] clocksource: wd-tsc-wd
read-back delay of 1225029ns, clock-skew test skipped!
Jun 30 21:45:41 vmguest kernel: [ 2639.804034] clocksource: timekeeping
watchdog on CPU2: kvm-clock retried 2 times before success
Jun 30 21:49:48 vmguest kernel: [ 2887.309051] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 1628288ns
Jun 30 21:49:48 vmguest kernel: [ 2887.311565] clocksource: wd-tsc-wd
read-back delay of 1204009ns, clock-skew test skipped!
Jun 30 21:50:19 vmguest kernel: [ 2917.811704] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 556027ns
Jun 30 21:50:19 vmguest kernel: [ 2917.847462] clocksource: wd-tsc-wd
read-back delay of 2308381ns, clock-skew test skipped!
Jun 30 21:53:38 vmguest kernel: [ 3117.034133] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 915497ns
Jun 30 21:53:38 vmguest kernel: [ 3117.037870] clocksource: wd-tsc-wd
read-back delay of 2035609ns, clock-skew test skipped!
Jun 30 21:56:11 vmguest kernel: [ 3269.840057] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 2257494ns
Jun 30 21:56:11 vmguest kernel: [ 3269.845014] clocksource: wd-tsc-wd
read-back delay of 582652ns, clock-skew test skipped!
Jun 30 21:57:02 vmguest kernel: [ 3321.362284] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 383947ns
Jun 30 21:57:02 vmguest kernel: [ 3321.363586] clocksource: wd-tsc-wd
read-back delay of 457507ns, clock-skew test skipped!
Jun 30 21:58:04 vmguest kernel: [ 3383.009219] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 262089ns
Jun 30 21:58:04 vmguest kernel: [ 3383.010857] clocksource: wd-tsc-wd
read-back delay of 254042ns, clock-skew test skipped!
Jun 30 22:00:09 vmguest kernel: [ 3507.345591] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 75288ns
Jun 30 22:00:09 vmguest kernel: [ 3507.398513] clocksource: wd-tsc-wd
read-back delay of 1273846ns, clock-skew test skipped!
Jun 30 22:01:28 vmguest kernel: [ 3586.849359] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 3193331ns
Jun 30 22:01:28 vmguest kernel: [ 3586.857097] clocksource: wd-tsc-wd
read-back delay of 1636403ns, clock-skew test skipped!
Jun 30 22:05:52 vmguest kernel: [ 3851.293700] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 192942ns
Jun 30 22:05:52 vmguest kernel: [ 3851.298910] clocksource: wd-tsc-wd
read-back delay of 1230127ns, clock-skew test skipped!
Jun 30 22:08:20 vmguest kernel: [ 3999.288323] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 3 times before success
Jun 30 22:09:03 vmguest kernel: [ 4041.801208] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 313076ns
Jun 30 22:09:03 vmguest kernel: [ 4041.812356] clocksource: wd-tsc-wd
read-back delay of 1140526ns, clock-skew test skipped!
Jun 30 22:12:51 vmguest kernel: [ 4270.245332] process[5263]: segfault at 0
ip 0000000000000000 sp 00007f952bf56768 error 14 in
process[563c1917d000+9000]
Jun 30 22:12:51 vmguest kernel: [ 4270.245358] Code: Unable to access
opcode bytes at RIP 0xffffffffffffffd6.
Jun 30 22:19:20 vmguest kernel: [ 4659.384029] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 1012741ns
Jun 30 22:19:20 vmguest kernel: [ 4659.390576] clocksource: wd-tsc-wd
read-back delay of 709064ns, clock-skew test skipped!
Jun 30 22:22:31 vmguest kernel: [ 4849.853418] clocksource: timekeeping
watchdog on CPU2: kvm-clock retried 2 times before success
Jun 30 22:23:44 vmguest kernel: [ 4922.831918] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 485914ns
Jun 30 22:23:44 vmguest kernel: [ 4922.831973] clocksource: wd-tsc-wd
read-back delay of 3134856ns, clock-skew test skipped!
Jun 30 22:25:28 vmguest kernel: [ 5027.303895] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 179661ns
Jun 30 22:25:28 vmguest kernel: [ 5027.308151] clocksource: wd-tsc-wd
read-back delay of 1370025ns, clock-skew test skipped!
Jun 30 22:26:12 vmguest kernel: [ 5071.335926] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 59176ns
Jun 30 22:26:12 vmguest kernel: [ 5071.338318] clocksource: wd-tsc-wd
read-back delay of 240364ns, clock-skew test skipped!
Jun 30 22:27:18 vmguest kernel: [ 5137.359304] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success
Jun 30 22:29:40 vmguest kernel: [ 5279.369515] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 64295ns
Jun 30 22:29:40 vmguest kernel: [ 5279.377214] clocksource: wd-tsc-wd
read-back delay of 1124748ns, clock-skew test skipped!
Jun 30 22:30:20 vmguest kernel: [ 5318.830518] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 920197ns
Jun 30 22:30:20 vmguest kernel: [ 5318.856871] clocksource: wd-tsc-wd
read-back delay of 161425ns, clock-skew test skipped!
Jun 30 22:32:22 vmguest kernel: [ 5441.323798] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 767172ns
Jun 30 22:32:22 vmguest kernel: [ 5441.363475] clocksource: wd-tsc-wd
read-back delay of 1850770ns, clock-skew test skipped!
Jun 30 22:35:03 vmguest kernel: [ 5601.816784] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 1375051ns
Jun 30 22:35:03 vmguest kernel: [ 5601.835171] clocksource: wd-tsc-wd
read-back delay of 810693ns, clock-skew test skipped!
Jun 30 22:35:28 vmguest kernel: [ 5627.319854] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 121516ns
Jun 30 22:35:28 vmguest kernel: [ 5627.322206] clocksource: wd-tsc-wd
read-back delay of 312780ns, clock-skew test skipped!
Jun 30 22:39:40 vmguest kernel: [ 5879.341388] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 1368929ns
Jun 30 22:39:40 vmguest kernel: [ 5879.346195] clocksource: wd-tsc-wd
read-back delay of 684633ns, clock-skew test skipped!
Jun 30 22:40:52 vmguest kernel: [ 5950.809032] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 516075ns
Jun 30 22:40:52 vmguest kernel: [ 5950.862625] clocksource: wd-tsc-wd
read-back delay of 714249ns, clock-skew test skipped!
Jun 30 22:41:46 vmguest kernel: [ 6005.361862] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 696276ns
Jun 30 22:41:46 vmguest kernel: [ 6005.362987] clocksource: wd-tsc-wd
read-back delay of 516355ns, clock-skew test skipped!
Jun 30 22:42:32 vmguest kernel: [ 6050.809383] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 1092827ns
Jun 30 22:42:32 vmguest kernel: [ 6050.841887] clocksource: wd-tsc-wd
read-back delay of 817399ns, clock-skew test skipped!
Jun 30 22:43:16 vmguest kernel: [ 6095.302508] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 106137ns
Jun 30 22:43:16 vmguest kernel: [ 6095.305197] clocksource: wd-tsc-wd
read-back delay of 876856ns, clock-skew test skipped!
Jun 30 22:43:23 vmguest kernel: [ 6102.293382] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 59403ns
Jun 30 22:43:23 vmguest kernel: [ 6102.316059] clocksource: wd-tsc-wd
read-back delay of 2367027ns, clock-skew test skipped!
Jun 30 22:43:42 vmguest kernel: [ 6121.342025] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 120150ns
Jun 30 22:43:42 vmguest kernel: [ 6121.347952] clocksource: wd-tsc-wd
read-back delay of 469137ns, clock-skew test skipped!
Jun 30 22:46:23 vmguest kernel: [ 6281.852983] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 239400ns
Jun 30 22:46:23 vmguest kernel: [ 6281.875461] clocksource: wd-tsc-wd
read-back delay of 2140900ns, clock-skew test skipped!
Jun 30 22:47:20 vmguest kernel: [ 6339.327714] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 98675ns
Jun 30 22:47:20 vmguest kernel: [ 6339.329957] clocksource: wd-tsc-wd
read-back delay of 936582ns, clock-skew test skipped!
Jun 30 22:49:50 vmguest kernel: [ 6489.373964] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 204606ns
Jun 30 22:49:50 vmguest kernel: [ 6489.377638] clocksource: wd-tsc-wd
read-back delay of 1501457ns, clock-skew test skipped!
Jun 30 22:49:57 vmguest kernel: [ 6496.366813] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 1093355ns
Jun 30 22:49:57 vmguest kernel: [ 6496.366929] clocksource: wd-tsc-wd
read-back delay of 2031940ns, clock-skew test skipped!
Jun 30 22:53:08 vmguest kernel: [ 6687.368566] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 994971ns
Jun 30 22:53:08 vmguest kernel: [ 6687.373583] clocksource: wd-tsc-wd
read-back delay of 825831ns, clock-skew test skipped!
Jun 30 22:57:42 vmguest kernel: [ 6960.794716] clocksource: timekeeping
watchdog on CPU0: kvm-clock retried 2 times before success
Jun 30 22:58:03 vmguest kernel: [ 6982.306088] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 67850ns
Jun 30 22:58:03 vmguest kernel: [ 6982.318780] clocksource: wd-tsc-wd
read-back delay of 348523ns, clock-skew test skipped!
Jun 30 22:58:31 vmguest kernel: [ 7010.293831] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 552868ns
Jun 30 22:58:31 vmguest kernel: [ 7010.304757] clocksource: wd-tsc-wd
read-back delay of 132456ns, clock-skew test skipped!
Jun 30 23:02:52 vmguest kernel: [ 7271.311506] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success
Jun 30 23:04:36 vmguest kernel: [ 7375.359751] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success
Jun 30 23:08:06 vmguest kernel: [ 7585.346684] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 155485ns
Jun 30 23:08:06 vmguest kernel: [ 7585.350818] clocksource: wd-tsc-wd
read-back delay of 108218ns, clock-skew test skipped!
Jun 30 23:08:51 vmguest kernel: [ 7629.833419] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 59550ns
Jun 30 23:08:51 vmguest kernel: [ 7629.851357] clocksource: wd-tsc-wd
read-back delay of 120937ns, clock-skew test skipped!
Jun 30 23:13:17 vmguest kernel: [ 7896.319284] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 172734ns
Jun 30 23:13:17 vmguest kernel: [ 7896.323427] clocksource: wd-tsc-wd
read-back delay of 793429ns, clock-skew test skipped!
Jun 30 23:14:40 vmguest kernel: [ 7978.816508] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 215490ns
Jun 30 23:14:40 vmguest kernel: [ 7978.842370] clocksource: wd-tsc-wd
read-back delay of 1369724ns, clock-skew test skipped!
Jun 30 23:16:36 vmguest kernel: [ 8095.360438] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 444465ns
Jun 30 23:16:36 vmguest kernel: [ 8095.394450] clocksource: wd-tsc-wd
read-back delay of 492421ns, clock-skew test skipped!
Jun 30 23:22:46 vmguest kernel: [ 8465.360835] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 788564ns
Jun 30 23:22:46 vmguest kernel: [ 8465.366064] clocksource: wd-tsc-wd
read-back delay of 628563ns, clock-skew test skipped!
Jun 30 23:28:46 vmguest kernel: [ 8825.372560] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 1741717ns
Jun 30 23:28:46 vmguest kernel: [ 8825.382894] clocksource: wd-tsc-wd
read-back delay of 849530ns, clock-skew test skipped!
Jun 30 23:31:55 vmguest kernel: [ 9013.822794] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 1754007ns
Jun 30 23:31:55 vmguest kernel: [ 9013.838658] clocksource: wd-tsc-wd
read-back delay of 420059ns, clock-skew test skipped!
Jun 30 23:37:09 vmguest kernel: [ 9327.828031] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 815120ns
Jun 30 23:37:09 vmguest kernel: [ 9327.872091] clocksource: wd-tsc-wd
read-back delay of 961182ns, clock-skew test skipped!
Jun 30 23:38:30 vmguest kernel: [ 9408.807541] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 230949ns
Jun 30 23:38:30 vmguest kernel: [ 9408.835431] clocksource: wd-tsc-wd
read-back delay of 1563574ns, clock-skew test skipped!
Jun 30 23:39:18 vmguest kernel: [ 9456.852124] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 191170ns
Jun 30 23:39:18 vmguest kernel: [ 9456.856414] clocksource: wd-tsc-wd
read-back delay of 1033023ns, clock-skew test skipped!
Jun 30 23:40:17 vmguest kernel: [ 9515.867373] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 82993ns
Jun 30 23:40:17 vmguest kernel: [ 9515.868685] clocksource: wd-tsc-wd
read-back delay of 240599ns, clock-skew test skipped!
Jun 30 23:42:54 vmguest kernel: [ 9672.813699] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 399380ns
Jun 30 23:42:54 vmguest kernel: [ 9672.832922] clocksource: wd-tsc-wd
read-back delay of 170307ns, clock-skew test skipped!
Jun 30 23:46:08 vmguest kernel: [ 9866.864948] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 107672ns
Jun 30 23:46:08 vmguest kernel: [ 9866.897564] clocksource: wd-tsc-wd
read-back delay of 1798359ns, clock-skew test skipped!
Jun 30 23:46:38 vmguest kernel: [ 9896.792471] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 155671ns
Jun 30 23:46:38 vmguest kernel: [ 9896.816841] clocksource: wd-tsc-wd
read-back delay of 284106ns, clock-skew test skipped!
Jun 30 23:47:11 vmguest kernel: [ 9930.377178] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 522215ns
Jun 30 23:47:11 vmguest kernel: [ 9930.383734] clocksource: wd-tsc-wd
read-back delay of 455305ns, clock-skew test skipped!
Jun 30 23:49:21 vmguest kernel: [10059.450110] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 83192ns
Jun 30 23:49:21 vmguest kernel: [10059.454133] clocksource: wd-tsc-wd
read-back delay of 457106ns, clock-skew test skipped!
Jun 30 23:50:52 vmguest kernel: [10151.353143] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 52054ns
Jun 30 23:50:52 vmguest kernel: [10151.357720] clocksource: wd-tsc-wd
read-back delay of 115868ns, clock-skew test skipped!
Jun 30 23:56:51 vmguest kernel: [10509.869693] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 469163ns
Jun 30 23:56:51 vmguest kernel: [10509.893278] clocksource: wd-tsc-wd
read-back delay of 4035988ns, clock-skew test skipped!
Jul  1 00:02:30 vmguest kernel: [10848.810138] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 1523178ns
Jul  1 00:02:30 vmguest kernel: [10848.826838] clocksource: wd-tsc-wd
read-back delay of 442502ns, clock-skew test skipped!
Jul  1 00:03:46 vmguest kernel: [10924.808529] clocksource: timekeeping
watchdog on CPU0: kvm-clock retried 2 times before success
Jul  1 00:04:01 vmguest kernel: [10939.471843] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 2307595ns
Jul  1 00:04:01 vmguest kernel: [10939.474126] clocksource: wd-tsc-wd
read-back delay of 1009591ns, clock-skew test skipped!
Jul  1 00:04:50 vmguest kernel: [10988.821470] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 106360ns
Jul  1 00:04:50 vmguest kernel: [10988.836277] clocksource: wd-tsc-wd
read-back delay of 314732ns, clock-skew test skipped!
Jul  1 00:06:36 vmguest kernel: [11094.835457] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 192013ns
Jul  1 00:06:36 vmguest kernel: [11094.860327] clocksource: wd-tsc-wd
read-back delay of 288576ns, clock-skew test skipped!
Jul  1 00:06:55 vmguest kernel: [11113.374043] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 459918ns
Jul  1 00:06:55 vmguest kernel: [11113.377757] clocksource: wd-tsc-wd
read-back delay of 1309199ns, clock-skew test skipped!
Jul  1 00:09:34 vmguest kernel: [11273.401512] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 210891ns
Jul  1 00:09:34 vmguest kernel: [11273.401518] clocksource: wd-tsc-wd
read-back delay of 1398515ns, clock-skew test skipped!
Jul  1 00:11:37 vmguest kernel: [11395.816527] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 325248ns
Jul  1 00:11:37 vmguest kernel: [11395.875321] clocksource: wd-tsc-wd
read-back delay of 1357137ns, clock-skew test skipped!
Jul  1 00:12:45 vmguest kernel: [11464.369745] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 2325534ns
Jul  1 00:12:45 vmguest kernel: [11464.372817] clocksource: wd-tsc-wd
read-back delay of 1742938ns, clock-skew test skipped!
Jul  1 00:14:23 vmguest kernel: [11561.435095] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 158574ns
Jul  1 00:14:23 vmguest kernel: [11561.442408] clocksource: wd-tsc-wd
read-back delay of 810764ns, clock-skew test skipped!
Jul  1 00:14:55 vmguest kernel: [11593.835505] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 612032ns
Jul  1 00:14:55 vmguest kernel: [11593.870752] clocksource: wd-tsc-wd
read-back delay of 493148ns, clock-skew test skipped!
Jul  1 00:15:16 vmguest kernel: [11614.826649] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 119493ns
Jul  1 00:15:16 vmguest kernel: [11614.843927] clocksource: wd-tsc-wd
read-back delay of 979408ns, clock-skew test skipped!
Jul  1 00:20:10 vmguest kernel: [11908.936187] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 130544ns
Jul  1 00:20:10 vmguest kernel: [11908.963742] clocksource: wd-tsc-wd
read-back delay of 662163ns, clock-skew test skipped!
Jul  1 00:21:43 vmguest kernel: [12002.322128] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 1057094ns
Jul  1 00:21:43 vmguest kernel: [12002.341618] clocksource: wd-tsc-wd
read-back delay of 452252ns, clock-skew test skipped!
Jul  1 00:23:56 vmguest kernel: [12134.822624] clocksource: timekeeping
watchdog on CPU0: kvm-clock retried 2 times before success
Jul  1 00:23:59 vmguest kernel: [12138.343342] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 2715683ns
Jul  1 00:23:59 vmguest kernel: [12138.343427] clocksource: wd-tsc-wd
read-back delay of 144726ns, clock-skew test skipped!
Jul  1 00:26:39 vmguest kernel: [12297.826908] clocksource: timekeeping
watchdog on CPU2: kvm-clock retried 2 times before success
Jul  1 00:28:01 vmguest kernel: [12380.336041] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 283615ns
Jul  1 00:28:01 vmguest kernel: [12380.337265] clocksource: wd-tsc-wd
read-back delay of 532258ns, clock-skew test skipped!
Jul  1 00:30:07 vmguest kernel: [12505.398269] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 512341ns
Jul  1 00:30:07 vmguest kernel: [12505.403232] clocksource: wd-tsc-wd
read-back delay of 1621058ns, clock-skew test skipped!
Jul  1 00:35:49 vmguest kernel: [12847.813579] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 107795ns
Jul  1 00:35:49 vmguest kernel: [12847.836807] clocksource: wd-tsc-wd
read-back delay of 168377ns, clock-skew test skipped!
Jul  1 00:36:05 vmguest kernel: [12864.359116] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 1920684ns
Jul  1 00:36:05 vmguest kernel: [12864.404482] clocksource: wd-tsc-wd
read-back delay of 6638467ns, clock-skew test skipped!
Jul  1 00:37:35 vmguest kernel: [12953.890112] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 2432960ns
Jul  1 00:37:35 vmguest kernel: [12953.892004] clocksource: wd-tsc-wd
read-back delay of 1061354ns, clock-skew test skipped!
Jul  1 00:40:32 vmguest kernel: [13130.841499] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 239286ns
Jul  1 00:40:32 vmguest kernel: [13130.861231] clocksource: wd-tsc-wd
read-back delay of 1622448ns, clock-skew test skipped!
Jul  1 00:40:57 vmguest kernel: [13155.434473] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 192709ns
Jul  1 00:40:57 vmguest kernel: [13155.436029] clocksource: wd-tsc-wd
read-back delay of 658472ns, clock-skew test skipped!
Jul  1 00:41:58 vmguest kernel: [13216.814792] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 444586ns
Jul  1 00:41:58 vmguest kernel: [13216.829213] clocksource: wd-tsc-wd
read-back delay of 1105489ns, clock-skew test skipped!
Jul  1 00:42:04 vmguest kernel: [13223.333225] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 930447ns
Jul  1 00:42:04 vmguest kernel: [13223.337598] clocksource: wd-tsc-wd
read-back delay of 987471ns, clock-skew test skipped!
Jul  1 00:42:51 vmguest kernel: [13269.844217] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 95871ns
Jul  1 00:42:51 vmguest kernel: [13269.895542] clocksource: wd-tsc-wd
read-back delay of 768658ns, clock-skew test skipped!
Jul  1 00:43:34 vmguest kernel: [13313.348627] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 317725ns
Jul  1 00:43:34 vmguest kernel: [13313.353416] clocksource: wd-tsc-wd
read-back delay of 349515ns, clock-skew test skipped!
Jul  1 00:44:40 vmguest kernel: [13378.846522] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 4805756ns
Jul  1 00:44:40 vmguest kernel: [13378.858233] clocksource: wd-tsc-wd
read-back delay of 1502829ns, clock-skew test skipped!
Jul  1 00:46:19 vmguest kernel: [13477.859173] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 60272ns
Jul  1 00:46:19 vmguest kernel: [13477.866903] clocksource: wd-tsc-wd
read-back delay of 1236942ns, clock-skew test skipped!
Jul  1 00:46:40 vmguest kernel: [13499.321422] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 119215ns
Jul  1 00:46:40 vmguest kernel: [13499.339395] clocksource: wd-tsc-wd
read-back delay of 132456ns, clock-skew test skipped!
Jul  1 00:53:19 vmguest kernel: [13897.850203] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 120104ns
Jul  1 00:53:19 vmguest kernel: [13897.870827] clocksource: wd-tsc-wd
read-back delay of 506794ns, clock-skew test skipped!
Jul  1 00:53:38 vmguest kernel: [13917.337780] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 766918ns
Jul  1 00:53:38 vmguest kernel: [13917.338066] clocksource: wd-tsc-wd
read-back delay of 1972365ns, clock-skew test skipped!
Jul  1 00:55:15 vmguest kernel: [14013.849372] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 184017ns
Jul  1 00:55:15 vmguest kernel: [14013.876536] clocksource: wd-tsc-wd
read-back delay of 277172ns, clock-skew test skipped!
Jul  1 01:03:42 vmguest kernel: [14520.820699] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 1459292ns
Jul  1 01:03:42 vmguest kernel: [14520.863492] clocksource: wd-tsc-wd
read-back delay of 540571ns, clock-skew test skipped!
Jul  1 01:05:06 vmguest kernel: [14604.814140] clocksource: timekeeping
watchdog on CPU0: kvm-clock retried 2 times before success
Jul  1 01:06:13 vmguest kernel: [14672.357828] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 68934ns
Jul  1 01:06:13 vmguest kernel: [14672.365656] clocksource: wd-tsc-wd
read-back delay of 194683ns, clock-skew test skipped!
Jul  1 01:06:40 vmguest kernel: [14699.347552] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 96071ns
Jul  1 01:06:40 vmguest kernel: [14699.349186] clocksource: wd-tsc-wd
read-back delay of 1454247ns, clock-skew test skipped!
Jul  1 01:07:16 vmguest kernel: [14734.830180] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 685392ns
Jul  1 01:07:16 vmguest kernel: [14734.847582] clocksource: wd-tsc-wd
read-back delay of 287928ns, clock-skew test skipped!
Jul  1 01:08:06 vmguest kernel: [14785.392080] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 817087ns
Jul  1 01:08:06 vmguest kernel: [14785.398021] clocksource: wd-tsc-wd
read-back delay of 348153ns, clock-skew test skipped!
Jul  1 01:08:48 vmguest kernel: [14826.849833] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 4326166ns
Jul  1 01:08:48 vmguest kernel: [14826.883427] clocksource: wd-tsc-wd
read-back delay of 2174687ns, clock-skew test skipped!
Jul  1 01:11:04 vmguest kernel: [14963.338415] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 95959ns
Jul  1 01:11:04 vmguest kernel: [14963.342279] clocksource: wd-tsc-wd
read-back delay of 204435ns, clock-skew test skipped!
Jul  1 01:12:01 vmguest kernel: [15020.351732] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 97036ns
Jul  1 01:12:01 vmguest kernel: [15020.359500] clocksource: wd-tsc-wd
read-back delay of 2185685ns, clock-skew test skipped!
Jul  1 01:14:41 vmguest kernel: [15180.345592] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 163158ns
Jul  1 01:14:41 vmguest kernel: [15180.352191] clocksource: wd-tsc-wd
read-back delay of 341614ns, clock-skew test skipped!
Jul  1 01:19:40 vmguest kernel: [15479.349621] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 1006174ns
Jul  1 01:19:40 vmguest kernel: [15479.353547] clocksource: wd-tsc-wd
read-back delay of 1083746ns, clock-skew test skipped!
Jul  1 01:25:47 vmguest kernel: [15846.325085] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 96017ns
Jul  1 01:25:47 vmguest kernel: [15846.346413] clocksource: wd-tsc-wd
read-back delay of 2103650ns, clock-skew test skipped!
Jul  1 01:26:32 vmguest kernel: [15891.359122] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 499443ns
Jul  1 01:26:32 vmguest kernel: [15891.359132] clocksource: wd-tsc-wd
read-back delay of 148547ns, clock-skew test skipped!
Jul  1 01:26:56 vmguest kernel: [15915.334004] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 71171ns
Jul  1 01:26:56 vmguest kernel: [15915.334100] clocksource: wd-tsc-wd
read-back delay of 2451327ns, clock-skew test skipped!
Jul  1 01:32:41 vmguest kernel: [16260.348782] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 202991ns
Jul  1 01:32:41 vmguest kernel: [16260.378568] clocksource: wd-tsc-wd
read-back delay of 4553589ns, clock-skew test skipped!
Jul  1 01:33:02 vmguest kernel: [16280.470943] traps: cron[9268] general
protection fault ip:7faf8796eb31 sp:7ffc70e2bdb0 error:0 in
ld-2.31.so[7faf87968000+20000]
Jul  1 01:34:33 vmguest kernel: [16371.845616] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 8166037ns
Jul  1 01:34:33 vmguest kernel: [16371.849348] clocksource: wd-tsc-wd
read-back delay of 1790520ns, clock-skew test skipped!
Jul  1 01:40:44 vmguest kernel: [16742.855607] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 155626ns
Jul  1 01:40:44 vmguest kernel: [16742.894869] clocksource: wd-tsc-wd
read-back delay of 205173ns, clock-skew test skipped!
Jul  1 01:41:11 vmguest kernel: [16769.865249] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 58853ns
Jul  1 01:41:11 vmguest kernel: [16769.865369] clocksource: wd-tsc-wd
read-back delay of 108483ns, clock-skew test skipped!
Jul  1 01:43:22 vmguest kernel: [16900.853182] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 1512930ns
Jul  1 01:43:22 vmguest kernel: [16900.869751] clocksource: wd-tsc-wd
read-back delay of 192709ns, clock-skew test skipped!
Jul  1 01:46:29 vmguest kernel: [17087.845943] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 167783ns
Jul  1 01:46:29 vmguest kernel: [17087.888979] clocksource: wd-tsc-wd
read-back delay of 180675ns, clock-skew test skipped!
Jul  1 01:46:32 vmguest kernel: [17091.361851] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 70201ns
Jul  1 01:46:32 vmguest kernel: [17091.367773] clocksource: wd-tsc-wd
read-back delay of 2427230ns, clock-skew test skipped!
Jul  1 01:49:18 vmguest kernel: [17257.410887] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success
Jul  1 01:52:07 vmguest kernel: [17426.380250] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 2735544ns
Jul  1 01:52:07 vmguest kernel: [17426.398142] clocksource: wd-tsc-wd
read-back delay of 2549175ns, clock-skew test skipped!
Jul  1 02:01:57 vmguest kernel: [18016.350497] clocksource: timekeeping
watchdog on CPU3: kvm-clock wd-wd read-back delay of 68017ns
Jul  1 02:01:57 vmguest kernel: [18016.374603] clocksource: wd-tsc-wd
read-back delay of 1781847ns, clock-skew test skipped!
Jul  1 02:03:04 vmguest kernel: [18083.400192] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 1242868ns
Jul  1 02:03:04 vmguest kernel: [18083.402788] clocksource: wd-tsc-wd
read-back delay of 867305ns, clock-skew test skipped!
Jul  1 02:03:14 vmguest kernel: [18092.890879] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 824566ns
Jul  1 02:03:14 vmguest kernel: [18092.894309] clocksource: wd-tsc-wd
read-back delay of 504845ns, clock-skew test skipped!
Jul  1 02:03:41 vmguest kernel: [18119.833978] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 300528ns
Jul  1 02:03:41 vmguest kernel: [18119.834673] clocksource: wd-tsc-wd
read-back delay of 660875ns, clock-skew test skipped!
Jul  1 02:03:52 vmguest kernel: [18131.374865] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 78775ns
Jul  1 02:03:52 vmguest kernel: [18131.376850] clocksource: wd-tsc-wd
read-back delay of 492273ns, clock-skew test skipped!
Jul  1 02:15:53 vmguest kernel: [18851.879342] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 312387ns
Jul  1 02:15:53 vmguest kernel: [18851.906406] clocksource: wd-tsc-wd
read-back delay of 600699ns, clock-skew test skipped!
Jul  1 02:16:55 vmguest kernel: [18913.893285] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 60541ns
Jul  1 02:16:55 vmguest kernel: [18913.897521] clocksource: wd-tsc-wd
read-back delay of 311194ns, clock-skew test skipped!
Jul  1 02:17:14 vmguest kernel: [18933.349431] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 119667ns
Jul  1 02:17:14 vmguest kernel: [18933.351246] clocksource: wd-tsc-wd
read-back delay of 552001ns, clock-skew test skipped!
Jul  1 02:17:30 vmguest kernel: [18949.344389] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 985687ns
Jul  1 02:17:30 vmguest kernel: [18949.344400] clocksource: wd-tsc-wd
read-back delay of 1777485ns, clock-skew test skipped!
Jul  1 02:17:49 vmguest kernel: [18967.831603] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 422241ns
Jul  1 02:17:49 vmguest kernel: [18967.846596] clocksource: wd-tsc-wd
read-back delay of 406710ns, clock-skew test skipped!
Jul  1 02:18:33 vmguest kernel: [19011.835143] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 71859ns
Jul  1 02:18:33 vmguest kernel: [19011.856119] clocksource: wd-tsc-wd
read-back delay of 948939ns, clock-skew test skipped!
--
Jul  1 07:58:35 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jul  1 07:58:35 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Jul  1 07:58:35 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Jul  1 07:58:35 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
72b8001, primary cpu clock
Jul  1 07:58:35 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 7168663791 cycles
Jul  1 07:58:35 vmguest kernel: [    0.000007] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Jul  1 07:58:35 vmguest kernel: [    0.193911] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Jul  1 07:58:35 vmguest kernel: [    0.193913] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Jul  1 07:58:35 vmguest kernel: [    0.193914] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Jul  1 07:58:35 vmguest kernel: [    0.193917] [mem 0x40000000-0xfebfffff]
available for PCI devices
Jul  1 07:58:35 vmguest kernel: [    0.193919] Booting paravirtualized
kernel on KVM
Jul  1 07:58:35 vmguest kernel: [    0.193924] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Jul  1 07:58:35 vmguest kernel: [    0.235615] ACPI: Core revision 20200925
Jul  1 07:58:35 vmguest kernel: [    0.235909] APIC: Switch to symmetric
I/O mode setup
Jul  1 07:58:35 vmguest kernel: [    0.236550] x2apic enabled
Jul  1 07:58:35 vmguest kernel: [    0.237155] Switched APIC routing to
physical x2apic.
Jul  1 07:58:35 vmguest kernel: [    0.240099] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Jul  1 07:58:35 vmguest kernel: [    0.240212] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns:
440795260276 ns
--
Jul  1 07:58:35 vmguest kernel: [    0.380644] smpboot: Max logical
packages: 1
Jul  1 07:58:35 vmguest kernel: [    0.380647] smpboot: Total of 4
processors activated (11980.79 BogoMIPS)
Jul  1 07:58:35 vmguest kernel: [    0.388983] node 0 deferred pages
initialised in 8ms
Jul  1 07:58:35 vmguest kernel: [    0.392245] devtmpfs: initialized
Jul  1 07:58:35 vmguest kernel: [    0.392420] x86/mm: Memory block size:
128MB
Jul  1 07:58:35 vmguest kernel: [    0.392840] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Jul  1 07:58:35 vmguest kernel: [    0.826018] NetLabel:  unlabeled traffic
allowed by default
Jul  1 07:58:35 vmguest kernel: [    0.826018] PCI: Using ACPI for IRQ
routing
Jul  1 07:58:35 vmguest kernel: [    0.826018] PCI: pci_cache_line_size set
to 64 bytes
Jul  1 07:58:35 vmguest kernel: [    0.828480] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Jul  1 07:58:35 vmguest kernel: [    0.828491] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Jul  1 07:58:35 vmguest kernel: [    0.832747] clocksource: Switched to
clocksource kvm-clock
--
Jul  1 07:58:35 vmguest kernel: [    0.878114] AppArmor: AppArmor
Filesystem Enabled
Jul  1 07:58:35 vmguest kernel: [    0.878171] pnp: PnP ACPI init
Jul  1 07:58:35 vmguest kernel: [    0.878316] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Jul  1 07:58:35 vmguest kernel: [    0.878454] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Jul  1 07:58:35 vmguest kernel: [    0.879696] pnp: PnP ACPI: found 2
devices
Jul  1 07:58:35 vmguest kernel: [    0.887217] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Jul  1 07:58:35 vmguest kernel: [    0.889158] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Jul  1 07:58:35 vmguest kernel: [    0.889257] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Jul  1 07:58:35 vmguest kernel: [    0.889361] PCI: CLS 0 bytes, default 64
Jul  1 07:58:35 vmguest kernel: [    0.889612] Trying to unpack rootfs
image as initramfs...
Jul  1 07:58:35 vmguest kernel: [    1.671754] Freeing initrd memory:
27504K
Jul  1 07:58:35 vmguest kernel: [    1.673153] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns: 440795260276 ns
Jul  1 07:58:35 vmguest kernel: [    1.688782] clocksource: Switched to
clocksource tsc
--
Jul  1 07:58:36 vmguest kernel: [    9.386609] FS-Cache: Netfs 'nfs'
registered for caching
Jul  1 07:58:36 vmguest kernel: [    9.454922] Key type dns_resolver
registered
Jul  1 07:58:37 vmguest kernel: [   10.810544] NFS: Registering the
id_resolver key type
Jul  1 07:58:37 vmguest kernel: [   10.810570] Key type id_resolver
registered
Jul  1 07:58:37 vmguest kernel: [   10.810571] Key type id_legacy
registered
Jul  1 10:09:44 vmguest kernel: [ 7877.487994] traps: process[719] general
protection fault ip:55f1891774e7 sp:7fb933e28ac8 error:0 in
process[55f18913b000+5a000]
Jul  1 10:23:16 vmguest kernel: [ 8689.779793] hrtimer: interrupt took
78745848 ns
Jul  1 10:32:56 vmguest kernel: [ 9269.507219] traps: process[3943] general
protection fault ip:55b1448024e7 sp:7f5f9d3c8ac8 error:0 in
process[55b1447c6000+5a000]
Jul  1 10:38:15 vmguest kernel: [ 9588.369110] traps: process[4061] general
protection fault ip:556ae90a54e7 sp:7fedb2487ac8 error:0 in
process[556ae9069000+5a000]
Jul  1 10:54:48 vmguest kernel: [10581.188483] process[4203]: segfault at 0
ip 0000000000000000 sp 00007f6b003b7658 error 14 in
process[5571fc184000+9000]
Jul  1 10:54:48 vmguest kernel: [10581.188505] Code: Unable to access
opcode bytes at RIP 0xffffffffffffffd6.
Jul  1 11:20:27 vmguest kernel: [12120.884271] traps: process[4571] general
protection fault ip:556c66e894e7 sp:7f418a0f7ac8 error:0 in
process[556c66e4d000+5a000]
Jul  1 11:24:13 vmguest kernel: [12346.124249] traps: process[4963] general
protection fault ip:7f8f63af091a sp:7f8f626cd788 error:0 in
libc-2.31.so[7f8f63a6e000+14b000]
Jul  1 11:35:52 vmguest kernel: [13045.319887] traps: process[5064] general
protection fault ip:55edcbde44e7 sp:7fa25d722ac8 error:0 in
process[55edcbda8000+5a000]
Jul  1 11:44:55 vmguest kernel: [13588.048714] traps: process[5299] general
protection fault ip:55c0fdf704e7 sp:7fdc03490ac8 error:0 in
process[55c0fdf34000+5a000]
--
Jul  1 20:26:23 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jul  1 20:26:23 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Jul  1 20:26:23 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Jul  1 20:26:23 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
134b8001, primary cpu clock
Jul  1 20:26:23 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 14912134068 cycles
Jul  1 20:26:23 vmguest kernel: [    0.000007] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Jul  1 20:26:23 vmguest kernel: [    0.727190] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Jul  1 20:26:23 vmguest kernel: [    0.727191] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Jul  1 20:26:23 vmguest kernel: [    0.727193] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Jul  1 20:26:23 vmguest kernel: [    0.727195] [mem 0x40000000-0xfebfffff]
available for PCI devices
Jul  1 20:26:23 vmguest kernel: [    0.727197] Booting paravirtualized
kernel on KVM
Jul  1 20:26:23 vmguest kernel: [    0.727320] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Jul  1 20:26:23 vmguest kernel: [    0.787528] ACPI: Core revision 20200925
Jul  1 20:26:23 vmguest kernel: [    0.787842] APIC: Switch to symmetric
I/O mode setup
Jul  1 20:26:23 vmguest kernel: [    0.788493] x2apic enabled
Jul  1 20:26:23 vmguest kernel: [    0.789099] Switched APIC routing to
physical x2apic.
Jul  1 20:26:23 vmguest kernel: [    0.796040] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Jul  1 20:26:23 vmguest kernel: [    0.796296] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns:
440795260276 ns
--
Jul  1 20:26:23 vmguest kernel: [    0.952639] smpboot: Max logical
packages: 1
Jul  1 20:26:23 vmguest kernel: [    0.952643] smpboot: Total of 4
processors activated (11980.79 BogoMIPS)
Jul  1 20:26:23 vmguest kernel: [    0.956375] node 0 deferred pages
initialised in 4ms
Jul  1 20:26:23 vmguest kernel: [    0.967549] devtmpfs: initialized
Jul  1 20:26:23 vmguest kernel: [    0.967549] x86/mm: Memory block size:
128MB
Jul  1 20:26:23 vmguest kernel: [    0.968571] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Jul  1 20:26:23 vmguest kernel: [    1.568811] NetLabel:  unlabeled traffic
allowed by default
Jul  1 20:26:23 vmguest kernel: [    1.568822] PCI: Using ACPI for IRQ
routing
Jul  1 20:26:23 vmguest kernel: [    1.568827] PCI: pci_cache_line_size set
to 64 bytes
Jul  1 20:26:23 vmguest kernel: [    1.569124] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Jul  1 20:26:23 vmguest kernel: [    1.569137] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Jul  1 20:26:23 vmguest kernel: [    1.594369] clocksource: Switched to
clocksource kvm-clock
--
Jul  1 20:26:23 vmguest kernel: [    1.631005] AppArmor: AppArmor
Filesystem Enabled
Jul  1 20:26:23 vmguest kernel: [    1.631005] pnp: PnP ACPI init
Jul  1 20:26:23 vmguest kernel: [    1.631005] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Jul  1 20:26:23 vmguest kernel: [    1.635841] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Jul  1 20:26:23 vmguest kernel: [    1.637291] pnp: PnP ACPI: found 2
devices
Jul  1 20:26:23 vmguest kernel: [    1.644968] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Jul  1 20:26:23 vmguest kernel: [    1.646983] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Jul  1 20:26:23 vmguest kernel: [    1.647070] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Jul  1 20:26:23 vmguest kernel: [    1.647175] PCI: CLS 0 bytes, default 64
Jul  1 20:26:23 vmguest kernel: [    1.647795] Trying to unpack rootfs
image as initramfs...
Jul  1 20:26:23 vmguest kernel: [    3.146354] Freeing initrd memory:
27504K
Jul  1 20:26:23 vmguest kernel: [    3.146732] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns: 440795260276 ns
Jul  1 20:26:23 vmguest kernel: [    3.167934] clocksource: Switched to
clocksource tsc
--
Jul  1 20:26:27 vmguest kernel: [   21.753760] Key type dns_resolver
registered
Jul  1 20:26:27 vmguest kernel: [   21.985796] SSE version of gcm_enc/dec
engaged.
Jul  1 20:26:30 vmguest kernel: [   25.635891] NFS: Registering the
id_resolver key type
Jul  1 20:26:30 vmguest kernel: [   25.635913] Key type id_resolver
registered
Jul  1 20:26:30 vmguest kernel: [   25.635915] Key type id_legacy
registered
Jul  1 20:44:49 vmguest kernel: [ 1122.778254] hrtimer: interrupt took
21312191 ns
Jul  1 20:45:20 vmguest kernel: [ 1153.481850] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 816732ns
Jul  1 20:45:20 vmguest kernel: [ 1153.505218] clocksource: wd-tsc-wd
read-back delay of 2540783ns, clock-skew test skipped!
Jul  1 20:45:28 vmguest kernel: [ 1161.842047] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 168857ns
Jul  1 20:45:28 vmguest kernel: [ 1161.876024] clocksource: wd-tsc-wd
read-back delay of 2006203ns, clock-skew test skipped!
Jul  1 21:02:39 vmguest kernel: [ 2192.520914] traps: process[718] general
protection fault ip:55e3b4d8f4e7 sp:7f5d538f2ac8 error:0 in
process[55e3b4d53000+5a000]
Jul  1 21:08:09 vmguest kernel: [ 2522.943899] process[2615]: segfault at
7f03bd7439fc ip 0000563e4cfb2516 sp 00007f00b447d1d0 error 4 in
process[563e4cf80000+5a000]
Jul  1 21:08:09 vmguest kernel: [ 2522.943930] Code: 00 29 d0 41 b8 ff ff
ff ff 39 c3 7c 73 41 b8 01 00 00 00 7f 6b 41 8b 0c 24 49 8b 45 48 41 b8 ff
ff ff ff 48 89 ca 48 c1 e2 05 <0f> be 74 10 1c 8b 55 00 48 89 d7 48 c1 e7
05 0f be 44 38 1c 39 c6
Jul  1 21:11:54 vmguest kernel: [ 2747.965445] process[2701]: segfault at 0
ip 0000000000000000 sp 00007f4df279c658 error 14 in
process[557b61431000+9000]
Jul  1 21:11:54 vmguest kernel: [ 2747.965469] Code: Unable to access
opcode bytes at RIP 0xffffffffffffffd6.
Jul  1 21:12:17 vmguest kernel: [ 2771.354679] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 121427ns
Jul  1 21:12:17 vmguest kernel: [ 2771.362213] clocksource: wd-tsc-wd
read-back delay of 1728686ns, clock-skew test skipped!
Jul  1 21:13:33 vmguest kernel: [ 2847.347122] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 337854ns
Jul  1 21:13:33 vmguest kernel: [ 2847.348329] clocksource: wd-tsc-wd
read-back delay of 1510376ns, clock-skew test skipped!
Jul  3 10:24:36 vmguest kernel: [136710.299609] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 3126200ns
Jul  3 10:24:36 vmguest kernel: [136710.342833] clocksource: wd-tsc-wd
read-back delay of 1013098ns, clock-skew test skipped!
Jul  3 10:28:34 vmguest kernel: [136948.296385] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 2221183ns
Jul  3 10:28:34 vmguest kernel: [136948.307494] clocksource: wd-tsc-wd
read-back delay of 1249549ns, clock-skew test skipped!
Jul  3 10:29:13 vmguest kernel: [136986.863003] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 740917ns
Jul  3 10:29:13 vmguest kernel: [136986.885208] clocksource: wd-tsc-wd
read-back delay of 175868ns, clock-skew test skipped!
Jul  3 14:36:16 vmguest kernel: [151810.335013] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 879027ns
Jul  3 14:36:16 vmguest kernel: [151810.342617] clocksource: wd-tsc-wd
read-back delay of 1475323ns, clock-skew test skipped!
Jul  3 14:37:42 vmguest kernel: [151896.090179] pps_core: LinuxPPS API ver.
1 registered
Jul  3 14:37:42 vmguest kernel: [151896.090188] pps_core: Software ver.
5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Jul  3 14:37:42 vmguest kernel: [151896.101503] PTP clock support
registered
Jul  3 15:07:57 vmguest kernel: [153711.899736] process[2864]: segfault at
0 ip 0000000000000000 sp 00007f0f75427658 error 14 in
process[55a7d7e94000+9000]
Jul  3 15:07:57 vmguest kernel: [153711.899757] Code: Unable to access
opcode bytes at RIP 0xffffffffffffffd6.
Jul  3 16:15:18 vmguest kernel: [157752.746539] process[37321]: segfault at
0 ip 0000000000000000 sp 00007fc89814b658 error 14 in
process[55f700733000+9000]
Jul  3 16:15:18 vmguest kernel: [157752.746560] Code: Unable to access
opcode bytes at RIP 0xffffffffffffffd6.
Jul  3 17:07:02 vmguest kernel: [160855.984816] traps: wget[38778] general
protection fault ip:7f6554626fda sp:7ffcebba2bb0 error:0 in
libtasn1.so.6.6.0[7f655461d000+c000]
Jul  3 17:42:01 vmguest kernel: [162955.828062] traps: wget[39180] general
protection fault ip:7f51272f5a97 sp:7fffd42e7850 error:0 in
libtasn1.so.6.6.0[7f51272f0000+c000]
Jul  3 18:28:01 vmguest kernel: [165715.700332] traps: wget[39732] general
protection fault ip:7ffaaa2cc73c sp:7ffce5cde140 error:0 in
libc-2.31.so[7ffaaa267000+14b000]
--
Jul  3 22:19:00 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jul  3 22:19:00 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Jul  3 22:19:00 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Jul  3 22:19:00 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
3e2ba001, primary cpu clock
Jul  3 22:19:00 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 5273953584 cycles
Jul  3 22:19:00 vmguest kernel: [    0.000007] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Jul  3 22:19:00 vmguest kernel: [    0.183631] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Jul  3 22:19:00 vmguest kernel: [    0.183633] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Jul  3 22:19:00 vmguest kernel: [    0.183634] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Jul  3 22:19:00 vmguest kernel: [    0.183637] [mem 0x40000000-0xfebfffff]
available for PCI devices
Jul  3 22:19:00 vmguest kernel: [    0.183639] Booting paravirtualized
kernel on KVM
Jul  3 22:19:00 vmguest kernel: [    0.183645] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Jul  3 22:19:00 vmguest kernel: [    0.219741] ACPI: Core revision 20200925
Jul  3 22:19:00 vmguest kernel: [    0.220024] APIC: Switch to symmetric
I/O mode setup
Jul  3 22:19:00 vmguest kernel: [    0.220656] x2apic enabled
Jul  3 22:19:00 vmguest kernel: [    0.221253] Switched APIC routing to
physical x2apic.
Jul  3 22:19:00 vmguest kernel: [    0.223987] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Jul  3 22:19:00 vmguest kernel: [    0.224057] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns:
440795260276 ns
--
Jul  3 22:19:00 vmguest kernel: [    0.347221] smpboot: Max logical
packages: 1
Jul  3 22:19:00 vmguest kernel: [    0.347221] smpboot: Total of 4
processors activated (11980.79 BogoMIPS)
Jul  3 22:19:00 vmguest kernel: [    0.349635] node 0 deferred pages
initialised in 8ms
Jul  3 22:19:00 vmguest kernel: [    0.352635] devtmpfs: initialized
Jul  3 22:19:00 vmguest kernel: [    0.352635] x86/mm: Memory block size:
128MB
Jul  3 22:19:00 vmguest kernel: [    0.356353] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Jul  3 22:19:00 vmguest kernel: [    0.704674] NetLabel:  unlabeled traffic
allowed by default
Jul  3 22:19:00 vmguest kernel: [    0.704674] PCI: Using ACPI for IRQ
routing
Jul  3 22:19:00 vmguest kernel: [    0.704674] PCI: pci_cache_line_size set
to 64 bytes
Jul  3 22:19:00 vmguest kernel: [    0.704821] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Jul  3 22:19:00 vmguest kernel: [    0.704832] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Jul  3 22:19:00 vmguest kernel: [    0.709816] clocksource: Switched to
clocksource kvm-clock
--
Jul  3 22:19:00 vmguest kernel: [    0.729824] AppArmor: AppArmor
Filesystem Enabled
Jul  3 22:19:00 vmguest kernel: [    0.729867] pnp: PnP ACPI init
Jul  3 22:19:00 vmguest kernel: [    0.730002] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Jul  3 22:19:00 vmguest kernel: [    0.730155] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Jul  3 22:19:00 vmguest kernel: [    0.731454] pnp: PnP ACPI: found 2
devices
Jul  3 22:19:00 vmguest kernel: [    0.751003] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Jul  3 22:19:00 vmguest kernel: [    0.753320] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Jul  3 22:19:00 vmguest kernel: [    0.753402] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Jul  3 22:19:00 vmguest kernel: [    0.753503] PCI: CLS 0 bytes, default 64
Jul  3 22:19:00 vmguest kernel: [    0.753609] Trying to unpack rootfs
image as initramfs...
Jul  3 22:19:00 vmguest kernel: [    1.496196] Freeing initrd memory:
27520K
Jul  3 22:19:00 vmguest kernel: [    1.496387] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns: 440795260276 ns
Jul  3 22:19:00 vmguest kernel: [    1.511322] clocksource: Switched to
clocksource tsc
--
Jul  3 22:19:02 vmguest kernel: [    9.318232] Key type id_resolver
registered
Jul  3 22:19:02 vmguest kernel: [    9.318233] Key type id_legacy
registered
Jul  3 22:20:33 vmguest kernel: [  100.820186] pps_core: LinuxPPS API ver.
1 registered
Jul  3 22:20:33 vmguest kernel: [  100.820191] pps_core: Software ver.
5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
Jul  3 22:20:33 vmguest kernel: [  100.839668] PTP clock support registered
Jul  3 22:26:30 vmguest kernel: [  457.762609] traps: process[718] general
protection fault ip:5654377624e7 sp:7f2848632ac8 error:0 in
process[565437726000+5a000]
--
Jul  3 22:28:18 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jul  3 22:28:18 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Jul  3 22:28:18 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Jul  3 22:28:18 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
22eb8001, primary cpu clock
Jul  3 22:28:18 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 5161541587 cycles
Jul  3 22:28:18 vmguest kernel: [    0.000006] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Jul  3 22:28:18 vmguest kernel: [    0.183056] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Jul  3 22:28:18 vmguest kernel: [    0.183057] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Jul  3 22:28:18 vmguest kernel: [    0.183059] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Jul  3 22:28:18 vmguest kernel: [    0.183062] [mem 0x40000000-0xfebfffff]
available for PCI devices
Jul  3 22:28:18 vmguest kernel: [    0.183064] Booting paravirtualized
kernel on KVM
Jul  3 22:28:18 vmguest kernel: [    0.183069] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Jul  3 22:28:18 vmguest kernel: [    0.220713] ACPI: Core revision 20200925
Jul  3 22:28:18 vmguest kernel: [    0.221038] APIC: Switch to symmetric
I/O mode setup
Jul  3 22:28:18 vmguest kernel: [    0.221850] x2apic enabled
Jul  3 22:28:18 vmguest kernel: [    0.222434] Switched APIC routing to
physical x2apic.
Jul  3 22:28:18 vmguest kernel: [    0.225164] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Jul  3 22:28:18 vmguest kernel: [    0.225233] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns:
440795260276 ns
--
Jul  3 22:28:18 vmguest kernel: [    0.349948] smpboot: Max logical
packages: 1
Jul  3 22:28:18 vmguest kernel: [    0.349951] smpboot: Total of 4
processors activated (11980.79 BogoMIPS)
Jul  3 22:28:18 vmguest kernel: [    0.354358] node 0 deferred pages
initialised in 4ms
Jul  3 22:28:18 vmguest kernel: [    0.357282] devtmpfs: initialized
Jul  3 22:28:18 vmguest kernel: [    0.357396] x86/mm: Memory block size:
128MB
Jul  3 22:28:18 vmguest kernel: [    0.357841] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Jul  3 22:28:18 vmguest kernel: [    0.717718] NetLabel:  unlabeled traffic
allowed by default
Jul  3 22:28:18 vmguest kernel: [    0.717729] PCI: Using ACPI for IRQ
routing
Jul  3 22:28:18 vmguest kernel: [    0.717733] PCI: pci_cache_line_size set
to 64 bytes
Jul  3 22:28:18 vmguest kernel: [    0.718000] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Jul  3 22:28:18 vmguest kernel: [    0.718011] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Jul  3 22:28:18 vmguest kernel: [    0.721663] clocksource: Switched to
clocksource kvm-clock
--
Jul  3 22:28:18 vmguest kernel: [    0.744156] AppArmor: AppArmor
Filesystem Enabled
Jul  3 22:28:18 vmguest kernel: [    0.744197] pnp: PnP ACPI init
Jul  3 22:28:18 vmguest kernel: [    0.744332] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Jul  3 22:28:18 vmguest kernel: [    0.744481] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Jul  3 22:28:18 vmguest kernel: [    0.746025] pnp: PnP ACPI: found 2
devices
Jul  3 22:28:18 vmguest kernel: [    0.767316] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Jul  3 22:28:18 vmguest kernel: [    0.769404] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Jul  3 22:28:18 vmguest kernel: [    0.769491] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Jul  3 22:28:18 vmguest kernel: [    0.769616] PCI: CLS 0 bytes, default 64
Jul  3 22:28:18 vmguest kernel: [    0.769744] Trying to unpack rootfs
image as initramfs...
Jul  3 22:28:18 vmguest kernel: [    1.501297] Freeing initrd memory:
27504K
Jul  3 22:28:18 vmguest kernel: [    1.501297] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns: 440795260276 ns
Jul  3 22:28:18 vmguest kernel: [    1.521406] clocksource: Switched to
clocksource tsc
--
Jul  3 22:28:19 vmguest kernel: [    8.081123] FS-Cache: Netfs 'nfs'
registered for caching
Jul  3 22:28:19 vmguest kernel: [    8.192308] Key type dns_resolver
registered
Jul  3 22:28:19 vmguest kernel: [    8.882064] NFS: Registering the
id_resolver key type
Jul  3 22:28:19 vmguest kernel: [    8.882090] Key type id_resolver
registered
Jul  3 22:28:19 vmguest kernel: [    8.882091] Key type id_legacy
registered
Jul  4 17:34:00 vmguest kernel: [68751.386157] hrtimer: interrupt took
5764268 ns
--
Jul  5 10:22:57 vmguest kernel: [    0.000000] DMI: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Jul  5 10:22:57 vmguest kernel: [    0.000000] Hypervisor detected: KVM
Jul  5 10:22:57 vmguest kernel: [    0.000000] kvm-clock: Using msrs
4b564d01 and 4b564d00
Jul  5 10:22:57 vmguest kernel: [    0.000000] kvm-clock: cpu 0, msr
2b2b8001, primary cpu clock
Jul  5 10:22:57 vmguest kernel: [    0.000002] kvm-clock: using sched
offset of 15619416672 cycles
Jul  5 10:22:57 vmguest kernel: [    0.000008] clocksource: kvm-clock:
mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns:
881590591483 ns
--
Jul  5 10:22:57 vmguest kernel: [    0.986500] PM: hibernation: Registered
nosave memory: [mem 0x0009f000-0x0009ffff]
Jul  5 10:22:57 vmguest kernel: [    0.986501] PM: hibernation: Registered
nosave memory: [mem 0x000a0000-0x000effff]
Jul  5 10:22:57 vmguest kernel: [    0.986503] PM: hibernation: Registered
nosave memory: [mem 0x000f0000-0x000fffff]
Jul  5 10:22:57 vmguest kernel: [    0.986506] [mem 0x40000000-0xfebfffff]
available for PCI devices
Jul  5 10:22:57 vmguest kernel: [    0.986508] Booting paravirtualized
kernel on KVM
Jul  5 10:22:57 vmguest kernel: [    0.986513] clocksource:
refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:
7645519600211568 ns
--
Jul  5 10:22:57 vmguest kernel: [    1.055618] ACPI: Core revision 20200925
Jul  5 10:22:57 vmguest kernel: [    1.055886] APIC: Switch to symmetric
I/O mode setup
Jul  5 10:22:57 vmguest kernel: [    1.056514] x2apic enabled
Jul  5 10:22:57 vmguest kernel: [    1.059337] Switched APIC routing to
physical x2apic.
Jul  5 10:22:57 vmguest kernel: [    1.067569] ..TIMER: vector=0x30 apic1=0
pin1=2 apic2=-1 pin2=-1
Jul  5 10:22:57 vmguest kernel: [    1.067689] clocksource: tsc-early:
mask: 0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns:
440795260276 ns
--
Jul  5 10:22:57 vmguest kernel: [    1.241040] smpboot: Max logical
packages: 1
Jul  5 10:22:57 vmguest kernel: [    1.241045] smpboot: Total of 4
processors activated (11980.79 BogoMIPS)
Jul  5 10:22:57 vmguest kernel: [    1.249932] node 0 deferred pages
initialised in 8ms
Jul  5 10:22:57 vmguest kernel: [    1.263895] devtmpfs: initialized
Jul  5 10:22:57 vmguest kernel: [    1.263905] x86/mm: Memory block size:
128MB
Jul  5 10:22:57 vmguest kernel: [    1.272181] clocksource: jiffies: mask:
0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
--
Jul  5 10:22:57 vmguest kernel: [    2.260539] NetLabel:  unlabeled traffic
allowed by default
Jul  5 10:22:57 vmguest kernel: [    2.260539] PCI: Using ACPI for IRQ
routing
Jul  5 10:22:57 vmguest kernel: [    2.260539] PCI: pci_cache_line_size set
to 64 bytes
Jul  5 10:22:57 vmguest kernel: [    2.260580] e820: reserve RAM buffer
[mem 0x0009fc00-0x0009ffff]
Jul  5 10:22:57 vmguest kernel: [    2.260676] e820: reserve RAM buffer
[mem 0x3fff0000-0x3fffffff]
Jul  5 10:22:57 vmguest kernel: [    2.268706] clocksource: Switched to
clocksource kvm-clock
--
Jul  5 10:22:57 vmguest kernel: [    2.326569] AppArmor: AppArmor
Filesystem Enabled
Jul  5 10:22:57 vmguest kernel: [    2.328370] pnp: PnP ACPI init
Jul  5 10:22:57 vmguest kernel: [    2.328528] pnp 00:00: Plug and Play
ACPI device, IDs PNP0303 (active)
Jul  5 10:22:57 vmguest kernel: [    2.328658] pnp 00:01: Plug and Play
ACPI device, IDs PNP0f03 (active)
Jul  5 10:22:57 vmguest kernel: [    2.331146] pnp: PnP ACPI: found 2
devices
Jul  5 10:22:57 vmguest kernel: [    2.391692] clocksource: acpi_pm: mask:
0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
--
Jul  5 10:22:57 vmguest kernel: [    2.395319] pci 0000:00:01.0: Activating
ISA DMA hang workarounds
Jul  5 10:22:57 vmguest kernel: [    2.395474] pci 0000:00:02.0: Video
device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Jul  5 10:22:57 vmguest kernel: [    2.395674] PCI: CLS 0 bytes, default 64
Jul  5 10:22:57 vmguest kernel: [    2.396459] Trying to unpack rootfs
image as initramfs...
Jul  5 10:22:57 vmguest kernel: [    4.134409] Freeing initrd memory:
27504K
Jul  5 10:22:57 vmguest kernel: [    4.143535] clocksource: tsc: mask:
0xffffffffffffffff max_cycles: 0x1596467b3e4, max_idle_ns: 440795260276 ns
Jul  5 10:22:57 vmguest kernel: [    4.183437] clocksource: Switched to
clocksource tsc
--
Jul  5 10:23:01 vmguest kernel: [   21.775504] FS-Cache: Netfs 'nfs'
registered for caching
Jul  5 10:23:01 vmguest kernel: [   22.111370] Key type dns_resolver
registered
Jul  5 10:23:05 vmguest kernel: [   25.970505] NFS: Registering the
id_resolver key type
Jul  5 10:23:05 vmguest kernel: [   25.970532] Key type id_resolver
registered
Jul  5 10:23:05 vmguest kernel: [   25.970533] Key type id_legacy
registered
Jul  5 10:39:28 vmguest kernel: [ 1009.241174] hrtimer: interrupt took
92917571 ns
Jul  5 12:23:41 vmguest kernel: [ 7261.678836] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 967010ns
Jul  5 12:23:41 vmguest kernel: [ 7261.790964] clocksource: wd-tsc-wd
read-back delay of 829142ns, clock-skew test skipped!
Jul  5 12:24:07 vmguest kernel: [ 7287.695208] clocksource: timekeeping
watchdog on CPU0: kvm-clock wd-wd read-back delay of 72384ns
Jul  5 12:24:07 vmguest kernel: [ 7287.699546] clocksource: wd-tsc-wd
read-back delay of 168219ns, clock-skew test skipped!
Jul  5 13:31:32 vmguest kernel: [11332.662655] clocksource: timekeeping
watchdog on CPU2: kvm-clock wd-wd read-back delay of 120032ns
Jul  5 13:31:32 vmguest kernel: [11332.662736] clocksource: wd-tsc-wd
read-back delay of 322514ns, clock-skew test skipped!
Jul  5 13:39:19 vmguest kernel: [11800.119023] clocksource: timekeeping
watchdog on CPU1: kvm-clock wd-wd read-back delay of 86646ns
Jul  5 13:39:19 vmguest kernel: [11800.129473] clocksource: wd-tsc-wd
read-back delay of 481023ns, clock-skew test skipped!
Jul  5 13:57:01 vmguest kernel: [12862.135393] clocksource: timekeeping
watchdog on CPU1: kvm-clock retried 2 times before success

Sorry I wasn't clear in my request.

I assumed these errors occurred in 1 boot session and having the FULL dmesg/
kern.log from *that* session would be useful.
Don't 'grep' the messages which you think are relevant. Often times there are
other messages which give important clues to experts (which I am not), which
seem irrelevant/harmless to you and me.
I'm guessing this bug should be sent upstream and they will (highly) likely
ask for a full dmesg/kernel log.
(I'm merely trying to collect as much useful information as possible)

HTH,
  Diederik

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I am also affected by this issue.

I cannot use my VM images anymore on this kernel version.
The Windows10 guest randomly crashes with:
00:35:44.190732 GIM: HyperV: Guest indicates a fatal condition! P0=0x1e
P1=0xffffffffc0000005 P2=0xfffff80732849020 P3=0x0 P4=0xffffffffffffffff
00:35:44.190795 GIMHv: BugCheck 1e {ffffffffc0000005, fffff80732849020, 0,
ffffffffffffffff}
00:35:44.190795 KMODE_EXCEPTION_NOT_HANDLED
00:35:44.190796 P1: ffffffffc0000005 - exception code - STATUS_ACCESS_VIOLATION
00:35:44.190796 P2: fffff80732849020 - EIP/RIP
00:35:44.190796 P3: 0000000000000000 - Xcpt param #0
00:35:44.190796 P4: ffffffffffffffff - Xcpt param #1
00:35:45.515885 AHCI#0: Reset the HBA
00:35:45.515902 VD#0: Cancelling all active requests
00:35:45.516175 AHCI#0: Port 0 reset
00:35:45.517213 VD#0: Cancelling all active requests
00:35:47.317356 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be
unresponsive. Last heartbeat received 4 seconds ago
00:35:55.668680 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1e
P1=0xffffffffc0000005 P2=0xfffff80732849020 P3=0x0 P4=0xffffffffffffffff

When I downgrade the kernel to linux-image-5.10.0-14-amd64 (5.10.113-1)
the VM runs well!

Control: tags -1 unreproducible

As Virtualbox uses it's own kernel module, we can't provide any help.
You need to ask them for a fixed version to work with that kernel
version.

Or you can use the included kvm support.

Bastian

https://wiki.debian.org/DebianKernel/GitBisect describe a/the way to narrow
down the specific commit that caused the regression.
Knowing that *really* helps to pinpoint the issue and would also help to
determine which upstream (sub)project to contact about this issue.

Bastian Blank wrote:

FWIW, I'm running a test build[1] of VirtualBox with the -15 kernel on
the host.  I, too, had the problem of Firefox crashing regularly with
VirtualBox 6.1.34, but things seem stable with VirtualBox 6.1.35
r151864.

mike
[1] https://www.virtualbox.org/wiki/Testbuilds

Thanks Mike,

I have upgraded to the test build of VirtualBox (6.1.35) and I am not
now seeing Firefox crashing in the virtual guest.  Both host and guest
are running 5.10.0-16-amd64 - 5.10.127-1.  So, I guess this is not a
kernel bug so much as a 'incompatibility' between these kernels and the
older versions of VirtualBox.

Regards,

Richard

Dear Maintainer,

VirtualBox (6.1.35) fixes the crashes on my system too.

See https://www.virtualbox.org/ticket/20914

Regards
Walter

We believe that the bug you reported is fixed in the latest version of
virtualbox, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1014394@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna <locutusofborg@debian.org> (supplier of updated virtualbox package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 29 Jul 2026 15:29:13 +0200
Source: virtualbox
Built-For-Profiles: noudeb
Architecture: source
Version: 7.2.14-dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Virtualbox Team <team+debian-virtualbox@tracker.debian.org>
Changed-By: Gianfranco Costamagna <locutusofborg@debian.org>
Closes: 1014394 1023603 1045194 1050406 1064225 1104227 1138419 1140286 1140302 1140838 1141114 1142527 1142643
Changes:
 virtualbox (7.2.14-dfsg-1) unstable; urgency=medium
 .
   * New upstream version 7.2.14-dfsg
     (Closes: #1142527, #1014394, #1023603, #1045194, #1050406, #1064225)
     (Closes: #1140302, #1142643, #1140286, #1140838, #1141114)
   * Strip also libssl/openssl from upstream tarball
   * Switch from yasm/nasm to only nasm
     (Closes: #1104227)
   * Fix build with Openssl 4.0 (Closes: #1138419)
Checksums-Sha1:
 675edaefa55d5ebb4fa340edff6b020cbf0c961a 3893 virtualbox_7.2.14-dfsg-1.dsc
 989878e25796ab30c11b1fccb0f9b2e98276648b 106712004 virtualbox_7.2.14-dfsg.orig.tar.xz
 7d2d28b681f54f013b8ae9a841b6f9ceb1a32a15 84276 virtualbox_7.2.14-dfsg-1.debian.tar.xz
 ebb3833f9c9415818aaabf34462981c1f7389178 29262 virtualbox_7.2.14-dfsg-1_source.buildinfo
Checksums-Sha256:
 b8b30cf076c1db83e0688833509371fb9efd75a3210401b27ff4e9b07bd4f378 3893 virtualbox_7.2.14-dfsg-1.dsc
 7756f1939fadccaf783b5dc268abaf2e55fc05f12af90944cba3d473595d4907 106712004 virtualbox_7.2.14-dfsg.orig.tar.xz
 2add8b8e74c6f7d917f4b2f809b5c1b7a9ad7caff37504e00638c3324aab59ca 84276 virtualbox_7.2.14-dfsg-1.debian.tar.xz
 3ec433c8d8cae658fbd255911069f5fa4b384a65f26ce38c5912ac195ec7fbfe 29262 virtualbox_7.2.14-dfsg-1_source.buildinfo
Files:
 801202f9fb86ad2018426b020175c9ee 3893 contrib/misc - virtualbox_7.2.14-dfsg-1.dsc
 c151d7824a0bd1e10b1296338233305e 106712004 contrib/misc - virtualbox_7.2.14-dfsg.orig.tar.xz
 49e08517e1135569588b40f9578cf1c6 84276 contrib/misc - virtualbox_7.2.14-dfsg-1.debian.tar.xz
 913aa095a6f0b451fc06cb0ea903dec2 29262 contrib/misc - virtualbox_7.2.14-dfsg-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJNBAEBCgA3FiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmpqIJQZHGxvY3V0dXNv
ZmJvcmdAZGViaWFuLm9yZwAKCRDzTwl0Tp9d2eLfD/4qsoanID9jjQJDS8HOHlS7
jqMvm+ADyrlNkgsgI9XD+LNjFwVAWDF9GPYAFm8NOnm/ssP6qQGUH5qI5h8xIUZg
XRl4UcNpyBGhY6W1P9Jc3z4l4ve6jjMC5z7Rv/sL5xFsasyFLuqsx6ZVkmqUA9n7
0Dz5kc9PdFtvpejfQxpLBFPjoCuow9eRdPplhqDYmF6xbAoSTj6j+3q04KvmOAdC
nEWCvuUapwTa26/jM8sm8iSgYiqpK1CydjQQzj76v2NETwrg5f0EO9TAn7eADbit
XQ83c7xtotYRDZ6AsSkGSLfh6/StBKqZUCJkVz/xhglbmS/7hKUtpsQoV+anHrDz
c1yyU8VDQEXENdkERftgwWTO7sLMELnIUwDWj3Ijepr+iu0/WlzeGKZkSpwWB1q3
GZWoHUD4TIv+4wD8SN/f0PIpeMiijeBVJUUHqNMCH8M7Yl3iQp5Zs16x1Xdn6/Ze
JqKWM+xPVO+bV1qcIX+mQ6rNgSjf0WgSMo8WcXqi3neCArs7PMUCnZzpi45Xh+0i
njEo/MU/OwPB5wPh0iTZEa6YXTCugdDAlBipAgZQA2A3sFtMVNyEf935hg8P2z3R
yED7JJRRbBpG3AXKTgBCKU6XA6h9eFCV/7dqDzaJzwHOJ9AHYVnN6V5Eq/33qQ+p
KW4o0Zg9L+tG21jR9QcmzQ==
=UK43
-----END PGP SIGNATURE-----