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

Re: [Xen-users] (domU) Device 0 (vif) could not be connected. Hotplug sc

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] (domU) Device 0 (vif) could not be connected. Hotplug scripts not working.
From: CJ van den Berg <cj@xxxxxxxxxxxxx>
Date: Mon, 30 Jan 2006 13:19:05 +0100
Delivery-date: Mon, 30 Jan 2006 12:28:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BAY107-F12C5B3568D733323408D89D1090@xxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: xen-users@xxxxxxxxxxxxxxxxxxx
References: <BAY107-F12C5B3568D733323408D89D1090@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11
On Mon, Jan 30, 2006 at 12:58:36PM +0100, BugOne S wrote:
> Hi, i cant run domU, because of this error:
> 
> xen xen # xm create -c client1
> Using config file "client1".
> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

I have this problem too. In my case it seems to be the very short timeout
for starting backend devices. Basically, AFAICT, all vif- scripts must
finish within 10 seconds or the xm create command is aborted.

In my case I do a lot of dynamic configuration in vif-nat and it often takes
much longer than 10 seconds, especially if I'm running a kernel build or
something in the background.

You can see if this is the same problem you're having by changing the
timeout DEVICE_CREATE_TIMEOUT in
/usr/lib/python/xen/xend/server/DevController.py (probably around line 28)
to something larger than 10.

-- 
CJ van den Berg

mailto:cj@xxxxxxxxxxxxx
  xmpp:cj@xxxxxxxxxxxxx
   sip:8918316@xxxxxxxxxx

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

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