[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL


  • To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>, 'Jürgen Groß' <jgross@xxxxxxxx>, osstest service owner <osstest-admin@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
  • Date: Mon, 30 Sep 2019 08:15:41 +0000
  • Accept-language: en-GB, en-US
  • Authentication-results: esa6.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=Paul.Durrant@xxxxxxxxxx; spf=Pass smtp.mailfrom=Paul.Durrant@xxxxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxx
  • Delivery-date: Mon, 30 Sep 2019 08:15:49 +0000
  • Ironport-sdr: /buBcKpDPaAnXWwf1xMGNCXT6RU7QlSFNwmGsfRviRHlNeHYdaVs22pkYFT+z65aRIOzCUPOmU 0mQjS8zE6PW4G7oaGBhwBLm/1+7EO41PqDChRwZQblit6x3h/AdCcDYjHfRBqgSXI0Fh42xhtC 97aO7QjnrTZDh9L6kTzDcGFeCxeb3pJ3ttDvW/jZ5ZnzDgBz6fWmHi/gE58hbYdRhni8WO9Ry4 xGd+3f9AMDRvl311LhrGmsy/uTyvUrimpdtyZZOq7V5GgTp4feu7pJDUoU/gOyES6w5J5vhH+4 OQk=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHVd0cpVJyIDfIZSUSz/TKxkhVs4adDmO+AgAATlQCAACx04IAABosA
  • Thread-topic: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL

> -----Original Message-----
> From: Xen-devel <xen-devel-bounces@xxxxxxxxxxxxxxxxxxxx> On Behalf Of Paul 
> Durrant
> Sent: 30 September 2019 08:51
> To: 'Jürgen Groß' <jgross@xxxxxxxx>; osstest service owner 
> <osstest-admin@xxxxxxxxxxxxxx>; xen-
> devel@xxxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> 
> > -----Original Message-----
> > From: Jürgen Groß <jgross@xxxxxxxx>
> > Sent: 30 September 2019 08:12
> > To: osstest service owner <osstest-admin@xxxxxxxxxxxxxx>; 
> > xen-devel@xxxxxxxxxxxxxxxxxxxx; Paul
> Durrant
> > <Paul.Durrant@xxxxxxxxxx>
> > Subject: Re: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
> >
> > On 30.09.19 08:01, Jürgen Groß wrote:
> > > On 30.09.19 06:23, osstest service owner wrote:
> > >> flight 141990 xen-unstable real [real]
> > >> http://logs.test-lab.xenproject.org/osstest/logs/141990/
> > >>
> > >> Regressions :-(
> > >>
> > >> Tests which did not succeed and are blocking,
> > >> including tests which could not be run:
> > >>   test-amd64-amd64-xl-qemut-debianhvm-amd64  7 xen-boot    fail REGR.
> > >> vs. 141822
> > >>   test-amd64-amd64-libvirt     12 guest-start              fail REGR.
> > >> vs. 141822
> > >>   test-amd64-i386-libvirt-xsm  12 guest-start              fail REGR.
> > >> vs. 141822
> > >>   test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host
> > >> fail REGR. vs. 141822
> > >>   test-amd64-i386-libvirt      12 guest-start              fail REGR.
> > >> vs. 141822
> > >>   test-amd64-amd64-migrupgrade 22 guest-migrate/src_host/dst_host fail
> > >> REGR. vs. 141822
> > >>   test-amd64-i386-libvirt-pair 22 guest-migrate/src_host/dst_host fail
> > >> REGR. vs. 141822
> > >>   test-amd64-i386-migrupgrade 22 guest-migrate/src_host/dst_host fail
> > >> REGR. vs. 141822
> > >>   test-arm64-arm64-examine    11 examine-serial/bootloader fail REGR.
> > >> vs. 141822
> > >>   test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10
> > >> debian-hvm-install fail REGR. vs. 141822
> > >>   test-arm64-arm64-libvirt-xsm 12 guest-start              fail REGR.
> > >> vs. 141822
> > >>   test-amd64-amd64-libvirt-vhd 10 debian-di-install        fail REGR.
> > >> vs. 141822
> > >>   test-armhf-armhf-libvirt     12 guest-start              fail REGR.
> > >> vs. 141822
> > >>   test-armhf-armhf-libvirt-raw 10 debian-di-install        fail REGR.
> > >> vs. 141822
> > >
> > > Several of the failures seem to be related to commit babde47a3feda6dd4
> > > ("introduce a 'passthrough' configuration option to xl.cfg").
> > >
> > > I think the assert() in lixl_create.c (line 589) should just be dropped?
> > >
> > >          assert(info->passthrough != LIBXL_PASSTHROUGH_ENABLED);
> > >          LOG(DETAIL, "passthrough: %s",
> > >              libxl_passthrough_to_string(info->passthrough));
> > >
> > >          if (info->passthrough != LIBXL_PASSTHROUGH_DISABLED)
> > >              create.flags |= XEN_DOMCTL_CDF_iommu;
> > >
> > >          if (info->passthrough == LIBXL_PASSTHROUGH_SYNC_PT)
> > >              create.iommu_opts |= XEN_DOMCTL_IOMMU_no_sharept;
> > >
> > > Or the if () statements after that are just plain wrong?
> >
> > I misread the code.
> >
> > But nevertheless there is something wrong...
> >
> 
> Ok, I'll take a look now.
> 

I can't find anything conclusive in the logs, but it looks like it's mainly AMD 
h/w that's the problem and on at least one of the test failures I see lots of 
this kind of thing in the serial log:

Sep 29 17:33:55.316422 [  169.828563] AMD-Vi: Event logged [[  169.831798] 
IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 
flags=0x0020]
Sep 29 17:33:55.376595 [  169.840481] AMD-Vi: Event logged [[  169.843716] 
IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 
flags=0x0020]
Sep 29 17:33:55.388469 [  169.852398] AMD-Vi: Event logged [[  169.855627] 
IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 
flags=0x0020]
Sep 29 17:33:55.400486 [  169.864311] AMD-Vi: Event logged [[  169.867540] 
IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 
flags=0x0020]
Sep 29 17:33:55.412559 [  169.876224] AMD-Vi: Event logged [[  169.879458] 
IO_PAGE_FAULT device=00:13.1 domain=0x0006 address=0x0000000000000080 
flags=0x0020]

I'll try to find an AMD rig and see if I can repro a failure.

  Paul

>   Paul
> 
> >
> > Juergen
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxx
> https://lists.xenproject.org/mailman/listinfo/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.