Re: specifying virtio block device as root filesystem for Debian S390X install?
On 11/16/2015 06:18 PM, Kevin Kwan (Personal) wrote:
> Okay, looks like there are more developments to this ->
> -----Original Message-----
> From: Christian Borntraeger [mailto:email@example.com]
> Sent: Friday, November 13, 2015 7:37 AM
> To: firstname.lastname@example.org; email@example.com
> Subject: Re: specifying virtio block device as root filesystem for Debian
> S390X install?
> On 11/04/2015 10:52 PM, Kevin Kwan (Personal) wrote:
>> Okay, I think I figured out the gist of the problem -
>> This being the Debian8 kernel/initrd environment, netcfg will be an
>> issue down the line, since it would not allow you to proceed with a
>> virtio NIC configure. This will need to be patched with installing
>> the netcfg 1.13 or
>> 1.134 udeb from the repo (1.13 is stable, 1.134 is testing/sid)
>> Then all you conceivably have to do is to patch the dasd-postinst so
>> the machine will allow you to proceed
> So Debian 8 did support the s390-ccw-virtio machine and so should Debian 9
> - which it does not. Correct?
> Yes. However, it looks like qemu 2.4.50/qemu-windows build 20150922 has an
> implementation of virtio-CCW
> that does not play well with Debian 9, but was okay for 8. This behavior
> was also observed for the qemu 2.4
> package on the Debian unstable repo (so if you run qemu on stretch/sid, it's
> doing that as well).
Maybe you hit an endianess bug, that was happening when the guest tried to check
for virtio 1.0.
> The newer release (2.4.90/qemu-windows build 20151105) seemed to have fixed
> the problem. This means that if you
> plan to run Debian 9 nightly it should have no problems. I am guessing that
> if qemu on sid is going to 2.4.1 (or wait for 2.5
> to drop before Christmas),it should work on Debian itself as well.