Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] [PATCH] Add a mechanism to detect block device setup failure

To: xen-devel@xxxxxxxxxxxxxxxxxxx, aliguori@xxxxxxxxxx
Subject: [Xen-devel] [PATCH] Add a mechanism to detect block device setup failure
From: Murillo Fernandes Bernardes <mfb@xxxxxxxxxx>
Date: Fri, 28 Oct 2005 16:42:10 -0200
Delivery-date: Sat, 29 Oct 2005 07:59:02 +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>
Organization: IBM
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
Hi

The problem is: There is no mechanism to detect block device setup failure

Network devices have the same problem, and are fixed with this too.

I handling this problem in the way suggested by aliguori: 
- hotplug scripts write a "hotplug-status" node on store
- Xend DevController.createDevice() check verify this node and return success 
or throw an exception on failure. 
- If no changes in "hotplug-status" node after DEVICE_CREATE_TIMEOUT seconds 
Xend throw an exception showing the problem with hotplug scripts.

Comments?

Regards

-- 
Murillo Fernandes Bernardes

Attachment: DevController_device_create_check.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>