Hello, Valentin Vidic, le lun. 03 mai 2021 18:15:22 +0200, a ecrit: > On Mon, May 03, 2021 at 09:16:03AM +0200, Cyril Brulebois wrote: > > Do we have any idea whether that could be something that's only > > triggered within QEMU (maybe try other QEMU versions?), or something > > that affects bare metal systems? > > I don't have access to real s390x hardware, but I tried to run the > installation with QEMU 5.2 from unstable.
How did you start it? I couldn't manage to make it start (with qemu from unstable or from stable), I only got the kernel start and a couple of lines. I was taking http://ftp.de.debian.org/debian/dists/bullseye/main/installer-s390x/current/images/generic/initrd.debian http://ftp.de.debian.org/debian/dists/bullseye/main/installer-s390x/current/images/generic/kernel.debian and run qemu-system-s390x -kernel /tmp/s390x/kernel.debian -initrd /tmp/s390x/initrd.debian -m 1G -serial stdio and got [..kernel logs..] [ 4.349417] Run /init as init process [ 5.499051] failover: module verification failed: signature and/or required key missing - tainting kernel [ 6.530501] virtio_net virtio0 enc0: renamed from eth0 steal-ctty: No such file or directory [ 83.282353] random: crng init done and nothing more. Samuel
