From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Victor Kaplansky <victork@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 for-2.11 0/2] Improvements for the pxe tester
Date: Fri, 11 Aug 2017 11:49:22 +0200 [thread overview]
Message-ID: <20170811114922.2edda3a7.cohuck@redhat.com> (raw)
In-Reply-To: <1502431076-22849-1-git-send-email-thuth@redhat.com>
On Fri, 11 Aug 2017 07:57:54 +0200
Thomas Huth <thuth@redhat.com> wrote:
> The first patch improves the buffer handling in the pxe tester a
> little bit by allocating a separate buffer on the heap for each
> architecture. This also gets rid of the huge pre-initialized
> array in the tester, shrinking the size of the executable by
> half of a megabyte!
> The second patch adds s390x support to the pxe tester. Starting
> with QEMU 2.10, the guest firmware on s390x can now net-boot via
> TFTP, too, so we can automatically test this code in the pxe tester.
>
> v2: Adressed Cornelia's review feedback from the first version, e.g.:
> - Use g_malloc0() instead of g_malloc()
> - Use sizeof with parentheses
>
> Thomas Huth (2):
> tests/boot-sector: Do not overwrite the x86 buffer on other
> architectures
> tests/pxe: Check virtio-net-ccw on s390x
>
> tests/Makefile.include | 1 +
> tests/boot-sector.c | 61 +++++++++++++++++++++++++++++++++++++-------------
> tests/pxe-test.c | 7 ++++++
> 3 files changed, 54 insertions(+), 15 deletions(-)
>
Haven't reviewed the updates yet, but tried it out (on my laptop and on
a z/VM guest). Laptop went fine; on the z/VM guest, I forgot to turn on
vm.allocate_pgste at first:
TEST: tests/pxe-test... (pid=56084)
/s390x/pxe/virtio-ccw: ioctl(KVM_CREATE_VM) failed: 22 Invalid argument
Host kernel setup problem detected. Please verify:
- for kernels supporting the switch_amode or user_mode parameters, whether
user space is running in primary address space
- for kernels supporting the vm.allocate_pgste sysctl, whether it is enabled
qemu-system-s390x: failed to initialize KVM: Invalid argument
qemu-system-s390x: Back to tcg accelerator
OK
PASS: tests/pxe-test
It does the correct fallback (the need for allocate_pgste will go away
with future kernels), so this is fine. However, it prompted me to test
with --disable-tcg:
TEST: tests/boot-serial-test... (pid=60499)
/s390x/boot-serial/s390-ccw-virtio: qemu-system-s390x: -machine accel=tcg: No accelerator found
socket_accept failed: Resource temporarily unavailable
**
ERROR:/root/git/qemu/tests/libqtest.c:212:qtest_init_without_qmp_handshake: assertion failed: (s->fd >= 0 && s->qmp_fd >= 0)
FAIL
GTester: last random seed: R02S83c8a1860bbd8c2658647407c7070b7e
(pid=60503)
FAIL: tests/boot-serial-test
There are probably more tests that rely on tcg always being available,
which is no longer true. (Also, the boot-serial test should probably
check if qemu even started rather than run into in a timeout.)
[Your patches are fine, but I think we really need to consider tests
and accelerators.]
next prev parent reply other threads:[~2017-08-11 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 5:57 [Qemu-devel] [PATCH v2 for-2.11 0/2] Improvements for the pxe tester Thomas Huth
2017-08-11 5:57 ` [Qemu-devel] [PATCH v2 for-2.11 1/2] tests/boot-sector: Do not overwrite the x86 buffer on other architectures Thomas Huth
2017-08-15 14:54 ` Cornelia Huck
2017-08-11 5:57 ` [Qemu-devel] [PATCH v2 for-2.11 2/2] tests/pxe: Check virtio-net-ccw on s390x Thomas Huth
2017-08-15 15:26 ` Cornelia Huck
2017-08-11 9:49 ` Cornelia Huck [this message]
2017-08-11 10:19 ` [Qemu-devel] [PATCH v2 for-2.11 0/2] Improvements for the pxe tester Cornelia Huck
2017-08-11 10:52 ` Thomas Huth
2017-08-11 11:43 ` Cornelia Huck
2017-08-14 14:35 ` Michael S. Tsirkin
2017-08-15 15:27 ` Cornelia Huck
2017-08-18 11:29 ` Cornelia Huck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170811114922.2edda3a7.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=victork@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).