seron at online.de
Mon Mar 31 04:35:39 UTC 2008
I just saw following in dmesg:
pciback 0000:00:06.0: seizing device
[ 1.947027] pciback 0000:01:03.0: seizing device
[ 1.947161] pciback 0000:01:04.0: seizing device
[ 1.947295] pciback 0000:01:04.1: seizing device
[ 1.947431] pciback 0000:02:0e.0: seizing device
[ 1.947783] ACPI: PCI Interrupt 0000:02:0e.0[C] -> GSI 21 (level,
low) -> IRQ 16
[ 1.948026] ACPI: PCI interrupt for device 0000:02:0e.0 disabled
[ 1.948299] ACPI: PCI Interrupt 0000:01:04.1[B] -> GSI 24 (level,
low) -> IRQ 17
[ 1.948539] ACPI: PCI interrupt for device 0000:01:04.1 disabled
[ 1.948805] ACPI: PCI Interrupt 0000:01:04.0[A] -> GSI 23 (level,
low) -> IRQ 18
[ 1.949045] ACPI: PCI interrupt for device 0000:01:04.0 disabled
[ 1.949348] ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level,
low) -> IRQ 19
[ 1.949587] ACPI: PCI interrupt for device 0000:00:06.0 disabled
So you was right and it worked. But after that message drivers of the
"hidden" devices were loaded like normal and afterwards its possible to
see them on lsmod.
One Device is a video-card (dvb) and the other is a sata-raid controller
Does anybody have some idea?
Thanks a lot, Stephan.
Am Montag, den 31.03.2008, 06:00 +0200 schrieb Stephan Schulz:
> Hi Todd,
> thank you for your Quick reply. Most likely you are right and there are
> pretty good reasons for making a module.
> I made suggestes changes, but there still seems to be something wrong.
> I did the following:
> - insert "pciback" in /etc/initramfs-tools/modules
> - insert "options pciback hide=(00:06.0)" into /etc/modprobe.d/options
> - update-initramfs -u
> - reboot
> modules of PCI devices still appear in lsmod.
> Could it be that when pciback is loaded by initrd the
> file /etc/modprobe.d/options isn't already availible? Is there a way to
> insert the "options" into the initrd?
> Do you have other ideas?
> Thanks a lot for your Help!
> Am Sonntag, den 30.03.2008, 23:13 -0400 schrieb Todd Deshane:
> > Hi Stephan,
> > I am not on the kernel team, but I can give you pointers for using
> > Xen.
> > Even if pciback is compiled as a module and not directly into the
> > kernel, you should still be able to use it.
> > The basic idea is to build it into the initiral RAM disk (initrd). You
> > can add the module to /etc/initramfs-tools/modules and then run:
> > update-initramfs -u
> > You should then be able to use the pciback functionality. Here
> > reference on the xen-users mailing list :
> > http://xen.markmail.org/search/?q=CentOS and pciback#query:CentOS and
> > pciback+page:1+mid:44atjkwi3qi7fzqb+state:results
> > It gives the mkinitrd equivalent, which is a similar tool to the
> > mkinitramfs tool that Ubuntu uses.
> > I am guessing that the kernel team did have reason and setup the
> > policy of what to build as module etc. If adding it to the initrd
> > doesn't work I would recommend that you file a bug to the Xen-3.2
> > package, as those bugs are generally fixed in a timely fashion.
> > Also, another appropriate place to ask questions if you run into
> > further problems is the xen-users mailing list
> > ( http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users )
> > Regards,
> > Todd
> > On Sun, Mar 30, 2008 at 10:47 PM, Stephan Schulz <seron at online.de>
> > wrote:
> > Hello kernel-team,
> > i've just installed the new Hardy Beta Release with
> > ubuntu-xen-server
> > package.
> > Now I wanted to hide some pci devices to pass them to xen
> > guests.
> > The problem now is, that I can't use pciback at boot time
> > because it's a
> > module and not compiled into the kernel.
> > Will you compile it into the kernel in final release as you
> > did in
> > gutsy?
> > Thanks for such great work!
> > Stephan
> > --
> > kernel-team mailing list
> > kernel-team at lists.ubuntu.com
> > https://lists.ubuntu.com/mailman/listinfo/kernel-team
More information about the kernel-team