From: Markus Armbruster <armbru@redhat.com>
To: Germano Veit Michel <germano@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Juan Jose Quintela Carreira <quintela@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] migration: expose qemu_announce_self() via qmp
Date: Fri, 05 May 2017 08:13:00 +0200 [thread overview]
Message-ID: <87efw3u903.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <CANHSq5Bvpm-ofhCVvReDcAPJYpfHTgu3qanT+kaJU3KH1MViNw@mail.gmail.com> (Germano Veit Michel's message of "Fri, 5 May 2017 10:36:35 +1000")
Germano Veit Michel <germano@redhat.com> writes:
> Hi guys,
>
> Finally got some time to prepare V3.
>
> First of all Dave's trick is really useful to test it:
>
> ./x86_64-softmmu/qemu-system-x86_64 -nographic -nodefaults -netdev
> user,id=netuser -object filter-dump,id=dump,netdev=netuser,file=foo2
> -device e1000,netdev=netuser,mac=00:11:22:33:44:55 -monitor stdio
> QEMU 2.8.91 monitor - type 'help' for more information
> (qemu) announce-self
> (qemu) announce-self
> (qemu) qemu-system-x86_64: terminating on signal 2
>
> tshark -r foo2 | grep RARP
> 1 0.000000 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 2 0.050017 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 3 0.200077 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 4 0.450112 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 5 0.800090 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 13 5.583887 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 14 5.633079 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 15 5.783152 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 16 6.033130 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
> 17 6.383144 Cimsys_33:44:55 → Broadcast RARP 60 Who is
> 00:11:22:33:44:55? Tell 00:11:22:33:44:55
>
> Now for qtest:
>
> It is compiling and running my test:
>
> [....]
> CC tests/qmp-net-test.o
> LINK tests/qmp-net-test
> [....]
> GTESTER check-qtest-x86_64
>
> /bin/sh -c printf " %-7s %s\n" "GTESTER" "check-qtest-x86_64" &&
> QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 QTEST_QEMU_IMG=qemu-img
> MALLOC_PERTURB_=${MALLOC_PERTURB_:-$((RANDOM % 255 + 1))} gtester -k -q
> -m=quick [.....] tests/qmp-net-test [....]
>
> Weird is... is the test qemu running without NICs?
Please show us test/qmp-net-test.c.
> x86_64-softmmu/qemu-system-x86_64 -qtest unix:/tmp/qtest-17545.sock,nowait
> -qtest-log /dev/null -qmp unix:/tmp/qtest-17545.qmp,nowait -machine
> accel=qtest -display none -M q35,accel=tcg -chardev
> file,id=serial0,path=/tmp/qtest-boot-serial-HYHJ2e -no-shutdown -serial
> chardev:serial0 -device sga
>
> I was looking at this
> http://events.linuxfoundation.org/sites/events/files/slides/Testing%20QEMU%20emulated%20devices%20using%20qtest.pdf
> and it's pretty helpful. But I have no clues on how to actually check if
> the RARP packets really go out on each NIC. Any idea on how to implement
> this or is the smoke test enough?
I'd try to use filter-dump to capture the traffic, then compare the
actual captured traffic to the expected one.
next prev parent reply other threads:[~2017-05-05 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 0:16 [Qemu-devel] [PATCH V2] migration: expose qemu_announce_self() via qmp Germano Veit Michel
2017-03-03 10:39 ` Dr. David Alan Gilbert
2017-03-03 12:06 ` Markus Armbruster
2017-03-13 2:59 ` Germano Veit Michel
2017-03-13 5:24 ` Markus Armbruster
2017-03-13 8:51 ` Markus Armbruster
2017-03-27 16:31 ` Dr. David Alan Gilbert
2017-05-05 0:36 ` Germano Veit Michel
2017-05-05 6:13 ` Markus Armbruster [this message]
2017-05-05 9:26 ` Jason Wang
2017-03-06 4:02 ` Jason Wang
2017-05-11 21:37 ` Vlad Yasevich
2017-05-12 19:24 ` Dr. David Alan Gilbert
2017-05-12 21:16 ` Vlad Yasevich
2017-05-22 23:23 ` Germano Veit Michel
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=87efw3u903.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=germano@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.