All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU postcopy-test failing on ppc64
Date: Tue, 15 Nov 2016 16:03:38 +0100	[thread overview]
Message-ID: <20161115160338.4b6f0cf6@bahia> (raw)
In-Reply-To: <20161115144830.GC17672@stefanha-x1.localdomain>

[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]

On Tue, 15 Nov 2016 14:48:30 +0000
Stefan Hajnoczi <stefanha@gmail.com> wrote:

> On Tue, Nov 15, 2016 at 01:58:38PM +0100, Laurent Vivier wrote:
> > 
> > 
> > On 15/11/2016 13:20, Dr. David Alan Gilbert wrote:  
> > > * Stefan Hajnoczi (stefanha@gmail.com) wrote:  
> > >> On Tue, Nov 15, 2016 at 10:09 AM, Greg Kurz <groug@kaod.org> wrote:  
> > >>> On Tue, 15 Nov 2016 10:53:35 +0100
> > >>> Laurent Vivier <lvivier@redhat.com> wrote:
> > >>>  
> > >>>> On 14/11/2016 21:52, Stefan Hajnoczi wrote:  
> > >>>>> I hit a failure running "make check" on ppc64 for the first time.  Ideas?
> > >>>>>
> > >>>>> Stefan
> > >>>>>
> > >>>>> commit 682df581c65ed2c1b9e77093e332214ecaa1ee93
> > >>>>>
> > >>>>>   GTESTER check-qtest-ppc64
> > >>>>> Memory content inconsistency at 5af4000 first_byte = 1b last_byte = 1a
> > >>>>> current = 7c hit_edge = 1
> > >>>>> Memory content inconsistency at 5af5000 first_byte = 1b last_byte = 7c
> > >>>>> current = 1b hit_edge = 1
> > >>>>> Memory content inconsistency at 5e59000 first_byte = 1b last_byte = 1b
> > >>>>> current = 1a hit_edge = 1
> > >>>>> **
> > >>>>> ERROR:tests/postcopy-test.c:345:check_guests_ram: 'bad' should be FALSE
> > >>>>> GTester: last random seed: R02S9d79166a1ca7e21940a0f4b0b1255d5b
> > >>>>>  
> > >>>>
> > >>>> Are you using KVM PR?
> > >>>>
> > >>>> it  was working fine with TCG and KVM HV.
> > >>>>
> > >>>> Apparently, USERFAULTFD doesn't work with KVM PR.
> > >>>>
> > >>>> I've already seen this kind of error with nested KVM on Power:
> > >>>> guest in guest with KVM PR in host.
> > >>>>
> > >>>> This problem was reported on IRC by Greg if I remember correctly (CC:)
> > >>>>  
> > >>>
> > >>> Yeah I hit this when running make check in a PPC64 BE guest which
> > >>> has kvm_pr loaded. I did not find time to investigate though... I've
> > >>> switched to run make check on bare metal POWER7 instead.  
> > >>
> > >> Right, it's POWER7 PPC64 BE with kvm_pr.
> > >>
> > >> If this should be fixed for QEMU 2.8 please add it to
> > >> http://qemu-project.org/Planning/2.8 and I'll track it (i.e. won't
> > >> release before it's resolved).
> > >>
> > >> If this is a known issue that will be in QEMU 2.8 please add it to
> > >> http://qemu-project.org/ChangeLog/2.8#Known_issues.  
> > > 
> > > I don't think it's new with 2.8 (Laurent?) and I think it's actually
> > > a kernel issue that needs fixing.  
> > 
> > I's not a regression and I think it's a kernel issue.
> > 
> > As it has never worked with KVM PR and can't be fixed at QEMU level, we
> > can't solve it for 2.8 (no tracking).
> > 
> > I'm going to update the know issues for 2.8.
> > [and I'm going to try to understand what really happens]  
> 
> Should the test be skipped on KVM PR?
> 
> It's a shame that make check fails.
> 

Yeah I agree this is lame but KVM PR isn't very cherished these days...

Since postcopy-test runs QEMU with -accel kvm:tcg, a possible workaround is
to kick KVM out of the environment you're running make check in.

> Stefan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-11-15 15:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 20:52 [Qemu-devel] QEMU postcopy-test failing on ppc64 Stefan Hajnoczi
2016-11-15  9:43 ` Dr. David Alan Gilbert
2016-11-15  9:53 ` Laurent Vivier
2016-11-15 10:09   ` Greg Kurz
2016-11-15 11:14     ` Stefan Hajnoczi
2016-11-15 12:20       ` Dr. David Alan Gilbert
2016-11-15 12:58         ` Laurent Vivier
2016-11-15 14:48           ` Stefan Hajnoczi
2016-11-15 15:03             ` Greg Kurz [this message]
2016-11-15 15:07               ` Laurent Vivier
2016-11-15 15:08                 ` Dr. David Alan Gilbert
2016-11-15 15:12                   ` Laurent Vivier
2016-11-15 18:01                 ` Greg Kurz
2016-11-15 18:24                   ` Laurent Vivier
2016-11-15 20:02                     ` Greg Kurz
2016-11-16  1:35                       ` Thomas Huth
2016-11-15 14:56       ` Greg Kurz
2016-11-15 15:18         ` Stefan Hajnoczi
2016-11-15 17:26           ` Thomas Huth
2016-11-15 17:43             ` Dr. David Alan Gilbert
2016-11-15 18:13               ` Greg Kurz
2016-11-15 18:48                 ` Thomas Huth
2016-11-15 19:00                   ` Eric Blake
2016-11-15 20:39                     ` Laurent Vivier
2016-11-15 20:44                       ` Laurent Vivier
2016-11-15 20:45                         ` Laurent Vivier
2016-11-15 20:26                   ` Greg Kurz

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=20161115160338.4b6f0cf6@bahia \
    --to=groug@kaod.org \
    --cc=aarcange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.