qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>,
	"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, wei@redhat.com,
	i.maximets@samsung.com, den@openvz.org,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PULL 2/7] tests/migration: Enable the migration test on s390x, too
Date: Thu, 18 Oct 2018 14:38:01 +0200	[thread overview]
Message-ID: <286c9ba0-05d9-02ec-7f59-34b34a66be2c@redhat.com> (raw)
In-Reply-To: <20181017192826.GA7385@flamenco>

On 2018-10-17 21:28, Emilio G. Cota wrote:
> On Thu, Oct 11, 2018 at 20:25:08 +0100, Dr. David Alan Gilbert (git) wrote:
>> From: Thomas Huth <thuth@redhat.com>
>>
>> We can re-use the s390-ccw bios code to implement a small firmware
>> for a s390x guest which prints out the "A" and "B" characters and
>> modifies the memory, as required for the migration test.
>>
>> [quintela: Converted the compile script to Makefile rules]
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> Message-Id: <1539078677-25396-1-git-send-email-thuth@redhat.com>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>   Fixed up Makefile since the aarch patch sneaked in first
> 
> I suspect this test is giving me intermittent hangs. I've seen the hangs
> in different machines, but when they're lightly loaded the
> hang happens more frequently.
> 
> To reproduce:
> 
> $ ./configure --target-list=s390x-softmmu
> $ make clean && make
> $ for i in $(seq 0 150); do echo $i && make -j check-qtest || break; done
> 
> It usually ends up hanging before 50 runs. When the hang happens, I see
> two qemu-system-s390x processes with:
> 
> -serial file:/tmp/migration-test-0FZErQ/dest_serial
> 
> as an argument, among others. That means the migration test is the
> one hanging, correct?
> 
> Attaching with gdb just shows the TCG thread waiting for work
> in qemu_tcg_rr_wait_io_event.
> 
> 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.

... not sure whether I've got time to debug this before KVM forum, so if
it bugs you, feel free to send a patch to disable the test in
tests/Makefile.include for s390x again.

 Thomas

  parent reply	other threads:[~2018-10-18 12:38 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 [this message]
2018-10-18 12:43       ` Emilio G. Cota
2018-10-18 14:53         ` Wei Huang
2018-10-19 10:42           ` Thomas Huth
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=286c9ba0-05d9-02ec-7f59-34b34a66be2c@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).