| 1 |
On Sat, Jan 7, 2012 at 11:35 AM, Pandu Poluan <pandu@××××××.info> wrote: |
| 2 |
> On Jan 7, 2012 8:44 PM, "victor romanchuk" <rom@××××××××××.net> wrote: |
| 3 |
>> |
| 4 |
>> Konstantinos Agouros wrote, at 01/07/2012 03:51 PM: |
| 5 |
>> > since xen got into the mainstream kernel the way to go is to use |
| 6 |
>> > gentoo-sources for dom0 and the domUs. However the blktap modules are |
| 7 |
>> > not |
| 8 |
>> > there. Is there any way to get this to work? |
| 9 |
>> |
| 10 |
>> blktap drivers were excluded from kernel mainline since 3.x, these two |
| 11 |
>> threads |
| 12 |
>> from xen-users mailing list might put some light in that context: |
| 13 |
>> |
| 14 |
>> |
| 15 |
>> http://old-list-archives.xen.org/archives/html/xen-users/2011-07/msg00637.html |
| 16 |
>> |
| 17 |
>> http://old-list-archives.xen.org/archives/html/xen-users/2011-10/msg00065.html |
| 18 |
>> |
| 19 |
>> the latest sys-kernel/xen-sources containing working blktap (not blktap2) |
| 20 |
>> is |
| 21 |
>> 2.6.38 (this is buggy from my point of view; i'm still sitting on |
| 22 |
>> 2.6.34-r5 for |
| 23 |
>> production installations) |
| 24 |
>> |
| 25 |
> |
| 26 |
> Can someone shed a light on the importance of blktap, i.e., why one would |
| 27 |
> want to use it when -- as someone explained in the first email thread you |
| 28 |
> gave -- blkfront+blkend is enough for paravirtualization? |
| 29 |
|
| 30 |
Reading through the linked threads, it sounds like the benefit stems |
| 31 |
from being able to shim things in between the front and back ends. |
| 32 |
|
| 33 |
You might want that for any number of reasons: |
| 34 |
* a block encryption layer |
| 35 |
* a metering layer |
| 36 |
* a read/write masking layer |
| 37 |
* an intercept to have the block device exist on (or be mirrored to) |
| 38 |
on another system. |
| 39 |
|
| 40 |
etc. |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
:wq |
Archives