[Xen-users] blktap2 support in xen 4.5

[svenvan svenvan <svenvan.van@xxxxxxxxx>]

Hi,
xen 4.5 building from source on debian wheezy kernel 3.16 (backport package) amd64.

Trying to use blktap2 as storage backend.
Installed blktap-dkms from debian jessie repositories and loaded succesfully blktap module.

My domU cfg disk configuration is the following:

rootÂÂÂÂÂÂÂ = '/dev/xvda2 ro'
diskÂÂÂÂÂÂÂ = [
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 'tap2:tapdisk:aio:/home/xen/domains/wheezy-template64/disk.img,xvda2,w',
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ 'tap2:tapdisk:aio:/home/xen/domains/wheezy-template64/swap.img,xvda1,w',

When I launch domU I don't get any warning/error message and domU boot correctly.Â

Strange thing is that ps auxwww shows:

/usr/local/lib/xen/bin/qemu-system-i386 -xen-domid 20 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-20,server,nowait -mon chardev=libxl-cmd,mode=control -nodefaults -xen-attach -name wheezy-template64 -nographic -machine xenpv -m 256

So it seems it's using qdisk in place of blktap2...

According to INSTALL doc:
The old backend drivers are disabled because qdisk is now the default.
This option can be used to build them anyway.
 --enable-blktap1
 --enable-blktap2

So I recompiled from source enabling blktap2, still no changes.

Am I missing something? Why it's using qdisk despite I explicitly set tap2?

Also, is qdisk more performant blktap2 at this point?

Thanks in advance for your reply

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