diff options
| author | Daniel P. Berrangé | 2022-01-28 17:11:56 +0100 |
|---|---|---|
| committer | John Snow | 2022-02-23 23:07:26 +0100 |
| commit | 439125293cc9cfb684eb4db23db04199f5f435a2 (patch) | |
| tree | 28d4356bed0cf6a1f3fa700ce273a8964d4b0023 /python/qemu/utils/qemu_ga_client.py | |
| parent | Merge remote-tracking branch 'remotes/lvivier-gitlab/tags/trivial-branch-for-... (diff) | |
| download | qemu-439125293cc9cfb684eb4db23db04199f5f435a2.tar.gz qemu-439125293cc9cfb684eb4db23db04199f5f435a2.tar.xz qemu-439125293cc9cfb684eb4db23db04199f5f435a2.zip | |
python: introduce qmp-shell-wrap convenience tool
With the current 'qmp-shell' tool developers must first spawn QEMU with
a suitable -qmp arg and then spawn qmp-shell in a separate terminal
pointing to the right socket.
With 'qmp-shell-wrap' developers can ignore QMP sockets entirely and
just pass the QEMU command and arguments they want. The program will
listen on a UNIX socket and tell QEMU to connect QMP to that.
For example, this:
# qmp-shell-wrap -- qemu-system-x86_64 -display none
Is roughly equivalent of running:
# qemu-system-x86_64 -display none -qmp qmp-shell-1234 &
# qmp-shell qmp-shell-1234
Except that 'qmp-shell-wrap' switches the socket peers around so that
it is the UNIX socket server and QEMU is the socket client. This makes
QEMU reliably go away when qmp-shell-wrap exits, closing the server
socket.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-id: 20220128161157.36261-2-berrange@redhat.com
[Edited for rebase. --js]
Signed-off-by: John Snow <jsnow@redhat.com>
Diffstat (limited to 'python/qemu/utils/qemu_ga_client.py')
0 files changed, 0 insertions, 0 deletions