From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Cc: Juergen Gross <juergen.gross@ts.fujitsu.com>
Subject: Re: [linux-linus test] 105655: regressions - FAIL
Date: Thu, 9 Feb 2017 08:20:14 -0500 [thread overview]
Message-ID: <fc3f1a41-a58d-36f5-3d57-8344696714fc@oracle.com> (raw)
In-Reply-To: <1486637085.3042.32.camel@citrix.com>
On 02/09/2017 05:44 AM, Dario Faggioli wrote:
> On Thu, 2017-02-09 at 10:00 +0000, osstest service owner wrote:
>> flight 105655 linux-linus real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/105655/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-amd64-amd64-xl-credit2 14 guest-saverestore fail REGR.
>> vs. 59254
>> test-amd64-amd64-xl 17 guest-localmigrate/x10 fail REGR.
>> vs. 59254
>> test-amd64-amd64-xl-xsm 17 guest-localmigrate/x10 fail REGR.
>> vs. 59254
>> test-amd64-i386-xl 17 guest-localmigrate/x10 fail REGR.
>> vs. 59254
>> test-amd64-amd64-xl-multivcpu 14 guest-saverestore fail REGR.
>> vs. 59254
>>
> I gave a quick look at these ones above, and it looks to me that Linux
> is panicing either while freezing:
>
> http://logs.test-lab.xenproject.org/osstest/logs/105655/test-amd64-amd64-xl-credit2/rimava0---var-log-xen-console-guest-debian.guest.osstest.log
> http://logs.test-lab.xenproject.org/osstest/logs/105655/test-amd64-amd64-xl-multivcpu/elbling1---var-log-xen-console-guest-debian.guest.osstest.log
>
> Or when trying to come back:
>
> http://logs.test-lab.xenproject.org/osstest/logs/105655/test-amd64-amd64-xl/godello0---var-log-xen-console-guest-debian.guest.osstest--incoming.log
> http://logs.test-lab.xenproject.org/osstest/logs/105655/test-amd64-i386-xl/chardonnay0---var-log-xen-console-guest-debian.guest.osstest--incoming.log
>
> Regards,
> Dario
>
These are known regressions and are fixed by
https://lists.xenproject.org/archives/html/xen-devel/2017-01/msg03269.html
and, to some extent, by
https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg00625.html
Neither have been committed yet (which reminds me that I should probably
ping David Miller)
What I can't figure out is this failure:
http://logs.test-lab.xenproject.org/osstest/logs/105353/test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm/13.ts-guest-localmigrate.log
i.e.
xc: info: Restoring domain
xc: detail: Failed allocation for dom 4: 1024 extents of order 0
xc: error: Failed to populate physmap (16 = Device or resource busy):
Internal error
xc: error: Failed to populate pfns for batch of 1024 pages: Internal error
xc: error: Restore failed (16 = Device or resource busy): Internal error
libxl-save-helper: debug: complete r=-1: Device or resource busy
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-02-09 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 10:00 [linux-linus test] 105655: regressions - FAIL osstest service owner
2017-02-09 10:44 ` Dario Faggioli
2017-02-09 13:20 ` Boris Ostrovsky [this message]
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=fc3f1a41-a58d-36f5-3d57-8344696714fc@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=juergen.gross@ts.fujitsu.com \
--cc=osstest-admin@xenproject.org \
--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).