qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Terjan <pterjan@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] snapshots
Date: Mon, 23 May 2005 10:04:27 +0200	[thread overview]
Message-ID: <e8ca353705052301047782d366@mail.gmail.com> (raw)

hello,
qemu has -loadvm and -snapshot but I don't like having to take care of
using the right vm dump with the snapshot, and having to think to
savevm to the right file when I commit the disk.

What do you think of snapshot/commit (or an additionnal equivalent
command) working with full state ?

             reply	other threads:[~2005-05-23  8:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23  8:04 Pascal Terjan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-27  5:47 [Qemu-devel] snapshots chandra shekar
2010-09-28  2:03 ` edison
2010-10-04  4:56 chandra shekar
2010-10-05  4:44 ` Mulyadi Santosa
2010-10-12  9:13 chandra shekar
2010-10-12  9:46 ` Stefan Hajnoczi
2010-10-14 10:22 chandra shekar
2010-10-14 16:51 ` Mulyadi Santosa
2011-01-07  4:37 chandra shekar
2011-01-07  9:54 ` Stefan Hajnoczi

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=e8ca353705052301047782d366@mail.gmail.com \
    --to=pterjan@gmail.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).