On 01.10.2020 07:11, osstest service owner wrote: > flight 155187 xen-unstable-smoke real [real] > http://logs.test-lab.xenproject.org/osstest/logs/155187/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. > 155128
All I can see in the serial log is Oct 1 03:49:33.145346 [ 16.993554] virbr0: port 1(virbr0-nic) entered disabled state Oct 1 03:49:33.145426 [ 16.993584] device virbr0-nic entered promiscuous mode Oct 1 03:49:33.157353 [ 16.993662] systemd-udevd[1538]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Oct 1 03:49:33.169370 [ 16.993840] systemd-udevd[1541]: Using default interface naming scheme 'v240'. Oct 1 03:49:33.169467 [ 16.998341] systemd-udevd[1538]: Process 'ifupdown-hotplug' failed with exit code 1. Oct 1 03:49:33.181371 [ 16.999735] systemd-udevd[1541]: Process 'ifupdown-hotplug' failed with exit code 1. Oct 1 03:49:33.193293 [ 17.287282] device virbr0-nic left promiscuous mode Oct 1 03:49:33.433389 [ 17.287356] virbr0: port 1(virbr0-nic) entered disabled state Oct 1 03:49:33.433466 [ 17.289383] systemd-udevd[1541]: Process 'ifupdown-hotplug' failed with exit code 1. Oct 1 03:49:33.445371 [ 17.294929] systemd-udevd[1541]: Process 'ifupdown-hotplug' failed with exit code 1. accompanied by multiple instances of # Warning: iptables-legacy tables present, use iptables-legacy to see them iptables: Operation not supported. and # Warning: iptables-legacy tables present, use iptables-legacy to see them iptables: Invalid argument. Run `dmesg' for more information. in libvirtd.log. What I can't tell is whether this is the cause of the test failure. In any event the domain was (still?) paused at the time the debug keys got sent. What I also can't guess at all is which of the five commits in question might be responsible here (or whether the issue is an environment one). Jan
