xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [linux-3.18 bisection] complete test-amd64-amd64-xl-shadow
Date: Fri, 24 Aug 2018 09:51:51 +0000	[thread overview]
Message-ID: <170c45fbb00646ea89a5b82eff5ae821@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20180824095020.ysqrwl7gq7i3cfe5@citrix.com>

> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@citrix.com]
> Sent: 24 August 2018 10:50
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>; osstest service owner <osstest-
> admin@xenproject.org>; xen-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] [linux-3.18 bisection] complete test-amd64-amd64-
> xl-shadow
> 
> On Fri, Aug 24, 2018 at 10:44:09AM +0100, Paul Durrant wrote:
> > > -----Original Message-----
> > > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > > Sent: 24 August 2018 10:38
> > > To: Paul Durrant <Paul.Durrant@citrix.com>
> > > Cc: Wei Liu <wei.liu2@citrix.com>; osstest service owner <osstest-
> > > admin@xenproject.org>; xen-devel@lists.xenproject.org
> > > Subject: Re: [Xen-devel] [linux-3.18 bisection] complete test-amd64-
> amd64-
> > > xl-shadow
> > >
> > > On Fri, Aug 24, 2018 at 10:35:52AM +0100, Paul Durrant wrote:
> > > > > -----Original Message-----
> > > > > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > > > > Sent: 24 August 2018 10:35
> > > > > To: Paul Durrant <Paul.Durrant@citrix.com>
> > > > > Cc: Wei Liu <wei.liu2@citrix.com>; osstest service owner <osstest-
> > > > > admin@xenproject.org>; xen-devel@lists.xenproject.org
> > > > > Subject: Re: [Xen-devel] [linux-3.18 bisection] complete test-amd64-
> > > amd64-
> > > > > xl-shadow
> > > > >
> > > > > On Fri, Aug 24, 2018 at 10:30:26AM +0100, Paul Durrant wrote:
> > > > > > > > For bisection revision-tuple graph see:
> > > > > > > >    http://logs.test-
> lab.xenproject.org/osstest/results/bisect/linux-
> > > > > > > 3.18/test-amd64-amd64-xl-shadow.guest-start.html
> > > > > > > > Revision IDs in each graph node refer, respectively, to the Trees
> > > above.
> > > > > > >
> > > > > > > domainbuilder: detail: vcpu_x86_64: called
> > > > > > > domainbuilder: detail: vcpu_x86_64: cr3: pfn 0x2245 mfn 0x244845
> > > > > > > xenforeignmemory: error: ioctl failed: Invalid argument
> > > > > > > xc: error: panic: xc_dom_boot.c:420: xc_dom_gnttab_seed: failed
> to
> > > > > acquire
> > > > > > > d1 grant table [errno=22]
> > > > > > > : Internal error
> > > > > > > libxl: error: libxl_dom.c:750:libxl__build_dom:
> xc_dom_gnttab_init
> > > failed:
> > > > > > > Invalid argument
> > > > > > > domainbuilder: detail: xc_dom_release: called
> > > > > > >
> > > > > >
> > > > > > Taking a look now... Just forcing hap off doesn't generate an
> immediate
> > > > > repro so I'll have to have a closer look at the environment.
> > > > >
> > > > > Note the Linux branch is 3.18. I'm not sure if that really matters.
> > > > >
> > > >
> > > > I think that's the guest version, which should be irrelevant. Trying to
> figure
> > > out from the logs what dom0 is.
> > >
> > > No. That's the host kernel.
> > >
> >
> > Ok. Got a repro with my base debian 4.9 dom0 kernel:
> >
> > xenforeignmemory: error: ioctl failed: Invalid argument
> > xc: error: panic: xc_dom_boot.c:420: xc_dom_gnttab_seed: failed to
> acquire d1 grant table [errno=22]
> > : Internal error
> > libxl: error: libxl_dom.c:750:libxl__build_dom: xc_dom_gnttab_init failed:
> Invalid argument
> > domainbuilder: detail: xc_dom_release: called
> > libxl: error: libxl_create.c:1266:domcreate_rebuild_done: Domain 1:cannot
> (re-)build domain: -3
> > libxl: error: libxl_domain.c:1034:libxl__destroy_domid: Domain 1:Non-
> existant domain
> > libxl: error: libxl_domain.c:993:domain_destroy_callback: Domain 1:Unable
> to destroy guest
> > libxl: error: libxl_domain.c:920:domain_destroy_cb: Domain 1:Destruction
> of domain failed
> >
> > I'm guessing it is a straight bug in the fall-back that's supposed to happen if
> privcmd doesn't do resource mapping.
> 
> There are a lot of failed tests for the same step  on 4.9 branch as
> well. I guess that is caused by the same issue.

It's looking like privcmd is failing the ioctl with EINVAL rather than ENOTTY or EOPNOTSUPP for some reason. I'll need to look at the older privcmd source.

  Paul

> Wei.

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

  reply	other threads:[~2018-08-24  9:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  0:58 [linux-3.18 bisection] complete test-amd64-amd64-xl-shadow osstest service owner
2018-08-24  9:13 ` Wei Liu
2018-08-24  9:30   ` Paul Durrant
2018-08-24  9:34     ` Wei Liu
2018-08-24  9:35       ` Paul Durrant
2018-08-24  9:37         ` Wei Liu
2018-08-24  9:44           ` Paul Durrant
2018-08-24  9:50             ` Wei Liu
2018-08-24  9:51               ` Paul Durrant [this message]
2018-08-24 10:02                 ` Paul Durrant
  -- strict thread matches above, loose matches on Subject: below --
2019-02-11 13:37 osstest service owner

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=170c45fbb00646ea89a5b82eff5ae821@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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).