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

[Xen-devel] xen_blk driver

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen_blk driver
From: Håvard Bjerke <Havard.Bjerke@xxxxxxxxxxx>
Date: Tue, 3 May 2005 11:23:56 +0200
Delivery-date: Tue, 03 May 2005 09:23:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4i
I have some trouble understanding the interface between the blkfront and 
blkback drivers. When a dom1 is created, after xlblk_init() is called, the 
wait_for_blkif() routine waits for a connection of some kind until it times out 
with a "xen_blk: Timeout connecting to device!". Is this a connection from 
Xend, Xen or dom0 it's waiting for? How is this connection timed to occur 
exactly when wait_for_blkif() is looping?

Håvard

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

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