On 01.03.2019 12:26, Simon McVittie wrote: > Package: installation-reports > Severity: normal > > I tried to install Debian s390x on a qemu VM using command lines based on > <https://wiki.qemu.org/Documentation/Platforms/S390X>. > > A stretch installation hasn't finished yet but appears to be heading for > success, using this command-line: > > qemu-system-s390x \ > -machine s390-ccw-virtio \ > -cpu max,zpci=on \ > -m 4096 \ > -nic bridge,br=virbr0,model=virtio \ > --cdrom ~/incoming/debian-9.7.0-s390x-netinst.iso \ > -kernel ~/incoming/kernel.debian.stretch.s390x \ > -initrd ~/incoming/initrd.debian.stretch.s390x \ > -drive > file=/home/smcv/tmp/virt/s390x.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=unsafe > \ > -device > virtio-blk-ccw,devno=fe.0.0001,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1,scsi=off > > (*.debian.stretch.s390x are from > <http://ftp.debian.org/debian/dists/stable/main/installer-s390x/current/images/generic/>, > and virbr0 is the default bridge behind NAT created by libvirtd, with > 192.168.122.x addresses.) > > However, an installation of the current buster netboot image with a > similar command-line fails. The step that should generate a SSH host key > hangs at 0% progress; perhaps this is related to insufficient entropy > in the kernel? > > I also noticed repeated kernel messages "BUG: non-zero pgtables_bytes > on freeing mm: -16384" which are probably a bad sign.
This is a known bug that sneaked in the 4.19 stable kernel. It was fixed around 4.19.13 (or 14?) and later. Fedora was also affected. It is only a cosmetic issue and should not explain the hang though.
