qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Pavel Hrdina <phrdina@redhat.com>,
	quintela@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [Qemu-devel] [RFC] lively write vmstate with predictable size
Date: Sat, 05 Jan 2013 20:28:18 -0700	[thread overview]
Message-ID: <50E8EF52.5080507@redhat.com> (raw)
In-Reply-To: <50E7E27A.8050209@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]

On 01/05/2013 01:21 AM, Wenchao Xia wrote:
>   I guess migration to file makes vm stopped, and lack a step
> to take snapshot in the end of migration, also the usage seems
> strange makes me feel something is lacking. I'd like to
> have:
> 1 take blk snapshot internal/external lively.
> 2 take vmstate snapshot internal/external lively.
> 3 combination.

Libvirt 1.0.1 can already do external live snapshots - it does a live
migration to file, and when that finally converges enough to pause,
there is less than a second of downtime when libvirt then follows up
with an external disk snapshot and then resumes the guest.  Of course,
this approach requires multiple files, and there is no way to take an
internal snapshot with current QMP support.  And the point remains in
this thread that a live migration to file takes more space than a paused
migration, in part because earlier portions of the migration stream are
revisited later in the stream as memory pages continue to be touched
during the live migration.  So a new format for seekable migration to
file, different than current migration being usable over a fifo, may
indeed allow for less disk space and faster booting when reverting to
that vmstate.

-- 
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: 619 bytes --]

  reply	other threads:[~2013-01-06  3:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50D2CC22.1060900@linux.vnet.ibm.com>
2012-12-21  2:25 ` [Qemu-devel] [RFC] lively write vmstate with predictable size Wenchao Xia
2012-12-21 18:36   ` Juan Quintela
2012-12-25  5:07     ` Wenchao Xia
2012-12-27  2:40       ` Wenchao Xia
2013-01-04 17:35   ` Stefan Hajnoczi
2013-01-04 22:42     ` Juan Quintela
2013-01-05  8:21       ` Wenchao Xia
2013-01-06  3:28         ` Eric Blake [this message]
2013-01-07 12:35           ` 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=50E8EF52.5080507@redhat.com \
    --to=eblake@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=dietmar@proxmox.com \
    --cc=pbonzini@redhat.com \
    --cc=phrdina@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    --cc=xiawenc@linux.vnet.ibm.com \
    /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).