From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-s390x@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [RFC PATCH 5/5] tests: stop skipping migration test on s390x/ppc64
Date: Tue, 28 Jun 2022 15:18:43 +0200 [thread overview]
Message-ID: <c23d007c-98d3-a8b4-269c-5b65d53064db@redhat.com> (raw)
In-Reply-To: <20220628105434.295905-6-berrange@redhat.com>
On 28/06/2022 12.54, Daniel P. Berrangé wrote:
> There have been checks put into the migration test which skip it in a
> few scenarios
>
> * ppc64 TCG
> * ppc64 KVM with kvm-pr
> * s390x TCG
>
> In the original commits there are references to unexplained hangs in
> the test. There is no record of details of where it was hanging, but
> it is suspected that these were all a result of the max downtime limit
> being set at too low a value to guarantee convergance.
>
> Since a previous commit bumped the value from 1 second to 30 seconds,
> it is believed that hangs due to non-convergance should be eliminated
> and thus worth trying to remove the skipped scenarios.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> tests/qtest/migration-test.c | 21 ---------------------
> 1 file changed, 21 deletions(-)
>
> diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
> index 9e64125f02..500169f687 100644
> --- a/tests/qtest/migration-test.c
> +++ b/tests/qtest/migration-test.c
> @@ -2085,7 +2085,6 @@ static bool kvm_dirty_ring_supported(void)
> int main(int argc, char **argv)
> {
> char template[] = "/tmp/migration-test-XXXXXX";
> - const bool has_kvm = qtest_has_accel("kvm");
> int ret;
>
> g_test_init(&argc, &argv, NULL);
> @@ -2094,26 +2093,6 @@ int main(int argc, char **argv)
> return g_test_run();
> }
>
> - /*
> - * On ppc64, the test only works with kvm-hv, but not with kvm-pr and TCG
> - * is touchy due to race conditions on dirty bits (especially on PPC for
> - * some reason)
> - */
> - if (g_str_equal(qtest_get_arch(), "ppc64") &&
> - (!has_kvm || access("/sys/module/kvm_hv", F_OK))) {
> - g_test_message("Skipping test: kvm_hv not available");
> - return g_test_run();
> - }
> -
> - /*
> - * Similar to ppc64, s390x seems to be touchy with TCG, so disable it
> - * there until the problems are resolved
> - */
> - if (g_str_equal(qtest_get_arch(), "s390x") && !has_kvm) {
> - g_test_message("Skipping test: s390x host with KVM is required");
> - return g_test_run();
> - }
I'm in favor of giving this now a try ... we still can revert the patch if
it does not work out.
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2022-06-28 13:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 10:54 [PATCH 0/5] tests: improve reliability of migration test Daniel P. Berrangé
2022-06-28 10:54 ` [PATCH 1/5] tests: wait max 120 seconds for migration test status changes Daniel P. Berrangé
2022-06-28 12:47 ` Laurent Vivier
2022-06-28 12:49 ` Thomas Huth
2022-06-28 10:54 ` [PATCH 2/5] tests: wait for migration completion before looking for STOP event Daniel P. Berrangé
2022-06-28 12:47 ` Laurent Vivier
2022-06-28 14:08 ` Dr. David Alan Gilbert
2022-06-28 14:10 ` Daniel P. Berrangé
2022-06-28 10:54 ` [PATCH 3/5] tests: increase migration test converge downtime to 30 seconds Daniel P. Berrangé
2022-06-28 12:47 ` Laurent Vivier
2022-06-28 10:54 ` [PATCH 4/5] tests: use consistent bandwidth/downtime limits in migration tests Daniel P. Berrangé
2022-06-28 14:16 ` Dr. David Alan Gilbert
2022-06-28 10:54 ` [RFC PATCH 5/5] tests: stop skipping migration test on s390x/ppc64 Daniel P. Berrangé
2022-06-28 13:18 ` Thomas Huth [this message]
2022-07-05 8:06 ` Thomas Huth
2022-07-05 8:09 ` Daniel P. Berrangé
2022-07-05 8:38 ` Dr. David Alan Gilbert
2022-06-28 13:19 ` [PATCH 0/5] tests: improve reliability of migration test Thomas Huth
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=c23d007c-98d3-a8b4-269c-5b65d53064db@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).