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


[Xen-users] "XENBUS: Device with no driver" errors on Debian

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] "XENBUS: Device with no driver" errors on Debian
From: Ben Firshman <ben@xxxxxxxxxxxxxx>
Date: Mon, 14 Jul 2008 14:43:08 +0100
Delivery-date: Mon, 14 Jul 2008 06:44:21 -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
I am running debian lenny, with the standard Xen 3.2 packages, with the 2.6.18-6-xen-686 kernel as dom0, and 2.6.24-1-xen-686 as domU. Everything is working fine apart from the console and the PCI passthrough. I am getting these errors in the domU on startup:

XENBUS: Device with no driver: device/pci/0
XENBUS: Device with no driver: device/console/0

Does this mean the modules are missing? I have the linux- modules-2.6.24-1-xen-686 package installed in the domU, I can't understand what could be wrong. Do they need to built into the kernel or something?

pciback is working fine on the dom0:

pciback 0000:04:00.0: seizing device
pciback 0000:01:00.0: seizing device
pciback 0000:01:00.1: seizing device
pciback 0000:01:00.2: seizing device
pciback 0000:01:01.0: seizing device
pciback 0000:01:02.0: seizing device



Xen-users mailing list