From: Brian Jackson <iggy@theiggy.com>
To: yue <kvmluck@163.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] from which version qemu support clone on rbd
Date: Wed, 02 Jul 2014 10:36:12 -0500 [thread overview]
Message-ID: <53B426EC.6000000@theiggy.com> (raw)
In-Reply-To: <55f3a6d8.2be20.146f7a712b8.Coremail.kvmluck@163.com>
Qemu doesn't handle that level of abstraction. The closest approximation
you could probably come up with is qemu-img's backing file support for
qcow2 images.
You should stick to using the rbd tool to create clones of rbd devices.
Alternatively, use a higher level tool (like openstack, etc) that
supports this.
--Iggy
On 7/2/2014 10:17 AM, yue wrote:
> hi,all
> i now look at qemu 2.0, i do not find rbd-api related to clone.
> if qemu support this function? and from which version?
> clone api of rbd is very simple(one api), why qemu does not
> implement?what is the reason?
> thanks.
>
>
next prev parent reply other threads:[~2014-07-02 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 15:17 [Qemu-devel] from which version qemu support clone on rbd yue
2014-07-02 15:36 ` Brian Jackson [this message]
2014-07-03 1:12 ` yue
2014-07-03 4:41 ` Brian Jackson
2014-07-04 8:20 ` Stefan Hajnoczi
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=53B426EC.6000000@theiggy.com \
--to=iggy@theiggy.com \
--cc=kvmluck@163.com \
--cc=qemu-devel@nongnu.org \
/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).