[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: "John Morris" <john@xxxxxxxxxxx>
  • From: "Todd Deshane" <deshantm@xxxxxxxxx>
  • Date: Sat, 20 Dec 2008 17:26:48 -0500
  • Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sat, 20 Dec 2008 14:27:54 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=uXYlOGyAu6SBvLuSnkNky50nYMdgyI5b5FbA5Z36OIHpW9Zyszm+fEKm9PaU5epbB6 /aETEWIKzamOzhBj597iGl6bwVW5Zr64qNYrOOp+jzA0/4s+z8rk8mFlyhr0rZDVs2og rUUOqRRC1cGMJrFZ69kYU+E3uxIRdmkroYvOk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Some questions/comments inline.

On Sat, Dec 20, 2008 at 2:25 PM, John Morris <john@xxxxxxxxxxx> 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.


Todd Deshane

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.