On 10.10.2022 04:26, osstest service owner wrote: > flight 173480 linux-linus real [real] > http://logs.test-lab.xenproject.org/osstest/logs/173480/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-arm64-arm64-xl-seattle 8 xen-boot fail REGR. vs. > 173462 > test-arm64-arm64-xl-credit2 8 xen-boot fail REGR. vs. > 173462 > test-arm64-arm64-libvirt-xsm 8 xen-boot fail REGR. vs. > 173462 > test-arm64-arm64-xl-credit1 8 xen-boot fail REGR. vs. > 173462 > test-arm64-arm64-xl-vhd 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-xl-vhd 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-xl-credit2 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-xl-multivcpu 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-examine 8 reboot fail REGR. vs. > 173462 > test-armhf-armhf-libvirt-raw 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-xl 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-libvirt 8 xen-boot fail REGR. vs. > 173462 > test-armhf-armhf-xl-arndale 8 xen-boot fail REGR. vs. > 173462
Hmm, they can't find their volume groups. Since xen-unstable flights have been working afaics, is there perhaps a kernel Kconfig change needed (e.g. because of a newly present or split option)? Albeit then it's not really clear to me why only Arm would be affected - I assume basic arrangements like these match between x86 and Arm. Jan
