b9420e4f4b
If we spy on the QMP commands instead, we don't need callers to remember to pass it. Seems like a fair trade-off. The one slightly weird bit is overloading this instance variable for wait(), where we use it to mean "don't issue the qmp 'quit' command". This means that wait() will "fail" if the QEMU process does not terminate of its own accord. In most cases, we probably did already actually issue quit -- some iotests do this -- but in some others, we may be waiting for QEMU to terminate for some other reason, such as a test wherein we tell the guest (directly) to shut down. Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Hanna Reitz <hreitz@redhat.com> Reviewed-by: Kevin Wolf <kwolf@redhat.com> Message-id: 20211026175612.4127598-2-jsnow@redhat.com Signed-off-by: John Snow <jsnow@redhat.com> |
||
|---|---|---|
| .. | ||
| README.rst | ||
| __init__.py | ||
| console_socket.py | ||
| machine.py | ||
| py.typed | ||
| qtest.py | ||
README.rst
qemu.machine package ==================== This package provides core utilities used for testing and debugging QEMU. It is used by the iotests, vm tests, acceptance tests, and several other utilities in the ./scripts directory. It is not a fully-fledged SDK and it is subject to change at any time. See the documentation in ``__init__.py`` for more information.