On Mon, May 23, 2011 at 2:02 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Sun, May 22, 2011 at 10:52 AM, Dor Laor dl...@redhat.com wrote:
On 05/20/2011 03:19 PM, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look like.
Specifically how does user software do the
On 5/27/2011 9:46 AM, Stefan Hajnoczi wrote:
On Mon, May 23, 2011 at 2:02 PM, Stefan Hajnoczistefa...@gmail.com wrote:
On Sun, May 22, 2011 at 10:52 AM, Dor Laordl...@redhat.com wrote:
On 05/20/2011 03:19 PM, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look
On Sun, May 22, 2011 at 10:52 AM, Dor Laor dl...@redhat.com wrote:
On 05/20/2011 03:19 PM, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look like.
Specifically how does user software do the following:
1. Create a snapshot
2. Delete a snapshot
3. List snapshots
On 05/20/2011 03:19 PM, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look like.
Specifically how does user software do the following:
1. Create a snapshot
2. Delete a snapshot
3. List snapshots
4. Access data from a snapshot
There are plenty of options there:
-
Hello Stefan,
I have been thinking about this since you sent out this message.
A quick look at the libvirt API indicates that their notion of a
snapshot often refers to a disk+memory snapshot. It would
be good to provide feedback to the libvirt developers to make
sure that proper support for a
I'm interested in what the API for snapshots would look like.
Specifically how does user software do the following:
1. Create a snapshot
2. Delete a snapshot
3. List snapshots
4. Access data from a snapshot
5. Restore a VM from a snapshot
6. Get the dirty blocks list (for incremental backup)
On 05/20/11 14:19, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look like.
I presume you're talking external snapshots here? The API is really what
should be defined by libvirt, so you get a unified API that can work
both on QEMU level snapshots as well as enterprise
On Fri, May 20, 2011 at 1:39 PM, Jes Sorensen jes.soren...@redhat.com wrote:
On 05/20/11 14:19, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look like.
I presume you're talking external snapshots here? The API is really what
should be defined by libvirt, so you
On 05/20/11 14:49, Stefan Hajnoczi wrote:
On Fri, May 20, 2011 at 1:39 PM, Jes Sorensen jes.soren...@redhat.com wrote:
On 05/20/11 14:19, Stefan Hajnoczi wrote:
I'm interested in what the API for snapshots would look like.
I presume you're talking external snapshots here? The API is really
Hello Dor,
I'm glad I could convince you of the value of Livebackup. I
think Livesnapshot/Livemerge, Livebackup and Block
Migration all have very interesting use cases. For example:
- Livesnapshot/Livemerge is very useful in development/QA
environments where one might want to create a
On 05/16/2011 11:23 AM, Jagane Sundar wrote:
Hello Dor,
Let me see if I understand live snapshot correctly:
If I want to configure a VM for daily backup, then I would do
the following:
- Create a snapshot s1. s0 is marked read-only.
- Do a full backup of s0 on day 0.
- On day 1, I would create
On 05/16/2011 12:38 AM, Jagane Sundar wrote:
Hello Dor,
One important advantage of live snapshot over live backup is support of
multiple (consecutive) live snapshots while there can be only a single
live backup at one time.
This is why I tend to think that although live backup carry some
Hello Dor,
Let me see if I understand live snapshot correctly:
If I want to configure a VM for daily backup, then I would do
the following:
- Create a snapshot s1. s0 is marked read-only.
- Do a full backup of s0 on day 0.
- On day 1, I would create a new snapshot s2, then
copy over the
On 05/13/2011 06:16 AM, Jagane Sundar wrote:
On 5/12/2011 8:33 AM, Jes Sorensen wrote:
On 05/09/11 15:40, Dor Laor wrote:
Summary:
* We need Marcelo's new (to come) block copy implementation
* should work in parallel to migration and hotplug
* General copy on read is desirable
* Live snapshot
Hello Dor,
One important advantage of live snapshot over live backup is support of
multiple (consecutive) live snapshots while there can be only a single
live backup at one time.
This is why I tend to think that although live backup carry some benefit
(no merge required), the live snapshot +
On Mon, May 09, 2011 at 10:23:03AM -0500, Anthony Liguori wrote:
On 05/09/2011 08:40 AM, Dor Laor wrote:
No patch here (sorry) but collection of thoughts about these features
and their potential building blocks. Please review (also on
http://wiki.qemu.org/Features/LiveBlockMigration)
Future
On 05/09/11 15:40, Dor Laor wrote:
Summary:
* We need Marcelo's new (to come) block copy implementation
* should work in parallel to migration and hotplug
* General copy on read is desirable
* Live snapshot merge to be implemented using block copy
* Need to utilize a remote block
On 05/09/11 17:23, Anthony Liguori wrote:
* Live snapshots and live snapshot merge
Live snapshot is already incorporated (by Jes) in qemu (still need
qemu-agent work to freeze the guest FS).
Live snapshot is unfortunately not really live. It runs a lot of
operations synchronously which
On 5/12/2011 8:33 AM, Jes Sorensen wrote:
On 05/09/11 15:40, Dor Laor wrote:
Summary:
* We need Marcelo's new (to come) block copy implementation
* should work in parallel to migration and hotplug
* General copy on read is desirable
* Live snapshot merge to be implemented using
On Mon, May 09, 2011 at 04:40:00PM +0300, Dor Laor wrote:
No patch here (sorry) but collection of thoughts about these
features and their potential building blocks. Please review (also on
http://wiki.qemu.org/Features/LiveBlockMigration)
Future qemu is expected to support these features
No patch here (sorry) but collection of thoughts about these features
and their potential building blocks. Please review (also on
http://wiki.qemu.org/Features/LiveBlockMigration)
Future qemu is expected to support these features (some already
implemented):
* Live block copy
Ability to
On 05/09/2011 08:40 AM, Dor Laor wrote:
No patch here (sorry) but collection of thoughts about these features
and their potential building blocks. Please review (also on
http://wiki.qemu.org/Features/LiveBlockMigration)
Future qemu is expected to support these features (some already
On 05/09/2011 06:23 PM, Anthony Liguori wrote:
On 05/09/2011 08:40 AM, Dor Laor wrote:
No patch here (sorry) but collection of thoughts about these features
and their potential building blocks. Please review (also on
http://wiki.qemu.org/Features/LiveBlockMigration)
Future qemu is expected to
23 matches
Mail list logo
