qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Juan Quintela <quintela@redhat.com>,
	Pavel Hrdina <phrdina@redhat.com>,
	Dietmar Maurer <dietmar@proxmox.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel]  [RFC] lively write vmstate with predictable size
Date: Fri, 21 Dec 2012 10:25:51 +0800	[thread overview]
Message-ID: <50D3C8AF.7050506@linux.vnet.ibm.com> (raw)
In-Reply-To: <50D2CC22.1060900@linux.vnet.ibm.com>

resent the mail to mail-list.
-------------------

Hi, Paolo and Juan
    Currently savevm needs pause vm, and I am working on that make it
 lively. Considering the flexibility I'd like to split out the
 functions apart as following:
 1) snapshot lively internal/external
 2) save vmstate lively internal/external
 3) assemble them as will

 1) was sent at
 http://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg02393.html

 but for 2), I think it have problem because file size may grow to a size
 out of control. Considering the migration code, I'd like to propose a
 way to fix it as following:

 Migration logic:
 Src send->dest recv->data analysis->copy data
 Savevm logic:
 Src send->write data to qcow2.

My suggestion:
 Savevm logic:
 Src send->dest recv->data analysis->write data to qcow2/external with
 addr.

   The idea is do the write operation after data analysis, and overwrite
 old data if address overlaps. So this will need qcow2 support
 write snapshot data at "address", and also change some savevm logic.

   Could u give some some comments on this to see if it is workable?


-- 
Best Regards

Wenchao Xia

       reply	other threads:[~2012-12-21  2:26 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 ` Wenchao Xia [this message]
2012-12-21 18:36   ` [Qemu-devel] [RFC] lively write vmstate with predictable size 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
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=50D3C8AF.7050506@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.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 \
    /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).