http://bugzilla.novell.com/show_bug.cgi?id=619030 http://bugzilla.novell.com/show_bug.cgi?id=619030#c1 --- Comment #1 from mail ignored <0.bugs.only.0@gmail.com> 2010-07-01 19:29:11 PDT --- reading at, "PCI-Paththrough with PCI-Card does not work anymore with RHEL5.4 " https://bugzilla.redhat.com/show_bug.cgi?id=521346#c27 with the setup above, after boot, dmesg | grep -i seiz [ 16.220175] pciback 0000:02:00.0: seizing device [ 16.220479] pciback 0000:04:00.0: seizing device xm pci-list-assignable-devices 0000:04:00.0 0000:02:00.0 then, once booted, @shell, echo -n 0000:05:07.0 > /sys/bus/pci/drivers/sata_sil24/unbind echo -n 0000:05:07.0 > /sys/bus/pci/drivers/pciback/new_slot echo -n 0000:05:07.0 > /sys/bus/pci/drivers/pciback/bind checking, dmesg | grep -i seiz [ 16.220175] pciback 0000:02:00.0: seizing device [ 16.220479] pciback 0000:04:00.0: seizing device [ 3886.476835] pciback 0000:05:07.0: seizing device xm pci-list-assignable-devices 0000:05:07.0 0000:04:00.0 0000:02:00.0 so the sata_sil24 device is *assignable* -- just not getting taken care of @ boot. testing per that thread -- just in case -- instead of as spec'd @, http://wiki.xensource.com/xenwiki/XenPCIpassthrough "If you're using Linux 2.6.31 or newer dom0 kernel based on the Novell/SLES/OpenSuse Xenlinux forward-ported patches, then you use this syntax:" pciback.permissive pciback.hide=(00:1d.7)(00:1a.0)(00:1a.1)(00:1a.7)(00:1b.0) pci=resource_alignment=00:1a.7;00:1d.7 adding to /etc/modprobe.d/99-local.conf options pciback hide=(0000:05:07.0)(0000:02:00.0)(0000:04:00.0) unfrotunately, same cirumstance -- not seized @ boot. but assignable after start using the "echo -n ..." cmds, above. now, the 'why not' ... and what's changes since 11.2 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.