From: Ian Jackson <ian.jackson@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [xen-4.11-testing test] 136385: regressions - FAIL
Date: Mon, 20 May 2019 11:30:08 +0100 [thread overview]
Message-ID: <23778.33200.47146.497482@mariner.uk.xensource.com> (raw)
In-Reply-To: <osstest-136385-mainreport@xen.org>
osstest service owner writes ("[xen-4.11-testing test] 136385: regressions - FAIL"):
> flight 136385 xen-4.11-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/136385/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-debianhvm-amd64 10 debian-hvm-install fail REGR. vs. 135683
> test-amd64-amd64-xl-qemut-debianhvm-i386-xsm 10 debian-hvm-install fail REGR. vs. 135683
These are a known bug. The Debian "stretch" ("stable") i386 kernel
simply does not work under Xen HVM. I don't thnk this is anything to
do with the 4.11 Xen commits under test here. It is appearing here in
this flight because I reorganised the amd64/i386 test jobs.
> test-armhf-armhf-xl-credit2 16 guest-start/debian.repeat fail REGR. vs. 135683
I looked at this. I thought it might be the known xenstore memory
handling bug but it doesn't seem to be. I looked at the logs and the
guest seems simply not to have started at all. There is nothing from
it in its pv console. Adding some ARM folks. I have a memory of some
allegation that there is a fundamental cache mismanagement problem
which might cause this, in which case we probably ought to force push.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Ian Jackson <ian.jackson@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Julien Grall <julien.grall@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [xen-4.11-testing test] 136385: regressions - FAIL
Date: Mon, 20 May 2019 11:30:08 +0100 [thread overview]
Message-ID: <23778.33200.47146.497482@mariner.uk.xensource.com> (raw)
Message-ID: <20190520103008.T9w1vAEV3W9NnGLl0xRC6PfzW3j3MvW-JnyQYdhQ0TM@z> (raw)
In-Reply-To: <osstest-136385-mainreport@xen.org>
osstest service owner writes ("[xen-4.11-testing test] 136385: regressions - FAIL"):
> flight 136385 xen-4.11-testing real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/136385/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemut-debianhvm-amd64 10 debian-hvm-install fail REGR. vs. 135683
> test-amd64-amd64-xl-qemut-debianhvm-i386-xsm 10 debian-hvm-install fail REGR. vs. 135683
These are a known bug. The Debian "stretch" ("stable") i386 kernel
simply does not work under Xen HVM. I don't thnk this is anything to
do with the 4.11 Xen commits under test here. It is appearing here in
this flight because I reorganised the amd64/i386 test jobs.
> test-armhf-armhf-xl-credit2 16 guest-start/debian.repeat fail REGR. vs. 135683
I looked at this. I thought it might be the known xenstore memory
handling bug but it doesn't seem to be. I looked at the logs and the
guest seems simply not to have started at all. There is nothing from
it in its pv console. Adding some ARM folks. I have a memory of some
allegation that there is a fundamental cache mismanagement problem
which might cause this, in which case we probably ought to force push.
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-05-20 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 21:09 [xen-4.11-testing test] 136385: regressions - FAIL osstest service owner
2019-05-18 21:09 ` [Xen-devel] " osstest service owner
2019-05-20 10:30 ` Ian Jackson [this message]
2019-05-20 10:30 ` Ian Jackson
2019-05-20 11:27 ` Jan Beulich
2019-05-20 11:27 ` [Xen-devel] " Jan Beulich
2019-05-20 12:51 ` Ian Jackson
2019-05-20 12:51 ` [Xen-devel] " Ian Jackson
2019-05-20 13:10 ` Ian Jackson
2019-05-20 13:10 ` [Xen-devel] " Ian Jackson
2019-05-20 14:35 ` Julien Grall
2019-05-20 14:35 ` [Xen-devel] " Julien Grall
2019-05-20 16:04 ` Ian Jackson
2019-05-20 16:04 ` [Xen-devel] " Ian Jackson
2019-05-21 16:55 ` Julien Grall
2019-05-21 16:55 ` [Xen-devel] " Julien Grall
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=23778.33200.47146.497482@mariner.uk.xensource.com \
--to=ian.jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.