All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Saul Wold" <Saul.Wold@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: [WIP v2 0/1] Add Qemu Monitor Support
Date: Tue, 10 Nov 2020 20:10:00 -0800	[thread overview]
Message-ID: <20201111041003.864509-1-saul.wold@windriver.com> (raw)

Version 2!

I figured out that I was saving the monitor_dumper in the wrong
class, so moved where it's saved into the OESSHTarget code, it still
needs to be created in the OEQemuTarget since that's where the runner
is available.

Currently we interact with the JSON (which is new to me) interface of
qmp and right now the write/read is just raw with no JSON dump, that
might be why I am seeing the erros after the first one.  I did try an
empty run_monitor("") between commands, but that did not help. The 
run_monitor() may need to be reworked to deal with JSON.

Also, I still have the static port of 4444 for the telnet/cli version 
of the monitor and the possible race for the generated port as I have 
not found a solution for that yet.

Sau!

The output goes into files as follows:
::::::::::::::
tmp/log/runtime-hostdump/202011101608_qmp/unknown_00_qemu_monitor
:::::::::::::: 
'{"execute":"status"}\n'
{"timestamp": {"seconds": 1605053296, "microseconds": 645339}, "event": "NIC_RX_FILTER
_CHANGED", "data": {"path": "/machine/peripheral-anon/device[0]/virtio-backend"}}
::::::::::::::
tmp/log/runtime-hostdump/202011101608_qmp/unknown_01_qemu_monitor
::::::::::::::
'{"execute":"query-status"}\n'
{"error": {"class": "GenericError", "desc": "QMP input must be a JSON object"}}
::::::::::::::
tmp/log/runtime-hostdump/202011101608_qmp/unknown_02_qemu_monitor
::::::::::::::
'{"execute":"query-block"}\n'
{"error": {"class": "GenericError", "desc": "QMP input must be a JSON object"}}


Saul Wold (1):
  qemurunner: add support for qmp cmds

 meta/classes/testimage.bbclass    |  7 ++++
 meta/lib/oeqa/core/target/qemu.py |  6 +++
 meta/lib/oeqa/core/target/ssh.py  | 22 ++++++++--
 meta/lib/oeqa/targetcontrol.py    |  5 +++
 meta/lib/oeqa/utils/dump.py       | 20 +++++++++
 meta/lib/oeqa/utils/qemurunner.py | 70 ++++++++++++++++++++++++++++++-
 6 files changed, 126 insertions(+), 4 deletions(-)

-- 
2.25.1


             reply	other threads:[~2020-11-11  4:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11  4:10 Saul Wold [this message]
2020-11-11  4:10 ` [WIP v2 1/1] qemurunner: add support for qmp cmds Saul Wold
2020-11-11 14:35   ` [OE-core] " Joshua Watt
2020-11-11 14:54   ` Joshua Watt
2020-11-11  4:10 ` [PATCH] [WIP] qemurunner.py: qemu as client Saul Wold
2020-11-11  4:10 ` [PATCH] qemurunner: add support for qmp cmds Saul Wold
     [not found] ` <164658B07603FC62.32470@lists.openembedded.org>
2020-11-11  4:19   ` [OE-core] [PATCH] [WIP] qemurunner.py: qemu as client Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201111041003.864509-1-saul.wold@windriver.com \
    --to=saul.wold@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.