Re: qemu install
On Mon, May 18, 2020 at 08:00:41PM +0200, Valentin Vidić wrote: > 1. debian-installer fails to start on serial port due to wrong device > name (ttyS1 vs ttysclp0). I can boot with init=/bin/sh and make a > symlink but a patch is here: > https://salsa.debian.org/installer-team/rootskel/-/merge_requests/2/diffs I got a suggestion to fix the console problem by patching the driver instead of the installer: https://lkml.org/lkml/2020/5/19/854 -- Valentin
Re: qemu install
On Tue, May 19, 2020 at 11:07:48AM +0200, Viktor Mihajlovski wrote: > I glanced over the d-i config and udebs. It seems that with buster the > virtio-modules udeb was removed under the assumption that the virtio modules > are to be found in nic-modules and scsi-modules. > Unfortunately, those don't include the virtio modules for s390x. > Would you care to open a defect against d-i? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961057 debian-installer: qemu-system-s390x installation fails due to missing modules -- Valentin
Re: qemu install
On Tue, May 19, 2020 at 04:18:06PM +0200, Viktor Mihajlovski wrote: > I tried to install under z/VM with the same debootstrap failure. It seems > that it would be necessary to add perl to the list of bootstrap packages in > order to satisfy the s390-tools depends. Yes, not sure what is the problem there, perhaps s390-tools needs to use perl-base instead? -- Valentin
Re: qemu install
On 5/18/20 8:00 PM, Valentin Vidić wrote: On Mon, May 18, 2020 at 07:31:15PM +0200, Benjamin Jakob Zimmermann wrote: $ qemu-system-s390x -M s390-ccw-virtio -m 1G -smp 1 -enable-kvm -nographic -device virtio-net-ccw,netdev=mynet0 -netdev tap,id=mynet0,script=qemu-ifup -drive file=/dev/disk/by-path/ccw-0.0. -kernel loopdir/boot/linux_vm -initrd loopdir/boot/root.bin -append 'debian-installer/allow_unauthenticated=true' This works on a z13 and z14. Works also fine with clefOS (CentOS clone). Thanks for the info. Indeed it seems that things work with the stretch image so I will try to use that. But can we also try to fix buster and unstable images as these seem to be broken at the moment? I have identified the following problems: 1. debian-installer fails to start on serial port due to wrong device name (ttyS1 vs ttysclp0). I can boot with init=/bin/sh and make a symlink but a patch is here: https://salsa.debian.org/installer-team/rootskel/-/merge_requests/2/diffs 2. initrd does not include the required modules (virtio_net and virtio_blk) so network and disk devices are not visible. Had to build a new initrd with these included. 3. installation starts but at some point debootstrap fails with May 17 20:12:05 debootstrap: dpkg: error processing package s390-tools (--configure): May 17 20:12:05 debootstrap: dependency problems - leaving unconfigured May 17 20:12:06 debootstrap: Errors were encountered while processing: May 17 20:12:06 debootstrap: s390-tools May 17 20:12:07 debootstrap: dpkg: dependency problems prevent configuration of s390-tools: May 17 20:12:07 debootstrap: s390-tools depends on perl:any. So probably s390-tools package needs to be updated? I tried to install under z/VM with the same debootstrap failure. It seems that it would be necessary to add perl to the list of bootstrap packages in order to satisfy the s390-tools depends. -- Kind Regards, Viktor
Re: qemu install
On 5/18/20 8:00 PM, Valentin Vidić wrote: On Mon, May 18, 2020 at 07:31:15PM +0200, Benjamin Jakob Zimmermann wrote: $ qemu-system-s390x -M s390-ccw-virtio -m 1G -smp 1 -enable-kvm -nographic -device virtio-net-ccw,netdev=mynet0 -netdev tap,id=mynet0,script=qemu-ifup -drive file=/dev/disk/by-path/ccw-0.0. -kernel loopdir/boot/linux_vm -initrd loopdir/boot/root.bin -append 'debian-installer/allow_unauthenticated=true' This works on a z13 and z14. Works also fine with clefOS (CentOS clone). Thanks for the info. Indeed it seems that things work with the stretch image so I will try to use that. But can we also try to fix buster and unstable images as these seem to be broken at the moment? I have identified the following problems: 1. debian-installer fails to start on serial port due to wrong device name (ttyS1 vs ttysclp0). I can boot with init=/bin/sh and make a symlink but a patch is here: https://salsa.debian.org/installer-team/rootskel/-/merge_requests/2/diffs 2. initrd does not include the required modules (virtio_net and virtio_blk) so network and disk devices are not visible. Had to build a new initrd with these included. I glanced over the d-i config and udebs. It seems that with buster the virtio-modules udeb was removed under the assumption that the virtio modules are to be found in nic-modules and scsi-modules. Unfortunately, those don't include the virtio modules for s390x. Would you care to open a defect against d-i? 3. installation starts but at some point debootstrap fails with May 17 20:12:05 debootstrap: dpkg: error processing package s390-tools (--configure): May 17 20:12:05 debootstrap: dependency problems - leaving unconfigured May 17 20:12:06 debootstrap: Errors were encountered while processing: May 17 20:12:06 debootstrap: s390-tools May 17 20:12:07 debootstrap: dpkg: dependency problems prevent configuration of s390-tools: May 17 20:12:07 debootstrap: s390-tools depends on perl:any. So probably s390-tools package needs to be updated? -- Kind Regards, Viktor
