From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
Pavel Hrdina <phrdina@redhat.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [RFC]VM live snapshot proposal
Date: Mon, 03 Mar 2014 14:19:37 +0100 [thread overview]
Message-ID: <53148169.6060700@redhat.com> (raw)
In-Reply-To: <20140303125520.GF4850@dhcp-200-207.str.redhat.com>
Il 03/03/2014 13:55, Kevin Wolf ha scritto:
>>> > > Due to memory-modifications may happen in kvm, qemu, or vhost, the key-part is how we
>>> > > can provide common page-modify-tracking-and-saving api, we completed a prototype by
>>> > > simply add modified-page tracking/saving function in qemu, and it seems worked fine.
>> >
>> > Yes, this is the tricky part. To be honest, I think this is the reason
>> > no one has submitted patches - it's a hard task and the win isn't that
>> > great (you can already migrate to file).
> So why don't we simply reuse the existing migration code?
I think this is different in the same way that block-backup and
block-mirror are different. Huangpeng's proposal would let you make a
consistent snapshot of disks and RAM.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: Pavel Hrdina <phrdina@redhat.com>,
Zhanghailiang <zhang.zhanghailiang@huawei.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC]VM live snapshot proposal
Date: Mon, 03 Mar 2014 14:19:37 +0100 [thread overview]
Message-ID: <53148169.6060700@redhat.com> (raw)
In-Reply-To: <20140303125520.GF4850@dhcp-200-207.str.redhat.com>
Il 03/03/2014 13:55, Kevin Wolf ha scritto:
>>> > > Due to memory-modifications may happen in kvm, qemu, or vhost, the key-part is how we
>>> > > can provide common page-modify-tracking-and-saving api, we completed a prototype by
>>> > > simply add modified-page tracking/saving function in qemu, and it seems worked fine.
>> >
>> > Yes, this is the tricky part. To be honest, I think this is the reason
>> > no one has submitted patches - it's a hard task and the win isn't that
>> > great (you can already migrate to file).
> So why don't we simply reuse the existing migration code?
I think this is different in the same way that block-backup and
block-mirror are different. Huangpeng's proposal would let you make a
consistent snapshot of disks and RAM.
Paolo
next prev parent reply other threads:[~2014-03-03 13:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 1:13 [RFC]VM live snapshot proposal Huangpeng (Peter)
2014-03-03 1:13 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-03 12:32 ` Stefan Hajnoczi
2014-03-03 12:32 ` [Qemu-devel] " Stefan Hajnoczi
2014-03-03 12:55 ` Kevin Wolf
2014-03-03 12:55 ` [Qemu-devel] " Kevin Wolf
2014-03-03 13:19 ` Paolo Bonzini [this message]
2014-03-03 13:19 ` Paolo Bonzini
2014-03-03 13:30 ` Kevin Wolf
2014-03-03 13:30 ` [Qemu-devel] " Kevin Wolf
2014-03-03 13:47 ` Paolo Bonzini
2014-03-03 13:47 ` [Qemu-devel] " Paolo Bonzini
2014-03-03 14:04 ` Kevin Wolf
2014-03-03 14:04 ` [Qemu-devel] " Kevin Wolf
2014-03-03 14:55 ` Dr. David Alan Gilbert
2014-03-03 14:55 ` Dr. David Alan Gilbert
2014-03-03 19:52 ` Andrea Arcangeli
2014-03-03 19:52 ` [Qemu-devel] " Andrea Arcangeli
2014-03-04 1:35 ` Huangpeng (Peter)
2014-03-04 1:35 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-05 14:46 ` Andrea Arcangeli
2014-03-05 14:46 ` [Qemu-devel] " Andrea Arcangeli
2014-03-05 1:52 ` Huangpeng (Peter)
2014-03-05 1:52 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-05 14:55 ` Andrea Arcangeli
2014-03-05 14:55 ` [Qemu-devel] " Andrea Arcangeli
2014-03-04 1:28 ` Huangpeng (Peter)
2014-03-04 1:28 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-04 9:40 ` Dr. David Alan Gilbert
2014-03-04 9:40 ` Dr. David Alan Gilbert
2014-03-05 1:00 ` Huangpeng (Peter)
2014-03-05 1:00 ` Huangpeng (Peter)
2014-03-05 9:09 ` Paolo Bonzini
2014-03-06 1:42 ` Huangpeng (Peter)
2014-03-06 1:42 ` Huangpeng (Peter)
2014-03-06 9:14 ` Dr. David Alan Gilbert
2014-03-04 1:06 ` Huangpeng (Peter)
2014-03-04 1:06 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-03 13:18 ` Paolo Bonzini
2014-03-03 13:18 ` [Qemu-devel] " Paolo Bonzini
2014-03-04 1:02 ` Huangpeng (Peter)
2014-03-04 1:02 ` [Qemu-devel] " Huangpeng (Peter)
2014-03-04 8:54 ` Stefan Hajnoczi
2014-03-04 8:54 ` [Qemu-devel] " Stefan Hajnoczi
2014-03-04 9:05 ` Paolo Bonzini
2014-03-04 9:05 ` [Qemu-devel] " Paolo Bonzini
2014-03-04 11:28 ` Wenchao Xia
2014-03-04 11:28 ` Wenchao Xia
2014-03-05 0:46 ` Huangpeng (Peter)
2014-03-05 0:46 ` [Qemu-devel] " Huangpeng (Peter)
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=53148169.6060700@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=phrdina@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=xiawenc@linux.vnet.ibm.com \
--cc=zhang.zhanghailiang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.