From: Eduardo Habkost <ehabkost@redhat.com>
To: Amador Pahim <apahim@redhat.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, armbru@redhat.com,
crosa@redhat.com, muriloo@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v11 4/8] qemu.py: always cleanup on shutdown()
Date: Fri, 19 Jan 2018 15:33:15 -0200 [thread overview]
Message-ID: <20180119173315.GE15832@localhost.localdomain> (raw)
In-Reply-To: <20171114102246.22221-5-apahim@redhat.com>
On Tue, Nov 14, 2017 at 11:22:42AM +0100, Amador Pahim wrote:
> Currently we only cleanup on shutdown() if the VM is running.
>
> To make sure we will always cleanup, this patch makes the
> self._load_io_log() and the self._post_shutdown() to
> always be called on shutdown(), regardless the VM running state.
>
> Reviewed-by: Fam Zheng <famz@redhat.com>
> Signed-off-by: Amador Pahim <apahim@redhat.com>
> ---
> scripts/qemu.py | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/qemu.py b/scripts/qemu.py
> index 28aa3712c7..7bd10b1a1d 100644
> --- a/scripts/qemu.py
> +++ b/scripts/qemu.py
> @@ -162,8 +162,9 @@ class QEMUMachine(object):
> return self._popen.pid
>
> def _load_io_log(self):
> - with open(self._qemu_log_path, "r") as iolog:
> - self._iolog = iolog.read()
> + if self._qemu_log_path is not None:
> + with open(self._qemu_log_path, "r") as iolog:
> + self._iolog = iolog.read()
>
> def _base_args(self):
> if isinstance(self._monitor_address, tuple):
> @@ -254,8 +255,8 @@ class QEMUMachine(object):
> self._popen.kill()
> self._popen.wait()
>
> - self._load_io_log()
> - self._post_shutdown()
> + self._load_io_log()
_load_io_log() is now safe to call at any time thanks to the hunk
above.
> + self._post_shutdown()
_post_shutdown() is safe to call at any time thanks to patch 2/8.
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
>
> exitcode = self.exitcode()
> if exitcode is not None and exitcode < 0:
> --
> 2.13.6
>
>
--
Eduardo
next prev parent reply other threads:[~2018-01-19 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 10:22 [Qemu-devel] [PATCH v11 0/8] scripts/qemu.py fixes and cleanups Amador Pahim
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 1/8] qemu.py: remove unused import Amador Pahim
2018-01-19 17:26 ` Eduardo Habkost
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 2/8] qemu.py: better control of created files Amador Pahim
2018-01-19 17:26 ` Eduardo Habkost
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 3/8] qemu.py: refactor launch() Amador Pahim
2018-01-19 17:29 ` Eduardo Habkost
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 4/8] qemu.py: always cleanup on shutdown() Amador Pahim
2018-01-19 17:33 ` Eduardo Habkost [this message]
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 5/8] qemu.py: use poll() instead of 'returncode' Amador Pahim
2018-01-19 17:37 ` Eduardo Habkost
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 6/8] qemu.py: cleanup redundant calls in launch() Amador Pahim
2018-01-19 17:37 ` Eduardo Habkost
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 7/8] qemu.py: launch vm only if it's not running Amador Pahim
2018-01-19 17:51 ` Eduardo Habkost
2017-11-14 10:22 ` [Qemu-devel] [PATCH v11 8/8] qemu.py: don't launch again before shutdown() Amador Pahim
2018-01-19 17:52 ` Eduardo Habkost
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=20180119173315.GE15832@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=apahim@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=famz@redhat.com \
--cc=muriloo@linux.vnet.ibm.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 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.