From: Eduardo Habkost <ehabkost@redhat.com>
To: Amador Pahim <apahim@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@gmail.com, famz@redhat.com,
berrange@redhat.com, mreitz@redhat.com, kwolf@redhat.com,
armbru@redhat.com, crosa@redhat.com, ldoktor@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 6/6] qemu.py: include qemu command line and output on launch error
Date: Tue, 25 Jul 2017 18:17:29 -0300 [thread overview]
Message-ID: <20170725211729.GX2757@localhost.localdomain> (raw)
In-Reply-To: <20170725171014.25193-7-apahim@redhat.com>
On Tue, Jul 25, 2017 at 07:10:14PM +0200, Amador Pahim wrote:
> When launching a VM, if an exception happens and the VM is not
> initiated, it is useful to see the qemu command line that was executed
> and the output of that command.
>
> Signed-off-by: Amador Pahim <apahim@redhat.com>
> ---
> scripts/qemu.py | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/qemu.py b/scripts/qemu.py
> index e18e8ec657..abfa3eebe9 100644
> --- a/scripts/qemu.py
> +++ b/scripts/qemu.py
> @@ -131,7 +131,8 @@ class QEMUMachine(object):
>
> def launch(self):
> '''
> - Try to launch the VM and make sure we cleanup on exception.
> + Try to launch the VM and make sure we cleanup and expose the
> + command line/output in case of exception.
> '''
> if self.is_running():
> return
> @@ -142,18 +143,24 @@ class QEMUMachine(object):
> self.shutdown()
>
> try:
> - self._launch()
> + args = None
> + args = self._wrapper + [self._binary] + self._base_args() + self._args
> + self._launch(args)
I think it would be easier to set a self._full_qemu_args
attribute instead of passing data around through local variables
and method arguments.
> self._shutdown_pending = True
> except:
> self.shutdown()
> + sys.stderr.write('Error launching VM.\n%s%s' %
> + ('Command:\n%s\n' %
> + ' '.join(args) if args else '',
> + 'Output:\n%s\n' %
> + ''.join(self._iolog) if self._iolog else ''))
I suggest making this conditional on self._debug.
We could also introduce a QEMULaunchError exception class
containing this info, but I'm unsure if we should raise it on
every exception, or raise more specific custom exceptions on
specific cases (e.g. one exception for QMP timeout, another for
QEMU binary not found, another for QEMU killed by a signal, etc).
> raise
>
> - def _launch(self):
> + def _launch(self, args):
> '''Launch the VM and establish a QMP connection.'''
> devnull = open('/dev/null', 'rb')
> qemulog = open(self._qemu_log_path, 'wb')
> self._pre_launch()
> - args = self._wrapper + [self._binary] + self._base_args() + self._args
> self._popen = subprocess.Popen(args, stdin=devnull, stdout=qemulog,
> stderr=subprocess.STDOUT, shell=False)
> self._post_launch()
> --
> 2.13.3
>
--
Eduardo
next prev parent reply other threads:[~2017-07-25 21:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 17:10 [Qemu-devel] [PATCH v5 0/6] scripts/qemu.py fixes and cleanups Amador Pahim
2017-07-25 17:10 ` [Qemu-devel] [PATCH v5 1/6] qemu.py: make 'args' public Amador Pahim
2017-07-27 14:18 ` Stefan Hajnoczi
2017-07-27 14:59 ` Amador Pahim
2017-07-25 17:10 ` [Qemu-devel] [PATCH v5 2/6] qemu.py: use poll() instead of 'returncode' Amador Pahim
2017-07-27 14:11 ` Stefan Hajnoczi
2017-07-25 17:10 ` [Qemu-devel] [PATCH v5 3/6] qemu.py: cleanup message on negative exit code Amador Pahim
2017-07-25 19:08 ` Cleber Rosa
2017-07-25 19:51 ` Eduardo Habkost
2017-07-27 8:21 ` Amador Pahim
2017-07-30 20:24 ` Eduardo Habkost
2017-07-27 14:12 ` Stefan Hajnoczi
2017-07-25 17:10 ` [Qemu-devel] [PATCH v5 4/6] qemu.py: cleanup launch() Amador Pahim
2017-07-25 19:17 ` Cleber Rosa
2017-07-25 20:42 ` Eduardo Habkost
2017-07-27 7:56 ` Amador Pahim
2017-07-25 17:10 ` [Qemu-devel] [PATCH v5 5/6] qemu.py: make sure shutdown() is called before launching again Amador Pahim
2017-07-25 19:58 ` Eduardo Habkost
2017-07-25 17:10 ` [Qemu-devel] [PATCH v5 6/6] qemu.py: include qemu command line and output on launch error Amador Pahim
2017-07-25 21:17 ` Eduardo Habkost [this message]
2017-07-27 8:01 ` Amador Pahim
2017-07-27 13:31 ` [Qemu-devel] [PATCH v5 0/6] scripts/qemu.py fixes and cleanups no-reply
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=20170725211729.GX2757@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=apahim@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=ldoktor@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).