From: Eduardo Habkost <ehabkost@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, crosa@redhat.com,
eblake@redhat.com, armbru@redhat.com, mreitz@redhat.com,
kwolf@redhat.com, famz@redhat.com, jsnow@redhat.com,
den@openvz.org, stefanha@redhat.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/3] scripts: add render_block_graph function for QEMUMachine
Date: Fri, 17 Aug 2018 16:09:20 -0300 [thread overview]
Message-ID: <20180817190920.GL15372@localhost.localdomain> (raw)
In-Reply-To: <20662248-c334-6479-36a8-937f622151ab@virtuozzo.com>
On Fri, Aug 17, 2018 at 09:59:41PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 17.08.2018 21:25, Eduardo Habkost wrote:
> > On Fri, Aug 17, 2018 at 09:04:39PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> > > Render block nodes graph with help of graphviz. This new function is
> > > for debugging, so there is no sense to put it into qemu.py as a method
> > > of QEMUMachine. Let's instead put it separately.
> > >
> > > Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> > > ---
> > > scripts/render_block_graph.py | 78 +++++++++++++++++++++++++++++++++++++++++++
> > > 1 file changed, 78 insertions(+)
> > > create mode 100644 scripts/render_block_graph.py
> > >
> > > diff --git a/scripts/render_block_graph.py b/scripts/render_block_graph.py
> > > new file mode 100644
> > > index 0000000000..7048a0bac8
> > > --- /dev/null
> > > +++ b/scripts/render_block_graph.py
> > > @@ -0,0 +1,78 @@
> > > +# Render Qemu Block Graph
> > [...]
> >
> > What about making the script work from the command-line?
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > ---
> > diff --git a/scripts/render_block_graph.py b/scripts/render_block_graph.py
> > old mode 100644
> > new mode 100755
> > index 7048a0bac8..e29fe0fc41
> > --- a/scripts/render_block_graph.py
> > +++ b/scripts/render_block_graph.py
> > @@ -1,3 +1,4 @@
> > +#!/usr/bin/env python
> > # Render Qemu Block Graph
> > #
> > # Copyright (c) 2017 Parallels International GmbH
> > @@ -16,8 +17,9 @@
> > # along with this program. If not, see <http://www.gnu.org/licenses/>.
> > #
> > -import os
> > +import os, sys
> > from graphviz import Digraph
> > +from qmp.qmp import QEMUMonitorProtocol
> > def perm(arr):
> > s = 'w' if 'write' in arr else '_'
> > @@ -27,16 +29,16 @@ def perm(arr):
> > s += 's' if 'resize' in arr else '_'
> > return s
> > -def render_block_graph(vm, filename, pointers=False, format='png'):
> > +def render_block_graph(qmp, filename, pointers=False, format='png'):
> > '''
> > Render graph in text (dot) representation into "@filename" and
> > representation in @format into "@filename.@format"
> > '''
> > - nodes = vm.command('query-named-block-nodes')
> > + nodes = qmp.command('query-named-block-nodes')
> > nodes_info = {n['node-name']: n for n in nodes}
> > - block_graph = vm.command('x-query-block-graph')
> > + block_graph = qmp.command('x-query-block-graph')
> > graph = Digraph(comment='Block Nodes Graph')
> > graph.format = format
> > @@ -76,3 +78,9 @@ def render_block_graph(vm, filename, pointers=False, format='png'):
> > graph.edge(str(e['parent']), str(e['child']), label=label)
> > graph.render(filename)
> > +
> > +if __name__ == '__main__':
> > + #TODO: use argparse for command-line arguments
> > + qmp = QEMUMonitorProtocol(sys.argv[1])
> > + qmp.connect()
> > + render_block_graph(qmp, sys.argv[2])
> >
> >
>
> Cool, thanks.
>
> so, how to use it then?
>
> for python iotest a proper parameter would be vm._qmp, yes?
Yes, assuming you just want to do it locally just for debugging.
One thing we could do later: refactor QEMUMachine and
QEMUMonitorProtocol so their method names are the same and both
'vm' and 'vm._qmp' work here.
>
> is there a way to dump running libvirt vm graph?
>
> I've started libvirt guest, qemu process has cmdline parameters
> -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-tmp/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control
>
> command
> virsh qemu-monitor-command tmp '{"execute": "x-query-block-graph"}'
> works fine,
>
> but script hangs on connection:
> # python ./scripts/render_block_graph.py
> /var/lib/libvirt/qemu/domain-3-tmp/monitor.sock
> ^CTraceback (most recent call last):
> File "./scripts/render_block_graph.py", line 85, in <module>
> qmp.connect()
> File "/work/src/qemu/up-new-fleecing/scripts/qmp/qmp.py", line 140, in
> connect
> self.__sock.connect(self.__address)
> File "/usr/lib64/python2.7/socket.py", line 224, in meth
> return getattr(self._sock,name)(*args)
> KeyboardInterrupt
>
> ./scripts/qmp/qmp-shell /var/lib/libvirt/qemu/domain-3-tmp/monitor.sock
> outputs nothing...
I don't know why it doesn't work with a running instance started
by libvirt, but it works if I run QEMU manually using "-qmp
unix:/tmp/qmp,server".
--
Eduardo
next prev parent reply other threads:[~2018-08-17 19:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 18:00 [Qemu-devel] [PATCH v2 0/3] block nodes graph visualization Vladimir Sementsov-Ogievskiy
2018-08-17 18:04 ` [Qemu-devel] [PATCH v2 1/3] qapi: add x-query-block-graph Vladimir Sementsov-Ogievskiy
2018-08-17 18:04 ` [Qemu-devel] [PATCH v2 2/3] scripts: add render_block_graph function for QEMUMachine Vladimir Sementsov-Ogievskiy
2018-08-17 18:25 ` Eduardo Habkost
2018-08-17 18:59 ` Vladimir Sementsov-Ogievskiy
2018-08-17 19:09 ` Eduardo Habkost [this message]
2018-08-17 18:04 ` [Qemu-devel] [PATCH v2 3/3] not-for-commit: example of new command usage for debugging Vladimir Sementsov-Ogievskiy
2018-08-17 20:32 ` [Qemu-devel] [PATCH v2 1/3] qapi: add x-query-block-graph Eric Blake
2018-08-17 21:03 ` Max Reitz
2018-08-20 10:20 ` Vladimir Sementsov-Ogievskiy
2018-08-20 13:44 ` Max Reitz
2018-08-20 15:13 ` Vladimir Sementsov-Ogievskiy
2018-08-20 16:35 ` Max Reitz
2018-08-20 17:04 ` Vladimir Sementsov-Ogievskiy
2018-08-20 17:13 ` Max Reitz
2018-08-20 17:35 ` Vladimir Sementsov-Ogievskiy
2018-08-22 15:19 ` Vladimir Sementsov-Ogievskiy
2018-08-20 18:38 ` Vladimir Sementsov-Ogievskiy
2018-08-22 8:33 ` Max Reitz
2018-08-20 10:03 ` Vladimir Sementsov-Ogievskiy
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=20180817190920.GL15372@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).