Hi,
I'm trying to install a s390x VM using qemu:
$ qemu-system-s390x -machine s390-ccw-virtio -nographic \
--cdrom debian-10.4.0-s390x-netinst.iso \
-kernel boot/linux_vm -initrd boot/root.bin -append init=/bin/sh
but it doesn't seem to work - there is no network, cdrom or disk.
Should this work or is this usecase not supported?
$ 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.xxxx -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).
On 5/17/20 8:57 PM, Valentin Vidić wrote:
Hi,
I'm trying to install a s390x VM using qemu:
$ qemu-system-s390x -machine s390-ccw-virtio -nographic \
--cdrom debian-10.4.0-s390x-netinst.iso \
-kernel boot/linux_vm -initrd boot/root.bin -append init=/bin/sh
but it doesn't seem to work - there is no network, cdrom or disk.
Should this work or is this usecase not supported?
I'd recommend to try virt-install, see http://kvmonz.blogspot.com/p/knowledge-use-virt-install-for-kvm.html. virt-install will set up the VM in a proper way.
You will need to invoke virt-install with --arch=s390x if your running
on an x86 box and make sure you have the qemu-system-s390x package
installed.
Chance for success will probably increase with the currency of the
QEMU used.
The invocation you've reported above doesn't instantiate a virtio disk
and network interface (which are the only device types supported for
s390x. Similary virtual CD/DVD must be on virtio-scsi for s390x.
Again, virt-install and virsh are your friends here
I'd recommend to try virt-install, see http://kvmonz.blogspot.com/p/knowledge-use-virt-install-for-kvm.html. virt-install will set up the VM in a proper way.
You will need to invoke virt-install with --arch=s390x if your running on an x86 box and make sure you have the qemu-system-s390x package installed.
Chance for success will probably increase with the currency of the QEMU
used.
The invocation you've reported above doesn't instantiate a virtio disk and network interface (which are the only device types supported for s390x. Similary virtual CD/DVD must be on virtio-scsi for s390x. Again,
virt-install and virsh are your friends here.
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.xxxx -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?
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.xxxx -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.
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?
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
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?
FWIW, lscpumf and chcpumf use the Data::Dumper package which require the
full perl setup. Perhaps it would make sense to split s390-tools into a
basic package containing the tools needed for device setup and an extension package with all the additional stuff. That would be up to the maintainer.
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 399 |
Nodes: | 16 (2 / 14) |
Uptime: | 98:44:39 |
Calls: | 8,363 |
Calls today: | 2 |
Files: | 13,162 |
Messages: | 5,897,721 |