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

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

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.

Do you know what could cause xen to fail to boot?
I don't believe a few more patch on top of qemu-xen would.

Thanks,

-- 
Anthony PERARD

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