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] XENBUS: Device with no driver

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XENBUS: Device with no driver
From: Steve Brueckner <steve@xxxxxxxxxxxxxx>
Date: Wed, 2 Aug 2006 15:56:25 -0400
Delivery-date: Wed, 02 Aug 2006 12:57:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
After upgrading to xen-unstable from a month-old version of xen-testing, I
am now getting the following errors when trying to create a paravirtualized
guest with both file-backed and LVM-backed VBDs (this config and guest image
used to work fine):

XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vif/0

...and things get worse from there.  Does anyone know what this means?  Or
what's causing it?  Or how I can fix it?

Thanks,

Steve Brueckner, ATC-NY

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] XENBUS: Device with no driver, Steve Brueckner <=