I/O test 181 is flaky under AWS runners due to non-responsive QEMU in post-copy migration
## Host environment
- Operating system: Unknown
- OS/kernel version: Unknown
- Architecture: x86_64
- QEMU flavor: qemu-system-x86_64
- QEMU version: e89049b3ba5f1f0468bc0d294173345597514a1b
- QEMU command line:
```
check -qed 181
```
## Description of problem
I/O test 181 saw a failure under QEMU's private AWS CI runners with the QED format, that was not see when using gitlab shared runners or QCow2 on the private AWS runners
```
58/100 block-qed-optional+block-thorough - qemu:io-qed-181 ERROR 5.29s exit status 1
>>> LD_LIBRARY_PATH=/builds/qemu-project/qemu/build/subprojects/libvfio-user/lib ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 RUST_BACKTRACE=1 PYTHON=/builds/qemu-project/qemu/build/pyvenv/bin/python3 MALLOC_PERTURB_=227 MESON_TEST_ITERATION=1 /builds/qemu-project/qemu/build/pyvenv/bin/python3 /builds/qemu-project/qemu/build/../tests/qemu-iotests/check -tap -qed 181 --source-dir /builds/qemu-project/qemu/tests/qemu-iotests --build-dir /builds/qemu-project/qemu/build/tests/qemu-iotests
――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
stderr:
--- /builds/qemu-project/qemu/tests/qemu-iotests/181.out
+++ /builds/qemu-project/qemu/build/scratch/qed-file-181/181.out.bad
@@ -17,21 +17,4 @@
=== Do postcopy migration to destination ===
-
-=== Do some I/O on the destination ===
-
-(qemu) qemu-io disk "read -P 0x55 0 64k"
-read 65536/65536 bytes at offset 0
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-(qemu)
-(qemu) qemu-io disk "write -P 0x66 1M 64k"
-wrote 65536/65536 bytes at offset 1048576
-64 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-
-=== Shut down and check image ===
-
-(qemu) quit
-(qemu)
-(qemu) quit
-No errors were found on the image.
-*** done
+Timeout waiting for (qemu) on handle 1
(test program exited with status code 1)
```
## Steps to reproduce
1.
2.
3.
## Additional information
<!--
Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
If using libvirt, libvirt logs and XML domain information may be relevant.
-->
<!--
The line below ensures that proper tags are added to the issue.
Please do not remove it.
-->
issue