From: Avi Kivity <avi@redhat.com>
To: Daniel Gollub <gollub@b1-systems.de>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] qemu-kvm: Handle -no-shutodwn
Date: Wed, 20 May 2009 14:51:16 +0300 [thread overview]
Message-ID: <4A13EEB4.9090703@redhat.com> (raw)
In-Reply-To: <200905192328.31362.gollub@b1-systems.de>
Daniel Gollub wrote:
> Plain QEMU has the parameter -no-shutdown. This avoids termination of the qemu
> process when VM got shutdown (e.g. to still use the QEMU-Monitor with stopped
> VM). This parameter has no effect on qemu-kvm, today.
>
> This patch introduces identical handling, as in qemu, of -no-shutdown for
> qemu-kvm:
>
> * termination of qemu-kvm process on a VM shutdown get only avoided once
> * second shutdown of VM cause termination of qemu-kvm (like in qemu)
>
>
Applied, thanks.
What is the reason for the wierd semantics? I'd expect -no-shutdown to
keep functioning even after the first shutdown.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-20 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 21:28 [PATCH] qemu-kvm: Handle -no-shutodwn Daniel Gollub
2009-05-20 11:51 ` Avi Kivity [this message]
2009-05-20 12:20 ` Daniel Gollub
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=4A13EEB4.9090703@redhat.com \
--to=avi@redhat.com \
--cc=gollub@b1-systems.de \
--cc=kvm@vger.kernel.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