[Top][All Lists]

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

Re: [qemu-s390x] [PATCH v6 00/16] s390: vfio-ccw dasd ipl support

From: Thomas Huth
Subject: Re: [qemu-s390x] [PATCH v6 00/16] s390: vfio-ccw dasd ipl support
Date: Fri, 5 Apr 2019 09:52:02 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

On 05/04/2019 08.58, Thomas Huth wrote:
> On 04/04/2019 16.34, Jason J. Herne wrote:
>> This is to support booting from vfio-ccw dasd devices. We basically implement
>> the real hardware ipl procedure. This allows for booting Linux guests on
>> vfio-ccw devices.
>> vfio-ccw's channel program prefetch algorithm complicates ipl because most 
>> ipl
>> channel programs dynamically modify themselves. Details on the ipl process 
>> and
>> how we worked around this issue can be found in docs/devel/s390-dasd-ipl.txt.
>  Hi Jason,
> while running my s390-ccw bios tests, I noticed that network booting
> seems to be broken now. This used to work before:
> s390x-softmmu/qemu-system-s390x -nographic -accel kvm \
>  -bios pc-bios/s390-ccw/s390-ccw.img \
>  -global s390-ipl.netboot_fw=pc-bios/s390-ccw/s390-netboot.img \
>  -netdev user,id=n1,tftp=/boot,bootfile=vmlinuz-4.18.0 \
>  -device virtio-net-ccw,netdev=n1,bootindex=1
> Now it simply fails with "! No IPL device available !".
> Could you have a look at it, please?

FWIW: The problem seems to be in the last patch: virtio_is_supported()
is now not called anymore, and so virtio_get_device_type() now returns
the wrong type.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]