What were you trying to do that didn't work?

use valgrind to check if there's memory leak in guest

What is the impact of this issue to you?

dev-ttysclp0.device cannot enable at once, fails to access the guest through ip address

Please provide the package NVR for which the bug is seen:

host kernel version: kernel-6.12.0-89.el10.s390x

guest kernel version: kernel-6.12.0-89.el10.s390x

qemu version: qemu-kvm-10.0.0-7.el10.s390x

libvirt version: libvirt-11.3.0-1.el10.s390x

How reproducible is this bug?:

100%

Steps to reproduce

1. boot guest wih valgrind and virtio-scsi-ccw/virtio-blk-ccw and two virtio-blk devices for storage

valgrind \
    -s \
    --trace-children=yes \
    --track-origins=yes \
    --leak-check=full  \
    --show-leak-kinds=definite \
    --log-file=/tmp/valgrind.log   /usr/libexec/qemu-kvm \

-device '{"driver": "virtio-net-ccw", "mac": "9a:44:1c:6a:ba:bd", "id": "idFShWdU", "netdev": "idKkQbgv", "devno": "fe.0.0005"}' \
-netdev  '{"id": "idKkQbgv", "type": "tap", "vhost": true, "vhostfd": "17", "fd": "11"}'  \{noformat}
h3. Expected results

guest could boot with all devices enabled
 
h3. Actual results

dev-ttysclp0.device start failed

[root@localhost home]# journalctl | grep clp
journalctl | grep clp
Jul 11 17:00:32 localhost kernel: Kernel command line: root=UUID=39e8868a-ad85-4717-9ed4-daa5490d6548 console=tty0 crashkernel=2G-64G:256M,64G-:512M rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap net.ifnames=0 console=ttysclp0,38400 modprobe.blacklist=qla4xxx,cnic,bnx2,bnx2fc,bnx2i
Jul 11 17:00:32 localhost kernel: printk: legacy console [ttysclp0] enabled
Jul 11 17:00:33 localhost dracut-cmdline[295]: Using kernel command line parameters:    root=UUID=39e8868a-ad85-4717-9ed4-daa5490d6548 console=tty0 crashkernel=2G-64G:256M,64G-:512M rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap net.ifnames=0 console=ttysclp0,38400 modprobe.blacklist=qla4xxx,cnic,bnx2,bnx2fc,bnx2i
Jul 11 17:02:33 localhost systemd[1]: Expecting device dev-ttysclp0.device - /dev/ttysclp0...
Jul 11 17:03:06 localhost systemd[1]: dev-ttysclp0.device: Job dev-ttysclp0.device/start timed out.
Jul 11 17:03:06 localhost systemd[1]: Timed out waiting for device dev-ttysclp0.device - /dev/ttysclp0.
Jul 11 17:03:06 localhost systemd[1]: Dependency failed for serial-getty@ttysclp0.service - Serial Getty on ttysclp0.
Jul 11 17:03:06 localhost systemd[1]: serial-getty@ttysclp0.service: Job serial-getty@ttysclp0.service/start failed with result 'dependency'.
Jul 11 17:03:06 localhost systemd[1]: dev-ttysclp0.device: Job dev-ttysclp0.device/start failed with result 'timeout'.

Expected results

guest could boot successfully
 

Actual results

guest boot into emergency mode

Additional info:

1. There's a workaround, guest would go into emergency mode cause the dev-ttysclp0.device is not enble, we could enable it manually by "systemctl start dev-ttysclp0.device", and after exit the emergency mode, the guest could boot correctly
2. After enable it manually and reboot still goes into emergency mode
3. [ TIME ] Timed out waiting for device dev-d...c502f1-6e68-4bfe-a11d-f2f0d8f619d0 this is not enabled as well