thr3ads.net - Xen users - [Xen-users] pciback/front in Fedora 10 domU: should this work? [Dec 2008]

If this information is useful, please help other people find it:
Share via:

John Morris

2008-Dec-20 19:25 UTC

[Xen-users] pciback/front in Fedora 10 domU: should this work?

I''d hoped to play with the new wireless architecture in recent kernels,
and so have (successfully) jumped through all sorts of hoops to get a 
F-10 domU running on a CentOS 5.2 dom0.  However, there''s some trouble 
getting the PCI wireless card passed into the domU.

The wireless device is bound to the dom0''s pciback driver correctly,
and
the ''pci'' option is set in the domU''s xen config in
the same manner as
the other CentOS domU guests in the box that have PCI devices assigned 
to them.  In fact, the same card can be passed to another CentOS domU 
and be seen with lspci.  However, lspci in the Fedora 10 domU returns 
nothing at all.

Is pcifront perhaps disabled in the stock Fedora 10 kernel?  What can I 
check to get more information?

Back to the original goal, is anyone aware of a quick way to get a domU 
up and running with a >=2.6.25 kernel (with the new wireless 
architecture) that has pcifront functionality?

Thanks-

	John


This in the xend.log (with formatting):

[2008-12-21 02:05:52 3174] DEBUG (DevController:120) DevController:
writing {
	''domain'': ''alfred'',
	''frontend'':
''/local/domain/12/device/pci/0'',
	''uuid'':
''9bdcb3c8-0c30-dc23-26b9-2f6935f09d45'',
	''dev-0'': ''0000:01:06.00'',
	''state'': ''1'',
	''online'': ''1'',
	''frontend-id'': ''12'',
	''num_devs'': ''1''
	} to /local/domain/0/backend/pci/12/0.

This in /var/log/messages:

Dec 21 02:05:48 shangri-la kernel: ACPI: PCI interrupt for device 
0000:01:06.0 disabled
Dec 21 02:05:52 shangri-la kernel: pciback: vpci: 0000:01:06.0: assign 
to virtual slot 0


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

Todd Deshane

2008-Dec-20 22:26 UTC

head link

Re: [Xen-users] pciback/front in Fedora 10 domU: should this work?

Some questions/comments inline.

On Sat, Dec 20, 2008 at 2:25 PM, John Morris <john@zultron.com>
wrote:> I''d hoped to play with the new wireless architecture in recent
kernels, and
> so have (successfully) jumped through all sorts of hoops to get a F-10 domU
> running on a CentOS 5.2 dom0.  However, there''s some trouble
getting the PCI
> wireless card passed into the domU.
>
> The wireless device is bound to the dom0''s pciback driver
correctly, and the
> ''pci'' option is set in the domU''s xen config in
the same manner as the other
> CentOS domU guests in the box that have PCI devices assigned to them.  In
> fact, the same card can be passed to another CentOS domU and be seen with
> lspci.  However, lspci in the Fedora 10 domU returns nothing at all.
>
> Is pcifront perhaps disabled in the stock Fedora 10 kernel?  What can I
> check to get more information?
>
Compare the kernel configs for the Fedora and Centos domUs

> Back to the original goal, is anyone aware of a quick way to get a domU up
> and running with a >=2.6.25 kernel (with the new wireless architecture)
that
> has pcifront functionality?
>
Have you tried enabling the Xen options, in a kernel.org kernel?
You can base your config on the fedora10 domU''s kernel even.
> Thanks-
>
>        John
>
>
> This in the xend.log (with formatting):
>
> [2008-12-21 02:05:52 3174] DEBUG (DevController:120) DevController:
> writing {
>        ''domain'': ''alfred'',
>        ''frontend'':
''/local/domain/12/device/pci/0'',
>        ''uuid'':
''9bdcb3c8-0c30-dc23-26b9-2f6935f09d45'',
>        ''dev-0'': ''0000:01:06.00'',
>        ''state'': ''1'',
>        ''online'': ''1'',
>        ''frontend-id'': ''12'',
>        ''num_devs'': ''1''
>        } to /local/domain/0/backend/pci/12/0.
>
> This in /var/log/messages:
>
> Dec 21 02:05:48 shangri-la kernel: ACPI: PCI interrupt for device
> 0000:01:06.0 disabled
> Dec 21 02:05:52 shangri-la kernel: pciback: vpci: 0000:01:06.0: assign to
> virtual slot 0
>
So this shows pciback getting the device, could the problem be in the hand-off?
Is it the same Xen version?

Or if the guest is supposed to be seeing it, does it have the driver support?
It would need the driver for the device as well as PCI support.


Cheers,
Todd

-- 
Todd Deshane
http://todddeshane.net
http://runningxen.com

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

John Morris

2008-Dec-21 06:25 UTC

head link

Re: [Xen-users] pciback/front in Fedora 10 domU: should this work?

Todd,
>> Is pcifront perhaps disabled in the stock Fedora 10 kernel?  What can I
>> check to get more information?
>>
> 
> Compare the kernel configs for the Fedora and Centos domUs
A little investigation shows that the CentOS 2.6.18 kernel RPM has a 
separate patch that adds Xen capability, as well as a config option 
CONFIG_XEN_PCIDEV_FRONTEND.

The Fedora 2.6.27 kernel, however, is the new paravirt_ops kernel that 
doesn''t need a separate Xen patch (if I understand correctly). 
However,
the Xen-related config options in this kernel are much more limited, and 
there is nothing about passing PCI devices.
>> Back to the original goal, is anyone aware of a quick way to get a domU
up
>> and running with a >=2.6.25 kernel (with the new wireless
architecture) that
>> has pcifront functionality?
>>
> 
> Have you tried enabling the Xen options, in a kernel.org kernel?
> You can base your config on the fedora10 domU''s kernel even.
I haven''t tried this yet, and may do so for a proof-of-concept. 
However, I forgot to state another condition, the final solution needs 
to be in RPM form.

One more relevant fact:  the latest Xen-ified kernel source on xen.org 
is a 2.6.18 kernel.

What this is all starting to look like is, the last Xen kernel that 
supported pcifront was the last one with the separate Xen patch, that 
is, 2.6.18.  Xen-capable kernels after this seem to be the new pvops 
kernels which don''t have pcifront capability.  Since the new wireless 
architecture was only released in more recent kernels, it looks like I 
won''t be able to achieve this goal.  Does this sound right? 
I''d be very
happy if anyone would show me I''m wrong.  ;)

Thanks-

	John

By the way,

 > [...]> Or if the guest is supposed to be seeing it, does it have the driver
support?
> It would need the driver for the device as well as PCI support.
The guest shouldn''t need a driver for the device to be listed on the
PCI
bus using ''lspci''.


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

Pasi Kärkkäinen

2008-Dec-21 12:43 UTC

head link

Re: [Xen-users] pciback/front in Fedora 10 domU: should this work?

On Sun, Dec 21, 2008 at 02:25:39PM +0800, John Morris
wrote:> Todd,
> 
> >>Is pcifront perhaps disabled in the stock Fedora 10 kernel?  What
can I
> >>check to get more information?
> >>
> >
> >Compare the kernel configs for the Fedora and Centos domUs
> 
> A little investigation shows that the CentOS 2.6.18 kernel RPM has a 
> separate patch that adds Xen capability, as well as a config option 
> CONFIG_XEN_PCIDEV_FRONTEND.
> 
> The Fedora 2.6.27 kernel, however, is the new paravirt_ops kernel that 
> doesn''t need a separate Xen patch (if I understand correctly). 
However,
> the Xen-related config options in this kernel are much more limited, and 
> there is nothing about passing PCI devices.
> 
> >>Back to the original goal, is anyone aware of a quick way to get a
domU up
> >>and running with a >=2.6.25 kernel (with the new wireless
architecture)
> >>that
> >>has pcifront functionality?
> >>
> >
> >Have you tried enabling the Xen options, in a kernel.org kernel?
> >You can base your config on the fedora10 domU''s kernel even.
> 
> I haven''t tried this yet, and may do so for a proof-of-concept. 
> However, I forgot to state another condition, the final solution needs 
> to be in RPM form.
> 
> One more relevant fact:  the latest Xen-ified kernel source on xen.org 
> is a 2.6.18 kernel.
> 
> What this is all starting to look like is, the last Xen kernel that 
> supported pcifront was the last one with the separate Xen patch, that 
> is, 2.6.18.  Xen-capable kernels after this seem to be the new pvops 
> kernels which don''t have pcifront capability.  Since the new
wireless
> architecture was only released in more recent kernels, it looks like I 
> won''t be able to achieve this goal.  Does this sound right? 
I''d be very
> happy if anyone would show me I''m wrong.  ;)
> 
pv_ops Xen support in upstream/vanilla Linux kernels is a work in progress..
currently dom0 support is being worked on and it should be included in
upcoming Linux 2.6.29.

See: http://wiki.xensource.com/xenwiki/XenParavirtOps

There''s also a temporary ''stop-gap'' Linux 2.6.27
based tree, with the
Xenlinux patches from Novell/SLES (forward-ported from Xensource Xenlinux
2.6.18).

http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg

That temporary 2.6.27 tree should have ''all'' the features.. 

http://www.nabble.com/Linux-2.6.27-temporary-tree-on-xenbits-td20620606.html

-- Pasi

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

Xen users - Dec 2008 - pciback/front in Fedora 10 domU: should this work?

[Xen-users] pciback/front in Fedora 10 domU: should this work?

Re: [Xen-users] pciback/front in Fedora 10 domU: should this work?

Re: [Xen-users] pciback/front in Fedora 10 domU: should this work?

Re: [Xen-users] pciback/front in Fedora 10 domU: should this work?