[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: specifying virtio block device as root filesystem for Debian S390X install?

Okay, the installer finished, but I ran into some weirdness on the
subsequent reboot - I modified the qemu command line to remove the
kernel/initrd parameters (since they are no longer needed) - I would assume
that ZIPL on /dev/vda1 should take care of the boot then.  The following
command line is used with the s390-zipl.rom file to boot the VM up - 

qemu-system-s390x.exe -machine type=s390-virtio -m 512 -drive
file=linux.disk,if=none,id=disk0 -device
virtio-blk-s390,drive=disk0,id=virtio-disk0 -device
virtio-net-s390,netdev=net0 -netdev user,id=net0 -k en-us -redir

However, this time the QEMU virtual console virtcon0 shows a blank on start,
I don't see any activities on the disk, sshd doesn't seem to show up so I
cannot login and see what's up, and I can't tell what was happening.  

If I use the CCW version:

qemu-system-s390x.exe -machine type=s390-ccw-virtio-2.5 -m 512 -hda
linux.disk -device virtio-net-ccw,netdev=net0 -netdev user,id=net0 -k en-us
-redir tcp:9022::22

Then I'll see a console, followed by some complaints about missing
/sys/bus/ccw/devices/virtio/cutype (sysfs not populating info on the CCW

Any pointers?  

-----Original Message-----
From: Philipp Kern [mailto:pkern@debian.org] 
Sent: Monday, November 02, 2015 1:20 PM
To: Kevin Kwan (Personal)
Cc: debian-s390@lists.debian.org
Subject: Re: specifying virtio block device as root filesystem for Debian
S390X install?

On Mon, Nov 02, 2015 at 10:46:39AM -0500, Kevin Kwan (Personal) wrote:
> it turns out that since I was running the Debian 9/stretch 
> kernel/initrd, it was not loading the ext3/4 modules due to missing 
> modules.  This is likely the reason why partman failed to give me an
option to make the filesystem.
> I had to boot the machine up on the Debian 8/jessie kernel/initrd, 
> shoehorn in the netcfg_1.134_s390x udeb to get rid of that virtio eth0 
> error, and then mess with the dasd postint to bypass the DASD 
> designation.  However, I was able to get partman working and got the 
> filesystem doing, and it's installing the base system now, so I suppose
that it is okay.

FWIW, there are daily builds on [1] that should have matching-up
kernel/modules. But yes, that breaks quite often during testing's lifetime
until it's cut to stable.

Please do report bugs that you encounter.

Kind regards
Philipp Kern

[1] http://d-i.debian.org/daily-images/s390x/daily/generic/ 

Reply to: