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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Timeout connecting to block device driver
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Mon, 22 Aug 2005 17:56:05 +0200
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Aug 2005 15:54:35 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <56ad92f017c42e5004d2ca6c21ae7255@xxxxxxxxxxxx>
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> <56ad92f017c42e5004d2ca6c21ae7255@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050529)
Keir Fraser wrote:

>> 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.

ok,
is there any documentation or code I can look at to figure out how to
give a domain access to a block device, using my own code or vm-tools?

thanks,
Jacob

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

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