The officially official Devuan Forum!

webman

Member

Registered: 2022-08-27

Posts: 45  

zfs setup package - missing dependencies leads to failed setup

Hello!
I just - for testing - setup ZFS in a kvm guest.
If fails miserably, because the package has left off dependencies.
I am listing the problem messages here (and a bad solution further down).

apt install zfsutils-linux -t daedalus-backports

Setting up zfs-dkms (2.2.4-1~bpo12+1) ...
Loading new zfs-2.2.4 DKMS files...
Building for 6.1.0-15-amd64
Module build for kernel 6.1.0-15-amd64 was skipped since the
kernel headers for this kernel do not seem to be installed.
....
Setting up zfsutils-linux (2.2.4-1~bpo12+1) ...
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.0-15-amd64
modprobe: FATAL: Module zfs not found in directory /lib/modules/6.1.0-15-amd64
invoke-rc.d: initscript zfs-import, action "start" failed.
dpkg: error processing package zfsutils-linux (--configure):
 installed zfsutils-linux package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 2.2.4-1~bpo12+1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-15-amd64
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Next, I installed the headers mentioned above.

apt install linux-headers-6.1.0-15-amd64

went through a while ....

Building module:
Cleaning build area...
make -j2 KERNELRELEASE=6.1.0-15-amd64..........................................................................
...............................................................................................................
................................................................
Signing module /var/lib/dkms/zfs/2.2.4/build/module/zfs.ko
Signing module /var/lib/dkms/zfs/2.2.4/build/module/spl.ko

Running the post_build script:
Cleaning build area...

zfs.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.1.0-15-amd64/updates/dkms/

 ....

dkms: autoinstall for kernel: 6.1.0-15-amd64.
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 2.2.4-1~bpo12+1); however:
  Package zfsutils-linux is not configured yet.

dpkg: error processing package zfs-zed (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)

The same story as for my first installation attempt.
From this, I know, how to continue:

apt install zfsutils-linux -t daedalus-backports

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
zfsutils-linux is already the newest version (2.2.4-1~bpo12+1).
0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up zfsutils-linux (2.2.4-1~bpo12+1) ...
insmod /lib/modules/6.1.0-15-amd64/updates/dkms/spl.ko 
insmod /lib/modules/6.1.0-15-amd64/updates/dkms/zfs.ko 
Mounting ZFS filesystem(s) .
Load ZFS filesystem(s) keys.
Sharing ZFS filesystems .
Setting up zfs-zed (2.2.4-1~bpo12+1) ...
Starting ZFS Event Daemon .

The zfs packages are in an invalid state, which has to be fixed!

Regards,
Manfred

Kiergan

Member

Registered: 2017-05-31

Posts: 15  

Re: zfs setup package - missing dependencies leads to failed setup

I don't know if this related, but I ran into a problem installing zfs (on daedalus on PC).
The building of the module hangs and and I had to stop it.
Now I can also not remove it because it says:
dpkg was interrupted, you must manually run 'dpkg --reconfigure -a'
to correct the problem.

But when I do that it hangs again.
Can someone please tell me what can be done about this?

Edit:
OK, I ran it again after a reboot and after a very long time, it finished with unconfigured packages.
I then ran remove and autoremove
and it looks ok now.

So, how can I install zfs, please?

Last edited by Kiergan (2024-06-24 12:03:54)

Kiergan

Member

Registered: 2017-05-31

Posts: 15  

Re: zfs setup package - missing dependencies leads to failed setup

OK, I got it to work!
So, maybe that someone else has some use of what I did:

nano /etc/apt/sources.list

deb http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-backports main non-free-firmware non-free contrib

apt update

apt install linux-headers-$(uname -r) linux-image-amd64  kmod zfsutils-linux
apt install zfsutils-linux zfs-dkms zfs-zed
zpool import stor -f
zpool list

zfs list
NAME   USED  AVAIL     REFER  MOUNTPOINT
stor  1.31M  3.51T      128K  /zfs

Success!

I hope I did not miss anything, since this was done after a previous failure.

Last edited by Kiergan (2024-06-24 14:03:47)

webman

Member

Registered: 2022-08-27

Posts: 45  

Re: zfs setup package - missing dependencies leads to failed setup

Hi!
Exactly, what I did (just not listed lile "headers-$(uname -r), but my real kernel version).
Additionally, I required the version form backports (because I need the block-copy feature).
From my first failed setup, I have to add: Use grub-pc from backports too, it may otherwise
fail after pool snapshots!
But it remains problematic and I am unsure, to continue:
- In my real hardware setup, I am getting an error message at each shutdown (postet this here).
- In another kvm/qemu setup, where NO pools are in use, but just ZFS setup, it crashes at each shutdown.
May be, there is an undiscovered problem with non-systemd systems - worked perfectly for me on debian.
Regards,
Manfred

webman

Member

Registered: 2022-08-27

Posts: 45  

Re: zfs setup package - missing dependencies leads to failed setup

Hi!
On my VM, I removed backports and ZFS and started from scratch
(was a bit tricky to remove 'grub-pc' from backports).
Installation of ZFS 2.1.11 went smootly, no errors.
But, with the "cannot unmount /var/log" from my hardware in mind,
I looked at shutdown and the I see this:

Stopping ZFS Event Daemon
Unloading modules rmmod: ERROR: Module zcommon is in use by icp
rmmod ERROR: Module znvpais is in use by: zcommon
rmmod: ERROR: Module spl is in use by: icp zstd znvpair zcommon
FAILED!

Packages:

Stopping ZFS Event Daemon
Unloading modules rmmod: ERROR: Module zcommon is in use by icp
rmmod ERROR: Module znvpais is in use by: zcommon
rmmod: ERROR: Module spl is in use by: icp zstd znvpair zcommon
FAILED!

zfsutils-linux:
  Installed: 2.1.11-1
  Candidate: 2.1.11-1
  Version table:
 *** 2.1.11-1 500
        500 http://deb.devuan.org/merged daedalus/contrib amd64 Packages
        100 /var/lib/dpkg/status
zfs-dkms:
  Installed: 2.1.11-1
  Candidate: 2.1.11-1
  Version table:
 *** 2.1.11-1 500
        500 http://deb.devuan.org/merged daedalus/contrib amd64 Packages
        100 /var/lib/dpkg/status

$ uname -a
Linux devu5base 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux

There are NO pools, but an extra disk, which contains a pool (which has not und should not be importet)

With this VM, using zfs 2.4, I created two clones (on ZFS volumes for VMs) and they have the same error
like the hardware installation:

Unsharing ZFS filesystems.
Stopping ZFS Event Daemon.
Unmounting ZFS filesystems cannot unmount '/var/pool': pool or dataset is busy
cannot unmount 'var/log': pool or dataset is busy
cannot unmount '/root': pool or dataset is busy

Lost my hope!

Regards,
Manfred

Kiergan

Member

Registered: 2017-05-31

Posts: 15  

Re: zfs setup package - missing dependencies leads to failed setup

I have not seen these kinds of problems.
If I have time, I will make a Virtualbox VM and install Daeldalus and zfs and see how it goes.

Kiergan

Member

Registered: 2017-05-31

Posts: 15  

Re: zfs setup package - missing dependencies leads to failed setup

I installed Daeldalus from netinstall with only ssh.

nano /etc/apt/sources.list

deb http://deb.devuan.org/merged daedalus main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-updates main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-security main non-free-firmware non-free contrib
deb http://deb.devuan.org/merged daedalus-backports main non-free-firmware non-free contrib

apt update
apt install linux-headers-$(uname -r) linux-image-amd64  kmod zfsutils-linux

(takes a long time)

   - Installing to /lib/modules/6.1.0-21-amd64/updates/dkms/
depmod....
Setting up linux-headers-6.1.0-21-amd64 (6.1.90-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-21-amd64.
dkms: autoinstall for kernel: 6.1.0-21-amd64.
Setting up g++ (4:12.2.0-3) ...
update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
Setting up build-essential (12.9) ...
Setting up linux-headers-amd64 (6.1.90-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-21-amd64
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Processing triggers for ca-certificates (20230311) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Errors were encountered while processing:
 zfsutils-linux
 zfs-zed
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@d5-zfs:~/.ssh#

I didn't look further what error it was (sorry).
I tried installing again:
apt install linux-headers-$(uname -r) linux-image-amd64
apt install  kmod zfsutils-linux zfs-dkms zfs-zed

root@d5-zfs:~/.ssh# apt install linux-headers-$(uname -r) linux-image-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-headers-6.1.0-21-amd64 is already the newest version (6.1.90-1).
linux-image-amd64 is already the newest version (6.1.90-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up zfsutils-linux (2.1.11-1) ...
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/spl.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/znvpair.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/zcommon.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/icp.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/zavl.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/zlua.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/zzstd.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/zunicode.ko
insmod /lib/modules/6.1.0-21-amd64/updates/dkms/zfs.ko
Mounting ZFS filesystem(s) .
Load ZFS filesystem(s) keys.
Sharing ZFS filesystems .
Setting up zfs-zed (2.1.11-1) ...
Starting ZFS Event Daemon .
root@d5-zfs:~/.ssh# apt install  kmod zfsutils-linux zfs-dkms zfs-zed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kmod is already the newest version (30+20221128-1).
zfsutils-linux is already the newest version (2.1.11-1).
zfs-dkms is already the newest version (2.1.11-1).
zfs-dkms set to manually installed.
zfs-zed is already the newest version (2.1.11-1).
zfs-zed set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@d5-zfs:~/.ssh#

All seems fine

(Added 3 1GB disks)

sudo lsblk
root@d5-zfs:~# sudo lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
sda      8:0    0   32G  0 disk
??sda1   8:1    0   31G  0 part /
??sda2   8:2    0    1K  0 part
??sda5   8:5    0  975M  0 part [SWAP]
sdb      8:16   0    1G  0 disk
sdc      8:32   0    1G  0 disk
sdd      8:48   0    1G  0 disk
sr0     11:0    1 1024M  0 rom
root@d5-zfs:~#

root@d5-zfs:~# ls -lh /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root  9 Jun 26 13:14 ata-VBOX_CD-ROM_VB2-01700376 -> ../../sr0
lrwxrwxrwx 1 root root  9 Jun 26 13:14 ata-VBOX_HARDDISK_VB19b22f4e-d366cedf -> ../../sdb
lrwxrwxrwx 1 root root  9 Jun 26 13:14 ata-VBOX_HARDDISK_VB4bba567c-1d2e5a13 -> ../../sda
lrwxrwxrwx 1 root root 10 Jun 26 13:14 ata-VBOX_HARDDISK_VB4bba567c-1d2e5a13-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jun 26 13:14 ata-VBOX_HARDDISK_VB4bba567c-1d2e5a13-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jun 26 13:14 ata-VBOX_HARDDISK_VB4bba567c-1d2e5a13-part5 -> ../../sda5
lrwxrwxrwx 1 root root  9 Jun 26 13:14 ata-VBOX_HARDDISK_VBab7c48ef-bbd457ab -> ../../sdd
lrwxrwxrwx 1 root root  9 Jun 26 13:14 ata-VBOX_HARDDISK_VBacc7b9a1-936214d4 -> ../../sdc
root@d5-zfs:~#

zpool create -f -m /zfs zpool \
               raidz \
                  ata-VBOX_HARDDISK_VB19b22f4e-d366cedf \
                  ata-VBOX_HARDDISK_VBacc7b9a1-936214d4\
                  ata-VBOX_HARDDISK_VBab7c48ef-bbd457ab

root@d5-zfs:~# zpool list
NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
zpool  2.75G   217K  2.75G        -         -     0%     0%  1.00x    ONLINE  -
root@d5-zfs:~#

root@d5-zfs:~# zpool list
NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
zpool  2.75G   217K  2.75G        -         -     0%     0%  1.00x    ONLINE  -
root@d5-zfs:~# zpool status
  pool: zpool
 state: ONLINE
config:

        NAME                                       STATE     READ WRITE CKSUM
        zpool                                      ONLINE       0     0     0
          raidz1-0                                 ONLINE       0     0     0
            ata-VBOX_HARDDISK_VB19b22f4e-d366cedf  ONLINE       0     0     0
            ata-VBOX_HARDDISK_VBacc7b9a1-936214d4  ONLINE       0     0     0
            ata-VBOX_HARDDISK_VBab7c48ef-bbd457ab  ONLINE       0     0     0

errors: No known data errors
root@d5-zfs:~#

root@d5-zfs:~# zfs list
NAME    USED  AVAIL     REFER  MOUNTPOINT
zpool   145K  1.71G     30.6K  /zfs

I saw no errors when rebooting.
There is a /zfs directory of 1745 MB that I can write to etc.

I hope this can be of some help.

webman

Member

Registered: 2022-08-27

Posts: 45  

Re: zfs setup package - missing dependencies leads to failed setup

Hi!
Thanks!

This is nearly, what I usually do (have only SSHD and some networking tools - I usually keep this as
a bootable installation on first partition as "repair-inst", with the same version of ZFS which I'll use
to setup zfs on root (onto anohter disk). Using ether netinstall, or, naturallay, for zfs on root the
debootstrap tool, how it is described. One different thing is, that I first install DKMS separately and
the wanted kernel with headers.

And you describe exactly ("image1"), what I am experiencing. What you see

"I didn't look further what error it was (sorry)."

is a dependency problem, which left a part uninitialized, which becomes "repaired" if you repeat the
step - independently, that you' made it a little differently (which is not neccessary, because all this
is in dependencies).

I have the (already) described problem with shutdown. If I add pools, they dont have a problem
and working properly like your's.

But I am not keeping installations, which have improperly behavior on stutdown (or startup).
For my ZFS-VMs (which are KVM/QEMU), I initiate a shutdown from inside and keep the
mouse-pointer (on the host) on the pause button, which I press at the moment, the red errorline appears.
On a new hardware, this is the same - but I cannot stop the display .... and they dont appear in logs,
and for my other cases, it is theit is the root-filesystem on unmount!

My older (and running) installations dont have errors or this behavior.
On my day-work machine (which ist Debian Bullseye, ZFS on root), no errors appear, wether
at startup or shutdown (and even my fileserver, staying on Debian Buster, ZFS on root, is error-free).

The 2.4 version (in backports), which I need due to the block-copy feature, is even crashing
hard at shutdown.

Usually, zfs-setup is easy (except for on root) and causes no errors - I am using it since
2012 (not on root at that time).

Regards,
Manfred

webman

Member

Registered: 2022-08-27

Posts: 45  

Re: zfs setup package - missing dependencies leads to failed setup

Hi!
For the vm, after upgrading from zfs from 2.1.11 to 2.2.4 I used two ssh session:
One for shutting down, the other running "dmesg -Tw", which shows the catastrophe:

The system is going down for system halt NOW!
[Wed Jun 26 15:29:46 2024] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[Wed Jun 26 15:29:46 2024] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[Wed Jun 26 15:29:46 2024] device-mapper: uevent: version 1.0.3
[Wed Jun 26 15:29:46 2024] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[Wed Jun 26 15:29:46 2024] ------------[ cut here ]------------
[Wed Jun 26 15:29:46 2024] kobject: '(null)' (00000000ae4d8a76): is not initialized, yet kobject_put() is being called.
[Wed Jun 26 15:29:46 2024] WARNING: CPU: 0 PID: 2114 at lib/kobject.c:726 kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:46 2024] Modules linked in: dm_mod nfnetlink_log nfnetlink binfmt_misc sha512_generic cmac nls_utf8 cifs cifs_arc4 cifs_md4 dns_resolver fscache netfs snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec drm_ttm_helper snd_hda_core ttm iTCO_wdt intel_pmc_bxt snd_hwdep drm_kms_helper snd_pcm pcspkr snd_timer vmw_vsock_virtio_transport serio_raw iTCO_vendor_support vmw_vsock_virtio_transport_common joydev snd watchdog soundcore evdev virtio_rng drm vsock virtio_balloon virtio_console qemu_fw_cfg button zfs(POE-) spl(OE) ext4 crc16 mbcache jbd2 crc32c_generic sg hid_generic sd_mod t10_pi usbhid crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_common hid ahci libahci virtio_scsi libata ehci_pci uhci_hcd psmouse i2c_i801 ehci_hcd virtio_net net_failover failover scsi_mod i2c_smbus lpc_ich scsi_common usbcore usb_common virtio_pci virtio_pci_legacy_dev virtio_pci_modern_dev virtio virtio_ring
[Wed Jun 26 15:29:47 2024] CPU: 0 PID: 2114 Comm: rmmod Tainted: P           OE      6.1.0-21-amd64 #1  Debian 6.1.90-1
[Wed Jun 26 15:29:47 2024] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
[Wed Jun 26 15:29:47 2024] RIP: 0010:kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024] Code: 00 4c 89 ef e8 84 8b 8e ff 48 85 db 74 9a f6 43 3c 01 0f 85 78 ff ff ff 48 8b 33 48 89 da 48 c7 c7 e0 a1 20 b4 e8 83 1b 6e ff <0f> 0b e9 5f ff ff ff c3 cc cc cc cc 4d 89 f1 49 c7 c0 30 59 f5 b3
[Wed Jun 26 15:29:47 2024] RSP: 0018:ffffad0bc077bd08 EFLAGS: 00010286
[Wed Jun 26 15:29:47 2024] RAX: 0000000000000000 RBX: ffff968f0478a6d0 RCX: c0000000ffffefff
[Wed Jun 26 15:29:47 2024] RDX: 0000000000000000 RSI: 00000000ffffefff RDI: 0000000000000001
[Wed Jun 26 15:29:47 2024] RBP: 00000000ffffffff R08: 0000000000000000 R09: ffffad0bc077bb80
[Wed Jun 26 15:29:47 2024] R10: 0000000000000003 R11: ffffffffb48d4448 R12: 0000000000000800
[Wed Jun 26 15:29:47 2024] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[Wed Jun 26 15:29:47 2024] FS:  00007f90abfb2040(0000) GS:ffff968f7dc00000(0000) knlGS:0000000000000000
[Wed Jun 26 15:29:47 2024] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Wed Jun 26 15:29:47 2024] CR2: 00007f90ab867c10 CR3: 00000000047ac000 CR4: 00000000000006f0
[Wed Jun 26 15:29:47 2024] Call Trace:
[Wed Jun 26 15:29:47 2024]  <TASK>
[Wed Jun 26 15:29:47 2024]  ? __warn+0x7d/0xc0
[Wed Jun 26 15:29:47 2024]  ? kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024]  ? report_bug+0xe2/0x150
[Wed Jun 26 15:29:47 2024]  ? handle_bug+0x41/0x70
[Wed Jun 26 15:29:47 2024]  ? exc_invalid_op+0x13/0x60
[Wed Jun 26 15:29:47 2024]  ? asm_exc_invalid_op+0x16/0x20
[Wed Jun 26 15:29:47 2024]  ? kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024]  ? kobject_put+0xbd/0x1d0
[Wed Jun 26 15:29:47 2024]  zfs_sysfs_fini+0x116/0x190 [zfs]
[Wed Jun 26 15:29:47 2024]  openzfs_fini+0x5/0x7df [zfs]
[Wed Jun 26 15:29:47 2024]  __do_sys_delete_module+0x1d5/0x320
[Wed Jun 26 15:29:47 2024]  do_syscall_64+0x55/0xb0
[Wed Jun 26 15:29:47 2024]  ? __handle_mm_fault+0x660/0xfa0
[Wed Jun 26 15:29:47 2024]  ? handle_mm_fault+0xdb/0x2d0
[Wed Jun 26 15:29:47 2024]  ? do_user_addr_fault+0x1b0/0x580
[Wed Jun 26 15:29:47 2024]  ? exit_to_user_mode_prepare+0x44/0x1f0
[Wed Jun 26 15:29:47 2024]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[Wed Jun 26 15:29:47 2024] RIP: 0033:0x7f90ab928a67
[Wed Jun 26 15:29:47 2024] Code: 73 01 c3 48 8b 0d 99 83 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 69 83 0c 00 f7 d8 64 89 01 48
[Wed Jun 26 15:29:47 2024] RSP: 002b:00007ffe277cc818 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0
[Wed Jun 26 15:29:47 2024] RAX: ffffffffffffffda RBX: 0000561de39f1780 RCX: 00007f90ab928a67
[Wed Jun 26 15:29:47 2024] RDX: 0000000000000000 RSI: 0000000000000800 RDI: 0000561de39f17e8
[Wed Jun 26 15:29:47 2024] RBP: 0000000000000000 R08: 1999999999999999 R09: 0000000000000000
[Wed Jun 26 15:29:47 2024] R10: 00007f90ab99bac0 R11: 0000000000000206 R12: 00007ffe277cca60
[Wed Jun 26 15:29:47 2024] R13: 00007ffe277cce16 R14: 0000561de39f12a0 R15: 00007ffe277cca70
[Wed Jun 26 15:29:47 2024]  </TASK>
[Wed Jun 26 15:29:47 2024] ---[ end trace 0000000000000000 ]---
[Wed Jun 26 15:29:47 2024] ------------[ cut here ]------------

Its followed by a second block with "same" content, probably, one for each CPU (the VM has two).

Regards,
Manfred