Xen devel - Dec 2009 - [xen-3.4.2][2.6.31.6-pvops] pciback not seizing devices

Hi Konrad,

I was trying 2.6.31.6 pvops on my xen-3.4.2 server passing through 3
pci-devices, but none seems to get seized by pciback.
On xen-3.4.2 in combination with a xenified 2.6.29 kernel/ 2.6.18.8-xen kernel
it works fine with the same config in grub.

Could this be due to the renaming stuff of blkdev pciback to xen-blkdev
xen-pciback etc. ?


Attachted:
- xm info
- xm dmesg
- dmesg
- lspci -vvvknn
- .config 2.6.31.6 pvops kernel
- grub menu.lst


(if it helps i could send the same for the working combination.

--
Sander






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

Whoops made a mistake, actually booted the xen-4.0.0-pre hypervisor.


Monday, December 14, 2009, 10:12:09 AM, you wrote:
> Hi Konrad,
> I was trying 2.6.31.6 pvops on my xen-3.4.2 server passing through 3
pci-devices, but none seems to get seized by pciback.
> On xen-3.4.2 in combination with a xenified 2.6.29 kernel/ 2.6.18.8-xen
kernel it works fine with the same config in grub.
> Could this be due to the renaming stuff of blkdev pciback to xen-blkdev
xen-pciback etc. ?
> Attachted:
> - xm info
> - xm dmesg
> - dmesg
> - lspci -vvvknn
> - .config 2.6.31.6 pvops kernel
> - grub menu.lst
> (if it helps i could send the same for the working combination.
> --
> Sander


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


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

Problem is the same on the real 3.4.2 + 2.6.31.6-pvops.

the right files attachted


Monday, December 14, 2009, 10:31:05 AM, you wrote:
> Whoops made a mistake, actually booted the xen-4.0.0-pre hypervisor.
> Monday, December 14, 2009, 10:12:09 AM, you wrote:
>> Hi Konrad,
>> I was trying 2.6.31.6 pvops on my xen-3.4.2 server passing through 3
pci-devices, but none seems to get seized by pciback.
>> On xen-3.4.2 in combination with a xenified 2.6.29 kernel/ 2.6.18.8-xen
kernel it works fine with the same config in grub.
>> Could this be due to the renaming stuff of blkdev pciback to xen-blkdev
xen-pciback etc. ?
>> Attachted:
>> - xm info
>> - xm dmesg
>> - dmesg
>> - lspci -vvvknn
>> - .config 2.6.31.6 pvops kernel
>> - grub menu.lst
>> (if it helps i could send the same for the working combination.
>> --
>> Sander





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






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

Reverting to 2.6.31.6 with commit fce462ce4dd8dc75a76be8fdcd89d2eba7d11bae Merge
remote branch ''xen/xen/dom0/acpi-parser'' into xen/master

And pciback works.

-- 
Sander

Monday, December 14, 2009, 10:46:32 AM, you wrote:
> Problem is the same on the real 3.4.2 + 2.6.31.6-pvops.
> the right files attachted
> Monday, December 14, 2009, 10:31:05 AM, you wrote:
>> Whoops made a mistake, actually booted the xen-4.0.0-pre hypervisor.
>> Monday, December 14, 2009, 10:12:09 AM, you wrote:
>>> Hi Konrad,
>>> I was trying 2.6.31.6 pvops on my xen-3.4.2 server passing through
3 pci-devices, but none seems to get seized by pciback.
>>> On xen-3.4.2 in combination with a xenified 2.6.29 kernel/
2.6.18.8-xen kernel it works fine with the same config in grub.
>>> Could this be due to the renaming stuff of blkdev pciback to
xen-blkdev xen-pciback etc. ?
>>> Attachted:
>>> - xm info
>>> - xm dmesg
>>> - dmesg
>>> - lspci -vvvknn
>>> - .config 2.6.31.6 pvops kernel
>>> - grub menu.lst
>>> (if it helps i could send the same for the working combination.
>>> --
>>> Sander








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


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

On Mon, Dec 14, 2009 at 10:12:09AM +0100, Sander Eikelenboom
wrote:
> Hi Konrad,
> 
> I was trying 2.6.31.6 pvops on my xen-3.4.2 server passing through 3
pci-devices, but none seems to get seized by pciback.
> On xen-3.4.2 in combination with a xenified 2.6.29 kernel/ 2.6.18.8-xen
kernel it works fine with the same config in grub.
> 
> Could this be due to the renaming stuff of blkdev pciback to xen-blkdev
xen-pciback etc. ?
Might be. Try to change the ''pciback.hide'' to
''xen-pciback.hide'' and see if that
helps you out. In the meantime I am going to try to try the same thing on my
box.

I usually do the unbind, new-slot, bind process.


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

On Mon, Dec 14, 2009 at 12:21:44PM +0100, Sander Eikelenboom
wrote:
> Reverting to 2.6.31.6 with commit fce462ce4dd8dc75a76be8fdcd89d2eba7d11bae
Merge remote branch ''xen/xen/dom0/acpi-parser'' into xen/master
> 
> And pciback works.
Using ''xen-pciback.hide=(xx:yy:zz)'' also does the trick.

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

Yeps that''s it,

xen-pciback.hide instead of pciback.hide works fine.

Hmm perhaps it would be nice to have some "autobind" option for
devices in .cfg.
So you can let xend autounbind and bind pci and usb devices.
Or some scripting hooks like onbeforestart, etc.

Apart from not getting it to reboot, 2.6.31.6 pvops seems to work fine at the
moment :-)


Thx !
-- 

Sander



Monday, December 14, 2009, 3:54:00 PM, you wrote:
> On Mon, Dec 14, 2009 at 10:12:09AM +0100, Sander Eikelenboom wrote:
>> Hi Konrad,
>> 
>> I was trying 2.6.31.6 pvops on my xen-3.4.2 server passing through 3
pci-devices, but none seems to get seized by pciback.
>> On xen-3.4.2 in combination with a xenified 2.6.29 kernel/ 2.6.18.8-xen
kernel it works fine with the same config in grub.
>> 
>> Could this be due to the renaming stuff of blkdev pciback to xen-blkdev
xen-pciback etc. ?
> Might be. Try to change the ''pciback.hide'' to
''xen-pciback.hide'' and see if that
> helps you out. In the meantime I am going to try to try the same thing on
my box.
> I usually do the unbind, new-slot, bind process.



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


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