From: Jason Baron <jbaron@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, aliguori@us.ibm.com,
quintela@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] qtest: add migration testing
Date: Thu, 13 Dec 2012 17:02:20 -0500 [thread overview]
Message-ID: <cover.1355435056.git.jbaron@redhat.com> (raw)
Hi,
Add a basic qtest for migration testing. Currently, it just tests a migrate of
machine 'pc' on the same host. Would be nice to extend to multiple machine
versions, but that requires multiple binaries, which could be done, but is
perhaps a bit awkward from qtest? Testing different machine versions within
the same binary doesn't seem like a real world test case to me. Currently,
the test aborts, if the migrate takes more than 2 minutes.
In any case, the test currently fails for q35, since ahci migration suport
isn't in place. Thus, I intend to add q35 testing here, once those ahci
migration patches are accepted.
Thanks,
-Jason
Jason Baron (3):
qtest: Enable creation of multiple qemu instances
qtest: extend qtest_qmp() to fill in the reply
qtest: add migrate-test
tests/Makefile | 8 ++-
tests/libqtest.c | 48 ++++++++++--------
tests/libqtest.h | 4 +-
tests/migrate-test.c | 140 ++++++++++++++++++++++++++++++++++++++++++++++++++
4 files changed, 175 insertions(+), 25 deletions(-)
create mode 100644 tests/migrate-test.c
next reply other threads:[~2012-12-13 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:02 Jason Baron [this message]
2012-12-13 22:02 ` [Qemu-devel] [PATCH 1/3] qtest: Enable creation of multiple qemu instances Jason Baron
2012-12-14 20:30 ` Blue Swirl
2012-12-15 9:14 ` Paolo Bonzini
2012-12-15 9:20 ` Blue Swirl
2012-12-17 17:13 ` Jason Baron
2012-12-19 19:42 ` Blue Swirl
2012-12-13 22:02 ` [Qemu-devel] [PATCH 3/3] qtest: add migrate-test Jason Baron
2012-12-14 8:08 ` Paolo Bonzini
2012-12-14 16:14 ` Jason Baron
2012-12-14 17:25 ` Paolo Bonzini
2012-12-13 22:02 ` [Qemu-devel] [PATCH 2/3] qtest: extend qtest_qmp() to fill in the reply Jason Baron
2012-12-14 0:07 ` Andreas Färber
2012-12-14 16:10 ` Jason Baron
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=cover.1355435056.git.jbaron@redhat.com \
--to=jbaron@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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 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).