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] can't start domU

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] can't start domU
From: "Charles Coffing" <ccoffing@xxxxxxxxxx>
Date: Fri, 11 Nov 2005 15:12:38 -0700
Delivery-date: Fri, 11 Nov 2005 22:34:26 +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
I've been getting hangs while attempting to start domUs on recent
changesets.  I get an error such as:
Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.

Yet if I run diagnose.py on the now- paused domU, I get this:
# python diagnose.py 2
Domain ID is 2.
Domain name is ExampleDomain.
Found 2 device classes in use.
Found 1 vbd devices.
Found device vbd, 769.
Backend is stuck waiting for frontend for device vbd, 769.
Device vbd, 769 hotplugging has completed successfully.
Found 0 vif devices.

Any idea why the front end would be stuck?

I'm running udev 068.


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

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