Re: [Xen-devel] RFC: blktap3

[Thanos Makatos <thanos.makatos@xxxxxxxxxx>]

Hi Konrad,

I'm not sure I understand your question. Blktap3 lives in tools/blktap3. The 
component that allows tapdisk3 to talk directly to blkfront is xenio, it lives 
in blktap3/tools/xenio. Since tapdisk3 can talk to blkfront via xenio, it 
doesn't interact with blkback/blktap kernel drivers.

-----Original Message-----
From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx] 
Sent: 09 August 2012 19:05
To: Thanos Makatos
Cc: xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] RFC: blktap3

On Thu, Aug 09, 2012 at 03:03:06PM +0100, Thanos Makatos wrote:
> Hi,
> 
> I'd like to introduce blktap3: essentially blktap2 without the need of 
> blkback. This has been developed by Santosh Jodh, and I'll maintain it.
> 

So where is the source of this driver located?
> In this patch, blktap2 binaries are suffixed with "2", so it's not yet 
> possible to use it along with blktap3.
> 
> An example configuration file I used is the following:
> name = "debian bktap3 without pygrub"
> memory = 256
> disk = 
> ['backendtype=xenio,format=vhd,vdev=xvda,access=rw,target=/root/debian-blktap3.vhd']
> kernel = "vmlinuz-2.6.32-5-amd64"
> root = '/dev/xvda1'
> ramdisk = "initrd.img-2.6.32-5-amd64"
> cpu_weight=256
> vif=['bridge=xenbr0']
> 
> Before starting any blktap3 VM, the xenio daemon must be started.
> 
> I've tested it on change set 472fc515a463 without pygrub.
> 
> Any comments are welcome :)
> 
> --
> Thanos Makatos
> 


> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel