From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [BUG] -no-quit does not work, this is bad when using -snapshot
Date: Fri, 6 Mar 2009 09:54:55 +0100 [thread overview]
Message-ID: <20090306085455.GH32521@hall.aurel32.net> (raw)
In-Reply-To: <49B0E254.2040302@sbeh.de>
On Fri, Mar 06, 2009 at 09:44:04AM +0100, Stan Behrens wrote:
> Hi List,
>
> -no-quit does not work. This is bad if you're using -snapshot and want to have a clean virtual disk-image after guest-shutdown. You have no possibility to commit because qemu just quits and the /tmp/snapshot-File is not accessible anymore.
$ qemu --help | grep no-quit
-no-quit disable SDL window close capability
This option works perfectly, there is no bug.
What you want is -no-shutdown.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2009-03-06 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 8:44 [Qemu-devel] [BUG] -no-quit does not work, this is bad when using -snapshot Stan Behrens
2009-03-06 8:54 ` Aurelien Jarno [this message]
2009-03-06 9:02 ` [Qemu-devel] [BUG SOLVED] use -no-shutdown instead of -no-quit Stan Behrens
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=20090306085455.GH32521@hall.aurel32.net \
--to=aurelien@aurel32.net \
--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).