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

To: Grant McWilliams <grantmasterflash@xxxxxxxxx>
Subject: Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Wed, 17 Feb 2010 05:23:32 +0700
Cc: headhunter_unit23 <atatut@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Feb 2010 14:24:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <ed123fa31002161028w7812065fx34ed8b2a72b0811a@xxxxxxxxxxxxxx>
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: <4B62F12E.906@xxxxxxxxx> <27606273.post@xxxxxxxxxxxxxxx> <ed123fa31002161028w7812065fx34ed8b2a72b0811a@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Feb 17, 2010 at 1:28 AM, Grant McWilliams
<grantmasterflash@xxxxxxxxx> wrote:
>
>> Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
>> headhunter
>>
>
> I battled this one problem as well on CentOS 5.4 forever and my solution was
> to learn to tiptoe around and not lean too hard on it.

Really?

I don't know about other distros, but when it comes to RHEL/Centos and
Xen 3.1+/3.3/3.4, the cause is usually udev is dead. At least that
what happens to me a couple of times. I haven't find out WHY udev is
dead though, and since I haven't had it in several months I assume one
of the updates has fixed it.

Another usual cause is putting in a wrong bridge name, but that one
gives a clear error message on xend.log so it's easier to solve.

-- 
Fajar

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

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