Re: [Xen-devel] [qemu-upstream-4.11-testing test] 136184: regressions - FAIL

[Julien Grall <julien.grall@xxxxxxx>]

Hi Anthony,

Thank you for CCing me.

On 5/16/19 11:37 AM, Anthony PERARD wrote:
> On Wed, May 15, 2019 at 07:48:17PM +0000, osstest service owner wrote:
> > flight 136184 qemu-upstream-4.11-testing real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/136184/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking,
> > including tests which could not be run:
> >   build-arm64-pvops               <job status>                 broken  in 134594
> >   build-arm64                     <job status>                 broken  in 134594
> >   build-arm64-xsm                 <job status>                 broken  in 134594
> >   build-arm64-xsm            4 host-install(4) broken in 134594 REGR. vs. 125575
> >   build-arm64-pvops          4 host-install(4) broken in 134594 REGR. vs. 125575
> >   build-arm64                4 host-install(4) broken in 134594 REGR. vs. 125575
> >   test-arm64-arm64-libvirt-xsm  7 xen-boot                 fail REGR. vs. 125575
> >   test-arm64-arm64-xl           7 xen-boot                 fail REGR. vs. 125575
> >   test-arm64-arm64-xl-xsm       7 xen-boot                 fail REGR. vs. 125575
> >   test-arm64-arm64-xl-credit2   7 xen-boot                 fail REGR. vs. 125575
> Ian, Julien,
>
> I can't figure out why Xen consistently fails to boot on rochester* in
> the qemu-upstream-4.11-testing flights. The xen-4.11-testing seems to
> pass.
>
> At boot, the boot loader seems to load blobs, but when it's time to Xen
> to shine, there are no output from Xen on the serial.
The serial console is initializing fairly late in the process. Any 
useful message (such as memory setup or even part of the interrupts) 
will be hide out. For getting them, you need earlyprintk. Unfortunately 
they can't be configured at runtime today :(.
> Do you know what could cause xen to fail to boot?
It is hard to say without the log. Looking at the different with a Xen 
4.11 flights on rochester0 [1], it seems the .config is slightly 
different. 4.11 flight has CONFIG_LIVEPATCH set.
I tried to boot xen built in this flight on an internal board, but I 
can't see any error. So it may be some board specific issues.
Sorry I can't provide more input without a proper investigation.

> I don't believe a few more patch on top of qemu-xen would.
Cheers,

[1] 
http://logs.test-lab.xenproject.org/osstest/logs/136231/test-arm64-arm64-xl/info.html
>
--
Julien Grall

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