xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Ian Jackson" <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [qemu-upstream-unstable test] 114273: regressions - FAIL
Date: Wed, 11 Oct 2017 12:34:23 +0100	[thread overview]
Message-ID: <20171011113423.GA31880@perard.uk.xensource.com> (raw)
In-Reply-To: <osstest-114273-mainreport@xen.org>

On Wed, Oct 11, 2017 at 04:33:26AM +0000, osstest service owner wrote:
> flight 114273 qemu-upstream-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/114273/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl-pvh-intel 12 guest-start             fail REGR. vs. 114029
>  test-amd64-amd64-xl-pvh-amd  12 guest-start              fail REGR. vs. 114029

Hi,

Is this an expected failure due to recent change about pvh (in libxl)?

In the logs, `xl create` fails with this:
xc: error: panic: xc_dom_x86.c:1587: bootlate_pv: pin_table failed (pfn 0x2374, rc=1): Internal error
libxl: error: libxl_dom.c:745:libxl__build_dom: xc_dom_boot_image failed: Invalid argument
domainbuilder: detail: xc_dom_release: called


Can we force push? as this error does not seems to be related to QEMU.

Thanks,

-- 
Anthony PERARD

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

  reply	other threads:[~2017-10-11 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  4:33 [qemu-upstream-unstable test] 114273: regressions - FAIL osstest service owner
2017-10-11 11:34 ` Anthony PERARD [this message]
2017-10-11 11:38   ` Roger Pau Monné

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=20171011113423.GA31880@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xensource.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 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).