From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"stefanha@gmail.com" <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"blauwirbel@gmail.com" <blauwirbel@gmail.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 0/2] live backup vm
Date: Sun, 09 Dec 2012 12:37:58 +0800 [thread overview]
Message-ID: <50C415A6.504@linux.vnet.ibm.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F75578601DF@lisa.maurer-it.com>
于 2012-12-7 18:12, Dietmar Maurer 写道:
> We already have a full functional implementation to create live snapshots including VM state.
>
> The interface allows you to create internal snapshots, or use external tools to create the blockdev snapshots
> directly on the underlying storage (we use that with nexenta). VM state is stored directly on a block device.
>
> https://git.proxmox.com/?p=pve-qemu-kvm.git;a=blob;f=debian/patches/internal-snapshot-async.patch;h=6c86de3a6160c58d77baa41a7774c4a80e63639e;hb=HEAD
>
> Unfortunately I had no time to cleanup those patches.
>
> - Dietmar
>
have that patch been sent to mail-list? I'll rebase that patch
and take it as part of the API's implemention, if you agree.
>> 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(-)
>>
>>
>
>
>
--
Best Regards
Wenchao Xia
next prev parent reply other threads:[~2012-12-09 4:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 8:24 [Qemu-devel] [RFC PATCH 0/2] live backup vm Wenchao Xia
2012-12-07 10:12 ` Dietmar Maurer
2012-12-09 4:37 ` Wenchao Xia [this message]
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=50C415A6.504@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).