On 2/22/22 10:21, Daniel P. Berrangé wrote:
On Tue, Feb 22, 2022 at 08:57:03AM +0100, Damien Hedde wrote:
On 2/22/22 07:10, Markus Armbruster wrote:
Damien Hedde <damien.he...@greensocs.com> writes:
Hi,
The main idea of this series is to be a bit more user-friendly when
using qmp-shell in a non-interactive way: with an input redirection
from a file containing a list of commands.
I'm working on dynamic qapi config of a qemu machine, this would
be very useful to provide and reproduce small examples.
Why not use plain QMP for that?
[...]
What do you mean by plain QMP ?
Directly connect to the socket and send the QMP JSON commands you have.
Essentially qmp-shell is designed for adhoc interactive human usage.
For automated / scripted, non-interactive usage, it is expected that
QMP is simple enough that tools just directly connect to the QMP
socket instead of using a wrapper layer.
What is the reason you want to use qmp-shell for this instead of
directly using the socket from your scripts ?
Regards,
Daniel
We have such scripts that interface with QMP directly for our own use.
Here I just wanted to propose a simple way to just send a
bunch of commands from a source file and stop if something unexpected
happens.
Only goal is to be able to share a file on the ml and allow people to
reproduce easily.
We can already redirect the input, but it is almost impossible to see
if something failed.
--
Damien
