Thomas Huth <th...@redhat.com> writes: > On 30.08.2017 10:59, Cornelia Huck wrote: > [...] >>>> On s390x: >>>> TEST: tests/ivshmem-test... (pid=63617) >>>> /x86_64/ivshmem/single: OK >>>> /x86_64/ivshmem/hotplug: OK >>>> /x86_64/ivshmem/memdev: OK >>>> /x86_64/ivshmem/pair: OK >>>> /x86_64/ivshmem/server-msi: >>>> qemu-system-x86_64: -device ivshmem-doorbell,chardev=chr0,vectors=2: >>>> server sent invalid ID message >>>> Broken pipe >>>> FAIL >>>> GTester: last random seed: R02Sda000f7be5ce27b3dfbb03d12f297b69 >>>> (pid=63640) >>>> /x86_64/ivshmem/server-irq: >>>> qemu-system-x86_64: -device >>>> ivshmem,size=1M,msi=off,chardev=chr0,vectors=2: server sent invalid ID >>>> message >>>> Broken pipe >>>> FAIL >>>> GTester: last random seed: R02S5a236dbcac35545cc34c0131fbc06162 >>>> (pid=63648) >>>> FAIL: tests/ivshmem-test >> >> ...but this is a different problem (i.e., it can't be tracked down to >> commit b4ba67d9a7). I'm not sure whether that one ever worked. Might be >> an endianness problem (a quick test on another BE platform could >> confirm.) > > This also fails on a big endian ppc64 host machine: > > $ uname -m > ppc64 > $ V=1 QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 tests/ivshmem-test > -m slow > /x86_64/ivshmem/single: OK > /x86_64/ivshmem/hotplug: OK > /x86_64/ivshmem/memdev: OK > /x86_64/ivshmem/pair: OK > /x86_64/ivshmem/server-msi: qemu-system-x86_64: -device > ivshmem-doorbell,chardev=chr0,vectors=2: server sent invalid ID message > Broken pipe
Botched endian conversion?
