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 -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
