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


Re: [Xen-devel] Error: Device 0 (vif) could not be connected. (Xen 3.0.1

To: Philippe Berthault <Philippe.Berthault@xxxxxxxx>
Subject: Re: [Xen-devel] Error: Device 0 (vif) could not be connected. (Xen 3.0.1 regression)
From: Rob Gardner <rob.gardner@xxxxxx>
Date: Wed, 08 Feb 2006 10:36:11 -0700
Cc: Xen-Devel <Xen-Devel@xxxxxxxxxxxxxxxxxxx>, Xen-Users <Xen-Users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 08 Feb 2006 17:47:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43E8C659.9070704@xxxxxxxx>
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: <43E8C659.9070704@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Philippe Berthault wrote:

But with the latest Xen release 3.0.1, the Knoppix boot in a user domain
fails with the following message :
Error: Device 0 (vif) could not be connected. Backend device not found.

I ran into a very similar sounding problem recently. It turned out that the xen tools could not find the bridge utilities. The latest version of brctl that I had installed got put into a a directory that wasn't in xm's path. So I just copied 'brctl' into /usr/local/sbin or something like that. Not sure if your problem is the same, but it's worth checking.

Rob Gardner

Xen-devel mailing list

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