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

To: Charles Coffing <ccoffing@xxxxxxxxxx>
Subject: Re: [Xen-devel] can't start domU
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Fri, 11 Nov 2005 14:44:42 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 11 Nov 2005 22:44:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4374B47B.D169.003C.0@xxxxxxxxxx>
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: <4374B47B.D169.003C.0@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
Charles Coffing wrote:
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.

All of these are failures to create the vif devices.
Please check /var/log/messages, xend-debug.log, etc.
You can put a set -x in your /etc/xen/vif-bridge (or equivalent)
script for more verbose detail.

Also, check to see that your install went successfully.

From previous debugging over the past week, most of
these cases were the lack of brctl (or execute perms
for root), or the lack of other utilities (make install
should catch these).

thanks,
Nivedita

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

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