On Thu, 24 Mar 2022 at 11:53, Laurent Vivier wrote:
>
> On 24/03/2022 12:11, Peter Maydell wrote:
> > This is a backtrace from virtio-failover-test, which had hung
> > on the s390 gitlab CI runner. Both processes were using CPU,
> > so this is some kind of livelock, not a deadlock.
> >
> > Looking
On 24/03/2022 12:11, Peter Maydell wrote:
This is a backtrace from virtio-failover-test, which had hung
on the s390 gitlab CI runner. Both processes were using CPU,
so this is some kind of livelock, not a deadlock.
Looking more closely at the virtio-net-failover process, in the function
test_mig
This is a backtrace from virtio-failover-test, which had hung
on the s390 gitlab CI runner. Both processes were using CPU,
so this is some kind of livelock, not a deadlock.
Looking more closely at the virtio-net-failover process, in the function
test_migrate_off_abort() we have executed 'migrate_c
