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/
Home Products Support Community News


[Xen-devel] Not waiting for devices in xend when resuming a domain

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Not waiting for devices in xend when resuming a domain
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Sat, 23 Sep 2006 12:31:23 -0400
Delivery-date: Sat, 23 Sep 2006 09:31:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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


I noticed that if a domain is resumed it is NOT being waited for the hotplug scripts to finish running (call to waitForDevices in xend) , like this is for example done when a domain is starting. If I put a lot of load on domain-0 by for example compiling the sources with multiple threads (make -j 16) and do a resume on a domain, this can lead to access to devices although they are not properly connected, yet. I think it's even more critical to have immediate and guaranteed access to all devices when a domain is immediately available (resume) and if it wants to access a device instead of it the case when it might be busy spending some time booting.

-- Stefan
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>