From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix termination by signal with -no-shutdown
Date: Fri, 16 Sep 2011 09:10:10 -0500 [thread overview]
Message-ID: <4E7358C2.2090204@codemonkey.ws> (raw)
In-Reply-To: <1316007520-30808-1-git-send-email-kwolf@redhat.com>
On 09/14/2011 08:38 AM, Kevin Wolf wrote:
> On signals such as SIGTERM qemu should exit instead of just stopping the VM
> even with -no-shutdown.
>
> Signed-off-by: Kevin Wolf<kwolf@redhat.com>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> vl.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index b773d2f..0c2fc3f 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -1296,6 +1296,7 @@ void qemu_system_killed(int signal, pid_t pid)
> {
> shutdown_signal = signal;
> shutdown_pid = pid;
> + no_shutdown = 0;
> qemu_system_shutdown_request();
> }
>
prev parent reply other threads:[~2011-09-16 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 13:38 [Qemu-devel] [PATCH] Fix termination by signal with -no-shutdown Kevin Wolf
2011-09-16 14:10 ` Anthony Liguori [this message]
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=4E7358C2.2090204@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@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).