xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Fajar A. Nugraha" <list@fajar.net>
To: Darren Shepherd <darren.s.shepherd@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: blktap3 as a block device?
Date: Sat, 24 Nov 2012 07:39:39 +0700	[thread overview]
Message-ID: <CAG1y0sci4Q8=Vy7i3NPfdYmH6e9rbvrHUPeoz_03+9_GvaHTwA@mail.gmail.com> (raw)
In-Reply-To: <CAMCEDC0sU+kBkGWmUoWwyOJ8pURZGwVgN1_xqDkt1MvxR-vE4A@mail.gmail.com>

On Sat, Nov 24, 2012 at 7:31 AM, Darren Shepherd
<darren.s.shepherd@gmail.com> wrote:
> So currently blktap2 can be used outside of Xen, but I don't think many
> people do that.  I have a use case now where I must support KVM (I currently
> run only Xen servers) and found the disk snapshotting to be not as nice as
> what I can do with vhd's in blktap2 (and a half).  So I was thinking of
> actually trying to just run blktap for the storage.  So I'm pretty pleased
> with that solution and functionally it works just fine.
>
> The problem now is blktap3.  So is there going to be any way to use blktap3
> outside of Xen?  If blktap3 is the future I probably won't continue with my
> blktap/kvm solution.

Since AFAIK blktap3 is not even in xen-unstable, personally I'd just
use something with more userbase and better tested. Something like
zfsonlinux. It has support for sparse zvols, as well as snapshot and
clones.

-- 
Fajar

  reply	other threads:[~2012-11-24  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24  0:31 blktap3 as a block device? Darren Shepherd
2012-11-24  0:39 ` Fajar A. Nugraha [this message]
2012-11-24  1:08   ` Darren Shepherd
2012-11-26 10:45     ` Ian Campbell
2012-11-26 10:54       ` Thanos Makatos
2012-11-26 11:48         ` Roger Pau Monné
2012-11-26 19:50     ` Stefano Stabellini

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='CAG1y0sci4Q8=Vy7i3NPfdYmH6e9rbvrHUPeoz_03+9_GvaHTwA@mail.gmail.com' \
    --to=list@fajar.net \
    --cc=darren.s.shepherd@gmail.com \
    --cc=xen-devel@lists.xen.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).