Victor Toso b124ebe53e migrate.py: fix events race ... Currently, when we run migrate.py with --client option we get stuck waiting for SPICE_CONNECTED event on target qmp (while receiving only QMP). Problem is, only after event SPICE_INITIALIZED in the source qmp is that the client will be able to do migration (to properly exchange spice messages). So, it is a must that if we have a test where a client is connected, to wait for SPICE_INITIALIZED event in the source qmp. To clarify, this patches fixes the following test: ./migrate.py --client spicy Signed-off-by: Victor Toso <victortoso@redhat.com> Acked-by: Kevin Pouget <kpouget@redhat.com>		2020-03-04 16:09:27 +00:00
..
migrate.py	migrate.py: fix events race	2020-03-04 16:09:27 +00:00