|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] pci device not owned by pciback.
On Wed, 2010-04-28 at 20:42 -0400, James Pifer wrote:
> On Wed, 2010-04-28 at 19:14 -0300, Sergio Charpinel Jr. wrote:
> > I think you forgot to make the new initrd with this options.
> > A time ago, I tried something similar to what you did, but i didnt
> > work here. I didnt get deep into this, so I recompiled the kernel.
> > Maybe I missed something too.
> >
>
>
> I thought looking at that config file that it meant that's the way it
> was configured, so updating modules.conf was all I needed. Can you
> elaborate on making the new initrd?
Still not sure what to do here. In my /boot directory I have this:
-rw-r--r-- 1 root root 88117 2009-02-28 02:28 config-2.6.27.19-5-xen
-rw-r--r-- 1 root root 6255788 2010-04-19 14:13 initrd-2.6.27.19-5-xen
lrwxrwxrwx 1 root root 22 2010-04-19 14:13 initrd-xen ->
initrd-2.6.27.19-5-xen
In /boot/grub/menu.lst I have:
title Xen -- SUSE Linux Enterprise Server 11 - 2.6.27.19-5
root (hd0,1)
kernel /boot/xen.gz dom0_mem=2048M
module /boot/vmlinuz-2.6.27.19-5-xen
root=/dev/disk/by-id/cciss-3600508b1001030364643393433300000-part2
resume=/dev/disk/by-id/cciss-3600508b1001030364643393433300000-part1
splash=silent showopts vga=0x317
module /boot/initrd-2.6.27.19-5-xen
uname -a gives:
Linux test03 2.6.27.19-5-xen #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64
x86_64 GNU/Linux
Inside config-2.6.27.19-5-xen have the lines:
CONFIG_XEN_PCIDEV_BACKEND=m
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
/etc/modprobe.conf.local has:
# hide pci card for xen passthrough
options pciback hide=(0000:0e:04.0)
options pciback hide=(0000:0e:04.1)
install mptspi /sbin/modprobe pciback ; /sbin/modprobe --first-time
--ignore-install mptspi
So, doesn't this mean that the initrd being used is already configured
to use pciback as a module, so updating modules.conf (or
modules.conf.local on sles11) like I have should be enough?
Help is appreciated. Boss is breathing down my neck!
Thanks,
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-users] pci device not owned by pciback., (continued)
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback., listmail
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Message not available
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback., Sergio Charpinel Jr.
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback., Sergio Charpinel Jr.
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback.,
James Pifer <=
- Re: [Xen-users] pci device not owned by pciback., Sergio Charpinel Jr.
- Re: [Xen-users] pci device not owned by pciback., James Pifer
- Re: [Xen-users] pci device not owned by pciback., Mark Hurenkamp
- Re: [Xen-users] pci device not owned by pciback., James Pifer
Re: [Xen-users] pci device not owned by pciback., Nick Couchman
|
|
|
|
|