Re: [Xen-devel] problems with pciback on 2.6.27 with xenclient patches

[Ben Garside <ben@xxxxxxxxxxxxxxxxxx>]

Hi Jean,

Thanks very much for the reply! 

Output from xm info is as follows:
host                   : benDom0
release                : 2.6.27.19-5.1
version                : #7 SMP Mon Jun 15 16:01:44 BST 2009
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2327
hw_caps                : bfebfbff:20100800:00000000:00000140:040ce3bd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 2045
free_memory            : 127
node_to_cpu            : node0:0-3
node_to_memory         : node0:127
xen_major              : 3
xen_minor              : 5
xen_extra              : -unstable
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : Mon Jun 08 12:24:14 2009 +0100 19739:4448fae52553
cc_compiler            : gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12)
cc_compile_by          : root
cc_compile_domain      :
cc_compile_date        : Fri Jun 12 08:22:28 BST 2009
xend_config_format     : 4

2009/6/17 Jean Guyader <jean.guyader@xxxxxxxxx>

Hi Ben,

The "I/O Virtualization Enable" log message is displayed by Xen and
not by pciback in dom0.

Could you give us the output of "xm info".

Thanks,

Jean

2009/6/16 Ben Garside <ben@xxxxxxxxxxxxxxxxxx>:

> Hi, am not sure if this is the most appropriate place to post, so
> excuse me if
> it's not. I've been tearing my hair out (and there's not much left)
> trying to
> get pciback to work. I picked the xci based kernel (2.6.27 with the pq
> patches
> (using guilt) - summarised at http://xenbits.xensource.com/xenclient/)
> as it
> seems to have the best support for pciback (and ultimate goal of vga
> passthrough) for a recent kernel. Compile was ok, XEN related kernel
> parameters
> are below. When I add the iommu=1 vtd=1  pciback.permissive
> pciback.hide=(00:1b.0) to the boot args, it looks like the card is
> "seized",
> only later to be released again - no mention of I/O virtualization
> which I have
> seen in logs of a few other people. Doing an lspci in Dom0 shows the
> card as
> normal. Have tried with a few different cards (this particular pci
> device is
> onboard sound).
>
> I have tried it with xen 3.40 (release) and with unstable (currently
> 3.5). My
> machine is a Dell T5400 (xeon processor) and has all the vt-d options
> enabled in
> the bios. Oh one other thing I noticed is that if I put a spurious
> (incorrect)
> option as a boot arg, I don't get any warning that this is
> unrecognised - have
> also tried adding debug to the boot line, but it has no effect.
>
> Any help much appreciated - this is driving me crazy!
>
>
> Grub entry:
> title Xen 3.4 Kernel 2.6.27.19-5.1
> uuid 6724237b-5a56-4765-b3e0-21ce3d358ab3
> kernel /xen-3.4.gz
> module /vmlinuz-2.6.27.19-5.1  debug
> root=/dev/mapper/VolGroup0-dom0_root ro
> iommu=1 vtd=1 dom0_mem=512M pciback.permissive  pciback.hide=(00:1b.0)
> console=tty0
> module /initrd-2.6.27.19-5.1.img
>
>
> Dmesg Entries:
>
> [    0.522373] pciback: adding device ID type: 1 for 0000:00:1b.0
> [    0.522470] pciback 0000:00:00.0: probing...
> [    0.522554] pciback 0000:00:01.0: probing...
> [    0.522633] pciback 0000:00:05.0: probing...
> [    0.522713] pciback 0000:00:09.0: probing...
> [    0.522794] pciback 0000:00:10.0: probing...
> [    0.522875] pciback 0000:00:10.1: probing...
> [    0.522956] pciback 0000:00:10.2: probing...
> [    0.523037] pciback 0000:00:10.3: probing...
> [    0.523118] pciback 0000:00:10.4: probing...
> [    0.523199] pciback 0000:00:11.0: probing...
> [    0.523280] pciback 0000:00:15.0: probing...
> [    0.523361] pciback 0000:00:15.1: probing...
> [    0.523442] pciback 0000:00:16.0: probing...
> [    0.523523] pciback 0000:00:16.1: probing...
> [    0.523604] pciback 0000:00:1b.0: probing...
> [    0.523679] pciback 0000:00:1b.0: seizing device
> [    0.523755] pciback 0000:00:1b.0: pcistub_device_alloc
> [    0.523832] pciback 0000:00:1b.0: deferring initialization
> [    0.523915] pciback 0000:00:1c.0: probing...
> [    0.524067] pciback 0000:00:1d.0: probing...
> [    0.524149] pciback 0000:00:1d.1: probing...
>
> ...
> [    0.896278] pciback: pcistub_init_devices_late
> [    0.896356] pciback 0000:00:1b.0: initializing...
> [    0.896433] pciback 0000:00:1b.0: pcistub_dev_data_alloc
> [    0.896511] pciback 0000:00:1b.0: initializing config
> [    0.896586] pciback 0000:00:1b.0: initializing virtual
> configuration space
> [    0.896666] pciback 0000:00:1b.0: added config field at offset 0x04
> [    0.896741] pciback 0000:00:1b.0: added config field at offset 0x3c
> [    0.896817] pciback 0000:00:1b.0: added config field at offset 0x3d
> [    0.896893] pciback 0000:00:1b.0: added config field at offset 0x0c
> [    0.896969] pciback 0000:00:1b.0: added config field at offset 0x0d
> [    0.897044] pciback 0000:00:1b.0: added config field at offset 0x0f
> [    0.897134] pciback 0000:00:1b.0: added config field at offset 0x10
> [    0.897222] pciback 0000:00:1b.0: added config field at offset 0x14
> [    0.897306] pciback 0000:00:1b.0: added config field at offset 0x18
> [    0.897389] pciback 0000:00:1b.0: added config field at offset 0x1c
> [    0.897472] pciback 0000:00:1b.0: added config field at offset 0x20
> [    0.897556] pciback 0000:00:1b.0: added config field at offset 0x24
> [    0.897639] pciback 0000:00:1b.0: added config field at offset 0x30
> [    0.897736] pciback 0000:00:1b.0: Found capability 0x1 at 0x50
> [    0.897812] pciback 0000:00:1b.0: added config field at offset 0x50
> [    0.897888] pciback 0000:00:1b.0: added config field at offset 0x52
> [    0.897966] pciback 0000:00:1b.0: added config field at offset 0x54
> [    0.898052] pciback 0000:00:1b.0: added config field at offset 0x56
> [    0.898128] pciback 0000:00:1b.0: added config field at offset 0x57
> [    0.898204] pciback 0000:00:1b.0: enabling device
> [    0.898290] pciback 0000:00:1b.0: reset device
> [    0.932248] serio: i8042 KBD port at 0x60,0x64 irq 1
> [    0.932353] serio: i8042 AUX port at 0x60,0x64 irq 12
> [    0.948131] mice: PS/2 mouse device common for all mice
>
>
>
>
> 2.6.27 with patches compile args:
> # CONFIG_X86_XEN is not set
> CONFIG_X86_64_XEN=y
> CONFIG_X86_XEN_GENAPIC=y
> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_PCIDEV_FE_DEBUG=y
> # CONFIG_INPUT_XEN is not set
> # CONFIG_TCG_XEN is not set
> CONFIG_XEN=y
> CONFIG_XEN_INTERFACE_VERSION=0x00030207
> # XEN
> CONFIG_XEN_PRIVILEGED_GUEST=y
> # CONFIG_XEN_UNPRIVILEGED_GUEST is not set
> CONFIG_XEN_PRIVCMD=y
> CONFIG_XEN_XENBUS_DEV=y
> CONFIG_XEN_NETDEV_ACCEL_SFC_UTIL=m
> CONFIG_XEN_BACKEND=y
> CONFIG_XEN_BLKDEV_BACKEND=y
> CONFIG_XEN_BLKDEV_TAP=y
> CONFIG_XEN_NETDEV_BACKEND=y
> # CONFIG_XEN_NETDEV_PIPELINED_TRANSMITTER is not set
> CONFIG_XEN_NETDEV_LOOPBACK=m
> CONFIG_XEN_PCIDEV_BACKEND=y
> CONFIG_XEN_PCIDEV_BACKEND_VPCI=y
> # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set
> # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set
> # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set
> CONFIG_XEN_PCIDEV_BE_DEBUG=y
> CONFIG_XEN_TPMDEV_BACKEND=y
> CONFIG_XEN_SCSI_BACKEND=m
> CONFIG_XEN_BLKDEV_FRONTEND=y
> CONFIG_XEN_NETDEV_FRONTEND=y
> CONFIG_XEN_NETDEV_ACCEL_SFC_FRONTEND=m
> CONFIG_XEN_SCSI_FRONTEND=m
> CONFIG_XEN_GRANT_DEV=y
> CONFIG_XEN_FRAMEBUFFER=y
> CONFIG_XEN_KEYBOARD=y
> CONFIG_XEN_DISABLE_SERIAL=y
> CONFIG_XEN_SYSFS=y
> CONFIG_XEN_NR_GUEST_DEVICES=256
> # CONFIG_XEN_COMPAT_030002_AND_LATER is not set
> # CONFIG_XEN_COMPAT_030004_AND_LATER is not set
> # CONFIG_XEN_COMPAT_030100_AND_LATER is not set
> # CONFIG_XEN_COMPAT_030200_AND_LATER is not set
> CONFIG_XEN_COMPAT_LATEST_ONLY=y
> CONFIG_XEN_COMPAT=0xffffff
> CONFIG_XEN_SMPBOOT=y
> CONFIG_XEN_DEVMEM=y
> CONFIG_XEN_BALLOON=y
> CONFIG_XEN_SCRUB_PAGES=y
>

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>

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