WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] xm block-attach DomID tap:aio:/...

To: "Wayne Gong" <wayne.gong@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] xm block-attach DomID tap:aio:/...
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 27 Dec 2008 13:05:43 +1100
Cc:
Delivery-date: Fri, 26 Dec 2008 18:06:20 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4954BA1D.7070400@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4954BA1D.7070400@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclnSckPH2BrUjd5T3eVj9eYPR5INwAfbxqA
Thread-topic: [Xen-devel] xm block-attach DomID tap:aio:/...
> Hi folks,
> 
> I meet a problem when developing windows PV drivers for Xen. Now my
> drivers can support adding a 'file' type backend media as a VBD device
> using 'xm block-attach' command. With the same code, 'xm block-attach'
a
> 'tap:aio' type backend media cannot works fine on my PV drivers. But
if
> I add a 'file' type backend media to windows VM and set set it to
> 'tap:aio' type, it works fine. Since my driver didn't get WHQL digital
> signature, when adding a new device VM, windows will pops up a 'Find
new
> hardware' dialog to install drivers for it even there is a device
object
> represents for it. When installing driver for new storage class
device,
> windows PnP manager will remove the device object and add a new one
> represents for the new device. In this progress, I will set device
> backend state to XenbusStateClosing->XenbusStateClosed
> ->XenbusStateInitWait and then reinitialize the device. If it's a
'file'
> type, all these progress works fine, but it's a 'type:aio' type, my
> drivers cannot get any response from ring buffer for Read/Write scsi
> command.
> 
> So does anybody can give me some brief guide on difference between
> 'file' type and 'tap:aio' type as a backend media for a frontend PV
> drivers? And I want to confirm that a 'tap:aio' type backend can work
> well when backend state changed as
> XenbusStateInitWait->XenbusStateConnected->
> XenbusStateClosing->XenbusStateClosed
> ->XenbusStateInitWait->XenbusStateConnected. I know that a 'file' type
> backend is Yes, I think 'tap:aio' type is Yes either, just want to
> conform.
> 
> James, any suggestion?
> 
> BTW, I use OVM 2.1.2 based on Xen 3.1 series.
> 

I have tried tap:aio before and also had no success, but I haven't
looked into why. If you do find out then please let me know.

Thanks

James

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

<Prev in Thread] Current Thread [Next in Thread>