From: Eric Blake <eblake@redhat.com>
To: Vasiliy Tolstov <v.tolstov@selfip.ru>, Kevin Wolf <kwolf@redhat.com>
Cc: mitake.hitoshi@lab.ntt.co.jp, namei.unix@gmail.com,
sheepdog@lists.wpkg.org, qemu-devel <qemu-devel@nongnu.org>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] internal snapshots with sheepdog
Date: Fri, 18 Sep 2015 08:37:21 -0600 [thread overview]
Message-ID: <55FC21A1.5030400@redhat.com> (raw)
In-Reply-To: <CACaajQs0-=dO3a9X-w-vkhfTLB2yV9Zo8WNzSrETfZavd+TGjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On 09/18/2015 03:03 AM, Vasiliy Tolstov wrote:
> 2015-09-18 12:02 GMT+03:00 Kevin Wolf <kwolf@redhat.com>:
>> Doesn't sheepdog already support storing snapshots in the same image?
>> I thought it would just work; at least, there's some code there for it.
>
>
> Yes, qemu and sheepdog have ability to create internal snapshot, i
> miss that, but when i'm try in libvirt create live snapshot - libvirt
> says, that this is not possible with raw image.
That may be a case of libvirt being over-conservative because no one has
provided a patch to utilize what qemu provides.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-09-18 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 15:49 [Qemu-devel] internal snapshots with sheepdog Vasiliy Tolstov
2015-09-18 9:02 ` Kevin Wolf
2015-09-18 9:03 ` Vasiliy Tolstov
2015-09-18 9:49 ` Kevin Wolf
2015-09-18 10:37 ` [Qemu-devel] [sheepdog] " Hitoshi Mitake
2015-09-18 14:37 ` Eric Blake [this message]
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=55FC21A1.5030400@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mitake.hitoshi@lab.ntt.co.jp \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=v.tolstov@selfip.ru \
/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.