From: Eric Blake <eblake@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Chijianchun <chijianchun@huawei.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>,
"paul@codesourcery.com" <paul@codesourcery.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Are there plans to achieve ram live Snapshot feature?
Date: Fri, 09 Aug 2013 09:51:42 -0600 [thread overview]
Message-ID: <5205100E.60007@redhat.com> (raw)
In-Reply-To: <877gfu3m25.fsf@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On 08/09/2013 09:45 AM, Anthony Liguori wrote:
> Chijianchun <chijianchun@huawei.com> writes:
>
>> Now in KVM, when RAM snapshot, vcpus needs stopped, it is Unfriendly restrictions to users.
>>
>> Are there plans to achieve ram live Snapshot feature?
>
> I think you mean a live version of the savevm command.
>
> You can approximate live migrating to a file, creating an external disk
> snapshot, then resuming the guest.
And libvirt does just that, since libvirt 1.0.5, for its external RAM
snapshots. The vcpu pause is a mere fraction of a second, so it is
generally not noticeable as any guest downtime.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-08-09 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 10:20 [Qemu-devel] Are there plans to achieve ram live Snapshot feature? Chijianchun
2013-08-09 15:38 ` Paolo Bonzini
2013-08-09 15:45 ` Anthony Liguori
2013-08-09 15:51 ` Eric Blake [this message]
2013-08-12 9:59 ` Stefan Hajnoczi
2013-08-12 10:26 ` Alex Bligh
2013-08-12 11:33 ` Stefan Hajnoczi
2013-08-13 2:53 ` Wenchao Xia
2013-08-13 8:21 ` Stefan Hajnoczi
2013-08-14 1:54 ` Wenchao Xia
2013-08-14 7:53 ` Stefan Hajnoczi
2013-08-14 8:13 ` Alex Bligh
2013-08-15 2:26 ` Wenchao Xia
2013-08-15 7:49 ` Stefan Hajnoczi
2013-08-15 8:03 ` Wenchao Xia
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=5205100E.60007@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=chijianchun@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paul@codesourcery.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).