From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38286)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <groug@kaod.org>) id 1c6fAM-0005Rf-JB
	for qemu-devel@nongnu.org; Tue, 15 Nov 2016 09:56:55 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <groug@kaod.org>) id 1c6fAI-0001kf-Nz
	for qemu-devel@nongnu.org; Tue, 15 Nov 2016 09:56:54 -0500
Received: from mo53.mail-out.ovh.net ([178.32.228.53]:41825)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <groug@kaod.org>) id 1c6fAI-0001kL-Io
	for qemu-devel@nongnu.org; Tue, 15 Nov 2016 09:56:50 -0500
Received: from player158.ha.ovh.net (b7.ovh.net [213.186.33.57])
	by mo53.mail-out.ovh.net (Postfix) with ESMTP id EDEE44387D
	for <qemu-devel@nongnu.org>; Tue, 15 Nov 2016 15:56:48 +0100 (CET)
Date: Tue, 15 Nov 2016 15:56:42 +0100
From: Greg Kurz <groug@kaod.org>
Message-ID: <20161115155642.345d1863@bahia>
In-Reply-To: <CAJSP0QV5SaeOBtNjUC2dtripNhucLKm6xzk=buHdiwjYHw4MUg@mail.gmail.com>
References: <CAJSP0QWWHEpqgJPg4tufNsbOBDCZBj6qiCupT2fznj2VHFGjBA@mail.gmail.com>
	<c37685c9-16ab-a0aa-0592-eccc0e077122@redhat.com>
	<20161115110956.5393749d@bahia>
	<CAJSP0QV5SaeOBtNjUC2dtripNhucLKm6xzk=buHdiwjYHw4MUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] QEMU postcopy-test failing on ppc64
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Laurent Vivier <lvivier@redhat.com>, Dave Gilbert <dgilbert@redhat.com>, Andrea Arcangeli <aarcange@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

On Tue, 15 Nov 2016 11:14:57 +0000
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.
> 

And you cannot install a PPC64 BE distro on this POWER7 host and use
kvm_hv instead ?

> 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.
> 
> Stefan