From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c6f2M-0003CT-GT for qemu-devel@nongnu.org; Tue, 15 Nov 2016 09:48:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c6f2H-0007B1-SK for qemu-devel@nongnu.org; Tue, 15 Nov 2016 09:48:38 -0500 Received: from mail-wm0-x243.google.com ([2a00:1450:400c:c09::243]:34085) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c6f2H-0007Aq-L8 for qemu-devel@nongnu.org; Tue, 15 Nov 2016 09:48:33 -0500 Received: by mail-wm0-x243.google.com with SMTP id g23so578631wme.1 for ; Tue, 15 Nov 2016 06:48:33 -0800 (PST) Date: Tue, 15 Nov 2016 14:48:30 +0000 From: Stefan Hajnoczi Message-ID: <20161115144830.GC17672@stefanha-x1.localdomain> References: <20161115110956.5393749d@bahia> <20161115122056.GG2038@work-vm> <97c72871-71f8-9385-c67d-45bc32e4c9c8@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2/5bycvrmDh4d1IB" Content-Disposition: inline In-Reply-To: <97c72871-71f8-9385-c67d-45bc32e4c9c8@redhat.com> Subject: Re: [Qemu-devel] QEMU postcopy-test failing on ppc64 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laurent Vivier Cc: "Dr. David Alan Gilbert" , Greg Kurz , Andrea Arcangeli , qemu-devel --2/5bycvrmDh4d1IB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 15, 2016 at 01:58:38PM +0100, Laurent Vivier wrote: >=20 >=20 > 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 wrote: > >>> On Tue, 15 Nov 2016 10:53:35 +0100 > >>> Laurent Vivier 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 =3D 1b last_byte= =3D 1a > >>>>> current =3D 7c hit_edge =3D 1 > >>>>> Memory content inconsistency at 5af5000 first_byte =3D 1b last_byte= =3D 7c > >>>>> current =3D 1b hit_edge =3D 1 > >>>>> Memory content inconsistency at 5e59000 first_byte =3D 1b last_byte= =3D 1b > >>>>> current =3D 1a hit_edge =3D 1 > >>>>> ** > >>>>> ERROR:tests/postcopy-test.c:345:check_guests_ram: 'bad' should be F= ALSE > >>>>> 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. > >=20 > > I don't think it's new with 2.8 (Laurent?) and I think it's actually > > a kernel issue that needs fixing. >=20 > I's not a regression and I think it's a kernel issue. >=20 > 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). >=20 > 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. Stefan --2/5bycvrmDh4d1IB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJYKyA+AAoJEJykq7OBq3PI9nkIAIO8dMC+N983TXQ6fAgthyuG XCky6g+ZCniXExgIL8587enixu9wjVBekZQcmOGFbug50mvMj9nlrJI7iOcpUyOx +e33DjzTRisynGDcDEYeoTDXg8ylIxU7rgtaOagB/FI5IVBBjDF/4CtLdQ1dPKhB +mt48hHprlVZo9mpFBHmnADhIRj9YYPUwmGetItO/jMjgkWgX5uiP/BMyDtt2ExE ZJkV/Qc2C9EciE9eDYVNhbBAEYrqg3E9BbSiM16ppnoTScF5dqYEkgDAndXME6+N Cup2WLj1DIuctseNZZdKLI2nnRivyKHfCnuTGjtHrMRU4YrV1xCxy9r8C7TsWB4= =icyO -----END PGP SIGNATURE----- --2/5bycvrmDh4d1IB--