Hi all,
I'm running a slitely modified migration over tcp test in virt-test,
which does a migration from one smp=2 VM to another on the same host
over TCP,
and exposes some dummy CPU load inside the GUEST while migration, and
after a series of runs I'm alwais getting a CLOCK_WATCHDOG_TIMEOUT
Hi Andrey, thank you for your answer.
I know I can work around this by specifying a numa node.
My question is though is the current behaviour considered to be a bug, or
not. And if yes, when it is expected to get fixed.
Thanks,
Mikhail
On Fri, Oct 17, 2014 at 5:54 PM, Andrey Korolyov
