qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, aliguori@us.ibm.com, stefanha@gmail.com,
	Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	blauwirbel@gmail.com, pbonzini@redhat.com, dietmar@proxmox.com
Subject: [Qemu-devel] [RFC PATCH 0/2] live backup vm
Date: Sat,  8 Dec 2012 16:24:17 +0800	[thread overview]
Message-ID: <1354955059-14391-1-git-send-email-xiawenc@linux.vnet.ibm.com> (raw)

  This patch is a scratch which enables a full live backup of VM,
actually it is equal to savevm lively. As a test it uses hmp
command migrate to trigger the action.

  The ultimate goal is providing another command to user as:
snapshotvm [with_state] [internal] [live]
which then create vm backups with a screen image(I am not sure if a
screen snapshot is supported in qemu now). This function is enabled
in VMWARE which can automatically create full vm snapshots lively
with a screen image which seems cool, so I want to introduce it
to qemu.

Limitations:
  currently only implemented "snapshotvm with_state internal live" case.
  no screen captured in the time of creating snapshots.
  no good integration with existing savevm, migration, snapshot_blkdev
code.
  no test case yet.
  hmp/qmp API not added.

  Although there are so many gaps, but I want to send these patch
first to make sure I am in the right direction, esp the implemention
of savevm lively with vmstate, to see if there is potentional problem,
such as creating snapshots takes too long? Other cases would be simpler
if this case have no major problem found. 

Wenchao Xia (2):
  live backup vm, export functions
  live backup vm, snapshots all lively

 block.c         |   21 ++++++
 block.h         |    2 +
 buffered_file.c |  106 +++++++++++++++++++++++++++
 buffered_file.h |    1 +
 migration.c     |  215 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 migration.h     |   13 ++++
 savevm.c        |   37 +++-------
 sysemu.h        |    2 +
 8 files changed, 371 insertions(+), 26 deletions(-)

             reply	other threads:[~2012-12-07  8:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08  8:24 Wenchao Xia [this message]
2012-12-07 10:12 ` [Qemu-devel] [RFC PATCH 0/2] live backup vm Dietmar Maurer
2012-12-09  4:37   ` Wenchao Xia
2012-12-09  7:12     ` Dietmar Maurer
2012-12-10  1:37       ` Wenchao Xia
2012-12-10  6:23         ` Dietmar Maurer
2012-12-11  7:14           ` Wenchao Xia
2012-12-11  7:46             ` Dietmar Maurer
2012-12-12  2:16               ` Wenchao Xia
2012-12-12  8:30               ` Paolo Bonzini
2012-12-12  8:50                 ` Dietmar Maurer
2012-12-12  9:03                 ` Dietmar Maurer
2012-12-12 10:00                   ` Paolo Bonzini
2012-12-08  8:24 ` [Qemu-devel] [RFC PATCH 1/2] live backup vm, export functions Wenchao Xia
2012-12-08  8:24 ` [Qemu-devel] [RFC PATCH 2/2] live backup vm, snapshots all lively 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=1354955059-14391-1-git-send-email-xiawenc@linux.vnet.ibm.com \
    --to=xiawenc@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=dietmar@proxmox.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).