From: Ian Jackson <ian.jackson@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [xen-4.7-testing test] 137065: regressions - FAIL
Date: Wed, 5 Jun 2019 19:02:57 +0100 [thread overview]
Message-ID: <23800.977.195291.114635@mariner.uk.xensource.com> (raw)
In-Reply-To: <5CF10F1C0200007800233FA8@prv1-mh.provo.novell.com>
Jan Beulich writes ("Re: [Xen-devel] [xen-4.7-testing test] 137065: regressions - FAIL"):
> The one you've picked looks to be a "fail never pass" one, so is perhaps
> not ideal. I've looked at a couple other ones, and in particular when the
> guests are supposedly 64-bit I notice two things
> - they look to be busy looping on vCPU 0,
> - the VMCS/VMCB dumps suggest they've never left early boot (i.e.
> are still in 32-bit mode with paging still disabled), and may well still
> be sitting inside the boot loader.
> I'm not at all certain though if this helps in any way.
I have not yet managed to make much progress with this. In my most
recent attempt I backported all of the build fixes onto the
last-working Xen revision.
The branch I built and tested was this:
iwj@osstest.test-lab:xen.git/t.47
And it failed:
flight 137255 xen-unstable play [play]
http://logs.test-lab.xenproject.org/osstest/logs/137255/
I think the most likely culprit is the OVMF/seabios changes.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-06-05 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 1:28 [xen-4.7-testing test] 137065: regressions - FAIL osstest service owner
2019-05-31 1:28 ` [Xen-devel] " osstest service owner
2019-05-31 10:55 ` Ian Jackson
2019-05-31 10:55 ` [Xen-devel] " Ian Jackson
2019-05-31 11:25 ` Jan Beulich
2019-05-31 11:25 ` [Xen-devel] " Jan Beulich
2019-06-05 18:02 ` Ian Jackson [this message]
2019-06-06 7:15 ` Jan Beulich
2019-06-17 7:04 ` Jan Beulich
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=23800.977.195291.114635@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=JBeulich@suse.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).