On Tue, Oct 27, 2020 at 5:23 PM osstest service owner
<[email protected]> wrote:
>
> flight 156257 qemu-mainline real [real]
> flight 156266 qemu-mainline real-retest [real]
> http://logs.test-lab.xenproject.org/osstest/logs/156257/
> http://logs.test-lab.xenproject.org/osstest/logs/156266/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-arm64-arm64-libvirt-xsm 14 guest-start fail REGR. vs.
> 152631
QEMU doesn't start with "qemu-system-i386: -xen-domid 1: Option not
supported for this target"
This happens if CONFIG_XEN isn't set.
QEMU is built with:
host CPU: aarch64
host endianness: little
target list: i386-softmmu
commit 8a19980e3fc4 "configure: move accelerator logic to meson"
introduced this logic:
+accelerator_targets = { 'CONFIG_KVM': kvm_targets }
+if cpu in ['x86', 'x86_64']
+ accelerator_targets += {
+ 'CONFIG_HAX': ['i386-softmmu', 'x86_64-softmmu'],
+ 'CONFIG_XEN': ['i386-softmmu', 'x86_64-softmmu'],
+ 'CONFIG_HVF': ['x86_64-softmmu'],
+ 'CONFIG_WHPX': ['i386-softmmu', 'x86_64-softmmu'],
+ }
+endif
I guess something like this would fix it:
if cpu in ['aarch64', 'arm']
accelerator_targets += { 'CONFIG_XEN': ['i386-softmmu'], }
endif
I don't have an arm setup to test this.
> test-armhf-armhf-xl-vhd 12 debian-di-install fail REGR. vs.
> 152631
> test-armhf-armhf-libvirt 14 guest-start fail REGR. vs.
> 152631
> test-amd64-amd64-libvirt-vhd 19 guest-start/debian.repeat fail REGR. vs.
> 152631
2020-10-27 14:08:29 Z lvdisplay output says device is still open:
/dev/fiano1-vg/test-amd64-amd64-xl-qcow2_debian.buster.guest.osstest-disk:fiano1-vg:3:1:-1:1:20504576:2503:-1:0:-1:253:2
It's unclear to me why the disk is still in use. Looks like QEMU exited.
-Jason
