[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

çå: [Xen-devel] some questions about the new blktap2 module



Thank you a lot for your attention . 
I got the dom0 kernel source code from xensource.com, and I don't know whether 
it's the same with  pv_ops dom0 source tree .  I'm wondering that how can 
people use VHD devices under the new blktap2 if he use SUSE11 as dom0 , whose 
kernel is 2.6.27 .  In my mind,  the new blktap2 module is developed matching 
with kernel 2.6.18 . For example, blktap2 includes lots header files from  
linux-2.6.18. Is this right ? 


 

-----éäåä-----
åää: Pasi KÃrkkÃinen [mailto:pasik@xxxxxx] 
åéæé: 2009å12æ21æ 17:17
æää: fanliang
æé: xen-devel@xxxxxxxxxxxxxxxxxxx; Jeremy Fitzhardinge
äé: Re: [Xen-devel] some questions about the new blktap2 module

On Mon, Dec 21, 2009 at 05:00:56PM +0800, fanliang wrote:
>    Hi, all:
>        I have some questions when read the code of the new blktap2 module.
>    One is  in function tapdisk_vbd_map_device ( ) . In this function , the
>    userspace proccess tapdisk2 used ioctl like this :
>         ioctl(ring->fd, BLKTAP_IOCTL_SETMODE, BLKTAP_MODE_INTERPOSE);
>    From the context , we can get that "ring->fd " is the file handle of the
>    ring-device  [/dev/xen/blktap-2/blktap[minor] ]  . In the blktap2 driver
>    codes , I find that blktap_ring_ioctl() didn't implement the
>    BLKTAP_IOCTL_SETMODE ioctl case . I used xen-unstable code package and
>    linux-2.6.18-xen-3.4.2 code package.
>    So my question is :
>    1,  Is blktap2 code in xen-unstable not match with linux-2.6.18-xen-3.4.2
>    ?
>    2,  Any body used VHD disk with blktap2 ?
> 

Hello,

Afaik blktap2 is not yet ready/working on pv_ops dom0 tree (xen-unstable uses 
pv_ops dom0).

Jeremy can possibly comment more about the status of blktap2.

-- Pasi




_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.