qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Wei Huang <wei@redhat.com>, "Emilio G. Cota" <cota@braap.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	quintela@redhat.com,
	"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
	qemu-devel@nongnu.org, i.maximets@samsung.com, den@openvz.org
Subject: Re: [Qemu-devel] [PULL 2/7] tests/migration: Enable the migration test on s390x, too
Date: Fri, 19 Oct 2018 12:42:45 +0200	[thread overview]
Message-ID: <9d6f3d79-fc23-4cdc-1a4c-7b3c4cf939f0@redhat.com> (raw)
In-Reply-To: <590abdea-cd12-651b-7130-86c1786da99a@redhat.com>

On 2018-10-18 16:53, Wei Huang wrote:
> 
> 
> On 10/18/2018 07:43 AM, Emilio G. Cota wrote:
>> On Thu, Oct 18, 2018 at 14:38:01 +0200, Thomas Huth wrote:
>>> On 2018-10-17 21:28, Emilio G. Cota wrote:
>>>> Can anyone reproduce this? Otherwise, let me know what other info
>>>> I could provide.
>>>
>>> I've finally been able to reproduce it - seems like it only happens here
>>> when the host is under heavy load.
> 
> Given that it only happens under heavy load, could the failure be caused
> by migration thresholds defined in migrate_postcopy_prepare()? You can
> play with "max-bandwidth", "downtime-limit" and others to see if it helps.

David suggested on IRC yesterday that this problem might be the same as
with the ppc64 migration test: It does not work with TCG, only with KVM.

I've now done some tests, and indeed, I can not reproduce the problem
when running with KVM on a s390x host. But as soon as I disable the kvm
kernel module and run the test with TCG there, the problem occurs again.

So I think I'll send a patch to disable this test with TCG for now. Once
the problem with TCG has been solved, we can enable it again.

 Thomas

  reply	other threads:[~2018-10-19 10:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 19:25 [Qemu-devel] [PULL 0/7] migration queue Dr. David Alan Gilbert (git)
2018-10-11 19:25 ` [Qemu-devel] [PULL 1/7] tests: Add migration test for aarch64 Dr. David Alan Gilbert (git)
2018-10-11 19:25 ` [Qemu-devel] [PULL 2/7] tests/migration: Enable the migration test on s390x, too Dr. David Alan Gilbert (git)
2018-10-17 19:28   ` Emilio G. Cota
2018-10-18  4:59     ` Thomas Huth
2018-10-18 12:38     ` Thomas Huth
2018-10-18 12:43       ` Emilio G. Cota
2018-10-18 14:53         ` Wei Huang
2018-10-19 10:42           ` Thomas Huth [this message]
2018-10-11 19:25 ` [Qemu-devel] [PULL 3/7] migration: Stop postcopy fault thread before notifying Dr. David Alan Gilbert (git)
2018-10-11 19:25 ` [Qemu-devel] [PULL 4/7] vhost-user: Fix userfaultfd leak Dr. David Alan Gilbert (git)
2018-10-11 19:25 ` [Qemu-devel] [PULL 5/7] vhost-user: Don't ask for reply on postcopy mem table set Dr. David Alan Gilbert (git)
2018-10-11 19:25 ` [Qemu-devel] [PULL 6/7] qmp, hmp: make subsystem/system-vendor identities optional Dr. David Alan Gilbert (git)
2018-10-11 19:25 ` [Qemu-devel] [PULL 7/7] migration-test: Only generate a single target architecture Dr. David Alan Gilbert (git)
2018-10-12 10:56 ` [Qemu-devel] [PULL 0/7] migration queue Peter Maydell

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=9d6f3d79-fc23-4cdc-1a4c-7b3c4cf939f0@redhat.com \
    --to=thuth@redhat.com \
    --cc=cota@braap.org \
    --cc=den@openvz.org \
    --cc=dgilbert@redhat.com \
    --cc=i.maximets@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=wei@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).