qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL 00/26] s390x updates (and friends)


From: Thomas Huth
Subject: Re: [Qemu-devel] [PULL 00/26] s390x updates (and friends)
Date: Thu, 1 Mar 2018 12:17:12 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

On 01.03.2018 11:27, Cornelia Huck wrote:
> On Thu, 1 Mar 2018 10:12:53 +0000
> Peter Maydell <address@hidden> wrote:
> 
>> On 27 February 2018 at 13:21, Cornelia Huck <address@hidden> wrote:
>>> The following changes since commit 0a773d55ac76c5aa89ed9187a3bc5af8c5c2a6d0:
>>>
>>>   maintainers: Add myself as a OpenBSD maintainer (2018-02-23 12:05:07 
>>> +0000)
>>>
>>> are available in the git repository at:
>>>
>>>   git://github.com/cohuck/qemu tags/s390x-20180227
>>>
>>> for you to fetch changes up to eae9f29130f3ed40ad77f40a3bae4b9ebff28907:
>>>
>>>   Merge tag 'tags/s390-ccw-bios-2018-02-26' into s390-next (2018-02-27 
>>> 13:54:37 +0100)
>>>
>>> ----------------------------------------------------------------
>>> - add query-cpus-fast and deprecate query-cpus, while adding s390 cpu
>>>   information
>>> - remove s390x memory hotplug implementation, which is not useable in
>>>   this form
>>> - add boot menu support in the s390-ccw bios
>>> - expose s390x guest crash information
>>> - fixes and cleaups
>>>
>>> ----------------------------------------------------------------  
>>
>> Something seems to be broken here: this failed 'make check' on
>> most hosts with
>> TEST: tests/pxe-test... (pid=48288)
>>   /s390x/pxe/ipv4/s390-ccw-virtio/virtio-net-ccw:                      **
>> ERROR:/home/pm215/qemu/tests/boot-sector.c:158:boot_sector_test:
>> assertion failed (signature == SIGNATURE): (0x00000000 == 0x0000dead)
>>
>> and just failed without an error on the rest (with the exception of
>> my Linux box, where that test hung entirely with qemu-system-s390x
>> using 100% of cpu).
>>
>> thanks
>> -- PMM
> 
> Hm, smells bootloader patches related... Thomas?
FWIW, I just bisected the issue and it's not due to the bootloader
changes, but due to this one:

 f26852aa31d49bf83a8defd65538137a2f9da82c is the first bad commit
 commit f26852aa31d49bf83a8defd65538137a2f9da82c
 Author: David Hildenbrand <address@hidden>
 Date:   Tue Feb 13 17:12:40 2018 +0100
 Subject: s390x/tcg: fix disabling/enabling DAT

  Thomas



reply via email to

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