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] Timeout connecting to block device driver

To: Jacob Gorm Hansen <jacobg@xxxxxxx>
Subject: Re: [Xen-devel] Timeout connecting to block device driver
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 22 Aug 2005 16:43:32 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Aug 2005 15:37:08 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4309EF2C.1070508@xxxxxxx>
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>
References: <4309EF2C.1070508@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 22 Aug 2005, at 16:28, Jacob Gorm Hansen wrote:

with the latest tarball I am seeing the following error:

<6>xen_blk: Initialising virtual block device driver
<4>xen_blk: Timeout connecting to device!

I have tried all permutations of grant table and blktap drivers in
linux0 and linuxU, to no avail.

I am using vm-tools-0.1.9 and am fearing the problem could lie in there. Has the interface for registering with blkdev backends changed recently?

We switched over to xenbus/xenstore on Friday. So blk devices don't use the control interface any more.

 -- Keir


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

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