Xen devel - Feb 2010 - pciback doesn''t seize device, but no error either.

Hi Konrad,

I''m trying to passthrough a secondary gfx device(intel IGD) (with
patches from Han Weidong).
Intel VT-D is enabled, pciback + pciback debug compiled in.
But some how pciback refuses to seize the device, but i don''t see an
error either.

Attached:
- xm info
- xm dmesg
- dmesg
- lspci -vvvknn

Any ideas on what it might be ?

-- 
Best regards,
 Sander                          mailto:linux@eikelenboom.it




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

Hi Konrad,

Sorry for the noise, forgot to fixup my grub lines to the new
''xen-pciback.hide'' instead of
''pciback.hide''.
Pretty stupid because i encountered it early ..

--
Sander
> Hi Konrad,
> I''m trying to passthrough a secondary gfx device(intel IGD) (with
patches from Han Weidong).
> Intel VT-D is enabled, pciback + pciback debug compiled in.
> But some how pciback refuses to seize the device, but i don''t see
an error either.
> Attached:
> - xm info
> - xm dmesg
> - dmesg
> - lspci -vvvknn
> Any ideas on what it might be ?



-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it


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

Hi,
> Any ideas on what it might be ?
dmesg says:
> Unknown boot option `pciback.hide=(0000:00:02.0)(0000:00:02.1)'':
ignoring
is your pciback.ko module in your initrd and/or loaded during boot? I
needed it in order to dismiss this error message.

Hth,
Ervin

On Sun, Feb 14, 2010 at 1:45 PM, Sander Eikelenboom
<linux@eikelenboom.it> wrote:

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

Ok, I just saw your other email... :)

ervin

On Sun, Feb 14, 2010 at 3:41 PM, Ervin Novak <enovak@opensuse.hu>
wrote:
> Hi,
>
>> Any ideas on what it might be ?
>
> dmesg says:
>> Unknown boot option
`pciback.hide=(0000:00:02.0)(0000:00:02.1)'': ignoring
>
> is your pciback.ko module in your initrd and/or loaded during boot? I
> needed it in order to dismiss this error message.
>
> Hth,
> Ervin
>
> On Sun, Feb 14, 2010 at 1:45 PM, Sander Eikelenboom
> <linux@eikelenboom.it> wrote:
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Sun, Feb 14, 2010 at 01:45:38PM +0100, Sander Eikelenboom
wrote:
> Hi Konrad,
> 
> I''m trying to passthrough a secondary gfx device(intel IGD) (with
patches from Han Weidong).
> Intel VT-D is enabled, pciback + pciback debug compiled in.
> But some how pciback refuses to seize the device, but i don''t see
an error either.
> 
> Attached:
> - xm info
> - xm dmesg
> - dmesg
> - lspci -vvvknn
> 
> Any ideas on what it might be ?
> 
> -- 
> Best regards,
>  Sander                          mailto:linux@eikelenboom.it
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Linux version 2.6.31.6 (root@xentest) (gcc version 4.3.2
(Debian 4.3.2-1.1) ) #2 SMP Sun Feb 14 05:18:49 CET 2010
> [    0.000000] Command line: root=/dev/sda1 ro earlyprintk=xen
pciback.hide=(0000:00:02.0)(0000:00:02.1) reassigndev=0000:00:02.0,0000:00:02.1
reassign_resources
It is called ''xen-pciback'' now. Try that instead of
''pciback''.

Also, ''reassigneddev'' and
''reassign_resources'' are no more in the upstream
kernels. It is one single option and it is:
''pci=resource_alignment=08:02.0''.


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