Xen users - Jul 2008 - "XENBUS: Device with no driver" errors on Debian

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

Thanks

Ben

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

I have fixed the console by adding hvc0 to inittab, but still no luck  
with the PCI. Both errors still show in dmesg.

Ben

On 14 Jul 2008, at 14:43, Ben Firshman wrote:
> 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
>
> Thanks
>
> Ben
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

I understand these kernel versions use paravirt_ops or something. Does  
this mean there is no PCI passthrough support? Can these kernels even  
run with a 2.6.18 dom0? I have tried upgrading to 2.6.25-2 with no luck.

Can someone fill me in? I can''t find any documentation about it  
anywhere. The debian package descriptions even fail to mention which  
kernels will and won''t work as a dom0 - it''s a matter of trial
and
error for new users it seems!

Ben

On 15 Jul 2008, at 18:05, Ben Firshman wrote:
> I have fixed the console by adding hvc0 to inittab, but still no  
> luck with the PCI. Both errors still show in dmesg.
>
> Ben
>
> On 14 Jul 2008, at 14:43, Ben Firshman wrote:
>
>> 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
>>
>> Thanks
>>
>> Ben
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

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

On Tuesday 15 July 2008, Ben Firshman wrote:
> I understand these kernel versions use paravirt_ops or something. Does
> this mean there is no PCI passthrough support? Can these kernels even
> run with a 2.6.18 dom0? I have tried upgrading to 2.6.25-2 with no luck.
You don''t need a matching domU and dom0 kernel, so the kernel should
work.

The paravirt_ops kernel doesn''t supported PCI passthrough currently; it
only
supports unprivileged domU functionality.  If it''s a paravirt_ops
kernel
you''re using then you can''t pass a PCI device to it.

You really need a dom0-capable kernel to successfully control a PCI device.  
Is there any reason not to just use the same kernel as dom0?  Is it a driver 
support issue?
> Can someone fill me in? I can''t find any documentation about it
> anywhere. The debian package descriptions even fail to mention which
> kernels will and won''t work as a dom0 - it''s a matter of
trial and
> error for new users it seems!
That''s a bit unfortunate.  You basically need something that is capable
of
being a dom0 in order to accept a PCI passthrough.  If the domU''s
kernel is
paravirt_ops then it doesn''t meet this requirement.

Does the description given by apt-cache show <pkgname> mention anything
about
whether something is paravirt_ops or not?

Cheers,
Mark
>
> Ben
>
> On 15 Jul 2008, at 18:05, Ben Firshman wrote:
> > I have fixed the console by adding hvc0 to inittab, but still no
> > luck with the PCI. Both errors still show in dmesg.
> >
> > Ben
> >
> > On 14 Jul 2008, at 14:43, Ben Firshman wrote:
> >> 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
> >>
> >> Thanks
> >>
> >> Ben
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@lists.xensource.com
> >> http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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

On 16 Jul 2008, at 22:35, Mark Williamson wrote:
> On Tuesday 15 July 2008, Ben Firshman wrote:
>> I understand these kernel versions use paravirt_ops or something.  
>> Does
>> this mean there is no PCI passthrough support? Can these kernels even
>> run with a 2.6.18 dom0? I have tried upgrading to 2.6.25-2 with no  
>> luck.
>
> You don''t need a matching domU and dom0 kernel, so the kernel
should
> work.
>
> The paravirt_ops kernel doesn''t supported PCI passthrough
currently;
> it only
> supports unprivileged domU functionality.  If it''s a paravirt_ops
> kernel
> you''re using then you can''t pass a PCI device to it.
That explains it! I was running a 2.6.24 dom0 and domU on Ubuntu with  
PCI passthrough working great, so I guess that wasn''t pv_ops.  
Unfortunately, it was incredibly unstable, and I couldn''t get it to  
run for more than a few days without kernel panics. I have a feeling  
it wasn''t just my configuration - they managed to break the networking
in their Xen packages during their 8.04 release and for weeks after,  
so I don''t have great deal of trust in their packages. Is anyone else  
running Xen on Ubuntu''s 2.6.24 packages?
>
> You really need a dom0-capable kernel to successfully control a PCI  
> device.
> Is there any reason not to just use the same kernel as dom0?  Is it  
> a driver
> support issue?
Yeah, the TV card drivers I need for MythTV don''t compile on 2.6.18. I
might try running the Ubuntu 2.6.24 kernel as a domU on the Debian  
2.6.18 dom0, but it didn''t work last time I tried IIRC.

Is there any stable way of running a recent kernel with PCI  
passthrough? I''m not really bothered about the dom0 distribution, but  
I''d like the domUs to be debian.
>
>
>> Can someone fill me in? I can''t find any documentation about
it
>> anywhere. The debian package descriptions even fail to mention which
>> kernels will and won''t work as a dom0 - it''s a matter
of trial and
>> error for new users it seems!
>
> That''s a bit unfortunate.  You basically need something that is  
> capable of
> being a dom0 in order to accept a PCI passthrough.  If the domU''s
> kernel is
> paravirt_ops then it doesn''t meet this requirement.
>
> Does the description given by apt-cache show <pkgname> mention  
> anything about
> whether something is paravirt_ops or not?
  linux-image-2.6.18-6-xen-686:
  This package provides the binary image for Linux kernel 2.6.18 on  
i686 and
  compatible machines.

linux-image-2.6.25-2-xen-686:
  This package provides the binary image for Linux kernel 2.6.25 on  
i686 and
  compatible machines.

No documentation is included with the packages either and their wiki  
is vague and out of date. I''ll try and clean up their wiki page for  
future users if I can.

Thanks for the help!

Ben


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

On 16 Jul 2008, at 23:01, Ben Firshman wrote:
>
>
> No documentation is included with the packages either and their wiki  
> is vague and out of date. I''ll try and clean up their wiki page
for
> future users if I can.
http://wiki.debian.org/Xen

Hopefully the the etch and lenny sections are clearer now. I''m not  
expert, so please emend it if it is incorrect.

Ben

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

I am using an Ubuntu Hardy domU (2.6.24-16-xen) with a Centos 5.1 kernel
(2.6.18-xen_3.1.0).  There was a networking problem with the 8.04 release
but  this site:

 http://www.il.is.s.u-tokyo.ac.jp/~hiranotaka/

has fixed kernel debs.

I use it for mythTV backend.  It is stable, just has a ton of dma timeouts.
I have another domU for comflagging only running Ubuntu as well and I get
kernel crashes here and there , something about stuck in cpu0 for 11s.

I am hoping there is a newer xen kernel that I could use for my mythbackend
but I guess, 2.6.24 is the latest that I could use.

Chris


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