Bug 200135 - kernel-xen* is built without pci frontend
Summary: kernel-xen* is built without pci frontend
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel-xen
Version: 5
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: 188771
TreeView+ depends on / blocked
 
Reported: 2006-07-25 17:21 UTC by Jón Fairbairn
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-09-20 17:23:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jón Fairbairn 2006-07-25 17:21:13 UTC 
Description of problem:
The kernel config for kernel-xen0 (and -xenU) contains the line

# CONFIG_XEN_PCIDEV_FRONTEND is not set

so that one cannot assign pci devices to a guest domain. As far as I know,
enabling this option shouldn't cause problems...

2.6.17-1.2157_FC5

How reproducible:
static!

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jón Fairbairn 2006-07-25 18:13:37 UTC 
I should probably be referring to kernel-xen.
Same applies.
Comment 2 Stephen Tweedie 2006-09-20 17:17:37 UTC 
$ grep PCI.*FRONT kernel-2.6.18-x86_64-xen.config
CONFIG_XEN_PCIDEV_FRONTEND=y

in latest rawhide (tested and working in i686 at least.)
Comment 3 Stephen Tweedie 2006-09-20 17:23:42 UTC 
[root@rawhideU64 ~]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:13:20:F3:F8:56
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Base address:0x20e0 Memory:50200000-50220000

[root@rawhideU64 ~]# /sbin/lspci
00:00.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection

from a rawhide x86_64 domU/dom0 with pciback delegation of an e1000 NIC to domU.
Note You need to log in before you can comment on or make changes to this bug.