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: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
From: headhunter_unit23 <atatut@xxxxxxxxx>
Date: Tue, 16 Feb 2010 02:33:04 -0800 (PST)
Delivery-date: Tue, 16 Feb 2010 02:34:30 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B62F12E.906@xxxxxxxxx>
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Olivier,

I had this problem with Xen 2.6.18-r12 on Gentoo 2.6.31-r6 with udev 146-r1

xm create /PATH/TO/MY/VM/CONF 

gives after a while: 

Error: Device 0 (vif) could not be connected. Hotplug scripts not working. 

I had to package.mask the gentoo kernel and udev latest versions and force
gentoo to install the following versions:

- linux-2.6.29-gentoo-r5
- udev-141

before I compile the xen kernel 2.6.18-r12

I found no other solutions than the above; kernel and udev downgrade, which
forced me to reinstall the whole server.

The first install with Gentoo 2.6.31-r6 with udev 146-r1 versions gave me:

* Mounting proc at /proc 
* Mounting sysfs at /sys 
* Your kernel is too old to work with this version of udev. 
* Current udev only supports Linux kernel 2.6.25 and newer. 

at boot time and that's what gave me the hint to downgrade the kernel and
udev versions.

If you don't need anything inside the latest kernel, then I suggest you
downgrade your kernel and go back to the "working" kernel version.

Hope this helps,

Cheers,

headhunter


Olivier B.-2 wrote:
> 
> Hi,
> 
> I tried to upgrade my dom0 kernel from 2.6.31.6-dae-dom0-00751-g60e0545 
> to 2.6.31.6-dae-dom0-00757-ge65323d ; and domU doesn't start anymore.
> 
> I obtain this error message :
>  > root! noburo:/var/log/xen# time xm create /etc/xen/hel.cfg
>  > Using config file "/etc/xen/hel.cfg".
>  > Error: Device 0 (vif) could not be connected. Hotplug scripts not 
> working.
>  >
>  > real    1m41.491s
>  > user    0m0.116s
>  > sys    0m0.056s
> 
> And the error is triggered after 100 seconds...
> 
> I use Xen 3.4.2 (Debian amd64) in bridge mode, and a 2.6.31.12 vanilla 
> pv_ops kernel.
> 
> In xen-hotplug.log I have only this line : Nothing to flush.
> 
> And in xend.log I found that :
> [2010-01-29 15:26:12 6213] DEBUG (DevController:139) Waiting for devices 
> vif.
> [2010-01-29 15:26:12 6213] DEBUG (DevController:144) Waiting for 0.
> [2010-01-29 15:26:12 6213] DEBUG (DevController:629) 
> hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status.
> [2010-01-29 15:27:52 6213] DEBUG (XendDomainInfo:2732) 
> XendDomainInfo.destroy: domid=5
> 
> 
> 
> Is there a bug in last pv_ops dom0 kernel, or have I something to fix in 
> my setup ?
> 
> Olivier
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Error%3A-Device-0-%28vif%29-could-not-be-connected.-Hotplug-scripts-not-working.-tp27372757p27606273.html
Sent from the Xen - User mailing list archive at Nabble.com.


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

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