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-users] Error: Device 0 (vif) could not be connected. Hotplug sc

To: Daniel Kao <dkao@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working. (CentOS 5.2 x86_64, Xen 3.2.1)
From: Stefan de Konink <skinkie@xxxxxxxxx>
Date: Fri, 18 Jul 2008 12:50:34 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Jul 2008 03:51:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <488073B6.7060406@xxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20080718121509.O95064-100000@xxxxxxxxxxxxx> <488073B6.7060406@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080519)
Daniel Kao schreef:
Thanks for the help! That got rid of the virbr0 interface, but I'm still having the same issue. :(

When I try to start the HVM, I see "tap0" created when I run ifconfig and added to the eth0 bridge. But still ends up with the same error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

[2008-07-18 03:34:26 6737] DEBUG (DevController:151) Waiting for devices vif.
[2008-07-18 03:34:26 6737] DEBUG (DevController:156) Waiting for 0.
[2008-07-18 03:34:26 6737] DEBUG (DevController:595) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.

What I saw specifically was the relation to a bridge name.

On a CentOS 5.1 & Xen 3.2.0 I'm running, this is what it looks like when it's working right:

I see that you have a xenbr0 and xenbr1 is this right?

To debug the problem: find the macaddress of your HVM, now try by typing:

brctl xenbr0 showmacs [yourhvmmac]
brctl xenbr1 showmacs [yourhvmmac]

To identify where the HVM is connected to. It might be that it is connected to the second bridge that might not have outside connectivity. To remove the second bridge (if required) take the same approach as for the virbr0.


Xen-users mailing list