Hi, I have a strange problem with vms running Leap 15.4. After a reboot, I do "zypper ps" and it outputs: # zypper ps The following running processes use deleted files: PID | PPID | UID | User | Command | Service | Files ----+------+-----+------+-------------------+---------+------------------------------ 177 | 1 | 0 | root | haveged (deleted) | haveged | /lib64/ld-2.31.so | | | | | | /usr/lib64/libhavege.so.2.0.0 | | | | | | /lib64/libc-2.31.so | | | | | | /usr/sbin/haveged (deleted) You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. No core libraries or services have been updated since the last system boot. Reboot is probably not necessary. # This is only on virtual machines that use VirtIO (/dev/vda) as disk. It is not on real hardware (using /dev/sda). It is not on vms using SCSI (/dev/sda) as disk. Hypervisor for vms is Leap 15.4 KVM (qemu). (It also happens on a proxmox 7.2 Hypervisor, but lets stay at the Leap 15.4 KVM). All vms are updated and have the same repos. Software versions of haveged, lsof and zypper are the same. Bonus info: On the vms with SCSI disks haveged is restarted after boot: # journalctl _SYSTEMD_UNIT=haveged.service Dez 21 01:24:43 wpyc057 haveged[172]: haveged: command socket is listening at fd 3 Dez 21 01:24:49 wpyc057 haveged[172]: haveged: Stopping due to signal 15 Dez 21 01:24:49 wpyc057 haveged[172]: haveged starting up Dez 21 01:24:49 wpyc057 haveged[620]: haveged: command socket is listening at fd 3 # On vms with VirtIO disks, it is not restarted: # journalctl _SYSTEMD_UNIT=haveged.service Dez 21 01:23:43 localhost haveged[177]: haveged: command socket is listening at fd 3 # Any hint for debugging?