From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Oksana Vohchana <ovoshcha@redhat.com>, qemu-devel@nongnu.org
Cc: ehabkost@redhat.com, crosa@redhat.com
Subject: Re: [PATCH v4] python/qemu/qmp.py: QMP debug with VM label
Date: Tue, 17 Mar 2020 17:15:01 -0300 [thread overview]
Message-ID: <289c4cea-6df3-0b79-b0b9-e40a25c12ee9@redhat.com> (raw)
In-Reply-To: <20200316103203.10046-1-ovoshcha@redhat.com>
On 3/16/20 7:32 AM, Oksana Vohchana wrote:
> QEMUMachine writes some messages to the default logger.
> But it sometimes hard to read the output if we have requests to
> more than one VM.
For example, tests/acceptance/migration.py uses two VMs and reading the
qmp outputs on avocado's log is very confusing. Certainly this change
will help to improve that situation, just need to adapt
tests/acceptance/avocado_qemu/__init__.py to create the QEMUMachine
object with a name.
Anyway, this patch looks good to me so:
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Thanks!
> This patch adds a label to the logger in the debug mode.
>
> Signed-off-by: Oksana Vohchana <ovoshcha@redhat.com>
> ---
> v2:
> - Instead of shown the label in the message it provides the label
> only in the debug logger information.
> v3:
> - Fixes coding style problems.
> v4:
> - Use a suffix method to get a children's logger process from the parent.
> ---
> python/qemu/machine.py | 3 ++-
> python/qemu/qmp.py | 5 ++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/python/qemu/machine.py b/python/qemu/machine.py
> index 183d8f3d38..f53abfa492 100644
> --- a/python/qemu/machine.py
> +++ b/python/qemu/machine.py
> @@ -270,7 +270,8 @@ class QEMUMachine(object):
> self._vm_monitor = os.path.join(self._sock_dir,
> self._name + "-monitor.sock")
> self._remove_files.append(self._vm_monitor)
> - self._qmp = qmp.QEMUMonitorProtocol(self._vm_monitor, server=True)
> + self._qmp = qmp.QEMUMonitorProtocol(self._vm_monitor, server=True,
> + nickname=self._name)
>
> def _post_launch(self):
> if self._qmp:
> diff --git a/python/qemu/qmp.py b/python/qemu/qmp.py
> index f40586eedd..d6c9b2f4b1 100644
> --- a/python/qemu/qmp.py
> +++ b/python/qemu/qmp.py
> @@ -46,7 +46,7 @@ class QEMUMonitorProtocol:
> #: Logger object for debugging messages
> logger = logging.getLogger('QMP')
>
> - def __init__(self, address, server=False):
> + def __init__(self, address, server=False, nickname=None):
> """
> Create a QEMUMonitorProtocol class.
>
> @@ -62,6 +62,9 @@ class QEMUMonitorProtocol:
> self.__address = address
> self.__sock = self.__get_sock()
> self.__sockfile = None
> + self._nickname = nickname
> + if self._nickname:
> + self.logger = logging.getLogger('QMP').getChild(self._nickname)
> if server:
> self.__sock.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
> self.__sock.bind(self.__address)
next prev parent reply other threads:[~2020-03-17 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 10:32 [PATCH v4] python/qemu/qmp.py: QMP debug with VM label Oksana Vohchana
2020-03-16 17:11 ` John Snow
2020-03-17 20:15 ` Wainer dos Santos Moschetta [this message]
2020-03-17 21:55 ` Cleber Rosa
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=289c4cea-6df3-0b79-b0b9-e40a25c12ee9@redhat.com \
--to=wainersm@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=ovoshcha@redhat.com \
--cc=qemu-devel@nongnu.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 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).