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

[Xen-users] Upgrade to xen 4 Error: Device 0 (vif) could not be connecte

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Upgrade to xen 4 Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
From: Ralf Hornik Mailings <ralf@xxxxxxxxxxxxxxxxx>
Date: Sat, 15 May 2010 21:13:21 +0200
Delivery-date: Sat, 15 May 2010 12:13:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (Windows/20100228)
Dear list,

I'm running Debian Lenny with xen build from source completely.
After upgrading xen to 4 with 2.6.32.12 kernel any paravirtualized domU hangs and after some minutes it breaks with:

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

There isn't any log entry regarding this error.

When I switch back to 3.4.2 with 2.6.18 kernel anything boots fine.
Any Ideas?
Thank you and best regards

Ralf



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Upgrade to xen 4 Error: Device 0 (vif) could not be connected. Hotplug scripts not working., Ralf Hornik Mailings <=