Hello! I have installed SLES 10 SP 1 in dom0 and SLES 9 SP3 in domU in paravirtualized mode. But if I type lspci in the domU (sles9 sp3), it shows nothing, it returns no result. During booting the error "PCI: System does not support PCI" arises. (Documented in boot.msg). Is it normal, that no pci-devices are shown in the domU? I know, I have to pass throw it. But lspci show realy nothing. Is this behaviour normal? best Regards! Hermann _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, On Thu, 2008-01-31 at 09:26 +0100, Hoeld, Hermann wrote:> I have installed SLES 10 SP 1 in dom0 and SLES 9 SP3 in domU in > paravirtualized mode.I''m using Red Hat AS 5.1, and I have this problem too :) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello! It seems to be a normal behaviour. I have also installed a SLES 10 SP 1 in a domU and the behaviour was the same. If you do not pass through a pci device, then lspci delivers absolute nothing. If you pass through a pci device, then lspci delivers output. But following kernel-configuration in domU is necessary: CONFIG_XEN_PCIDEV_FRONTEND=y Type zcat /proc/config.gz > .config grep XEN_PCIDEV .config in your domU to see, if it is right configured. In my opinion it is not possible to pass through pci devices to a sles9 sp3 domU, because the kernel 2.6.5-7.282 (modified for xen) does not support "XEN PCI FRONTEND". best Regards! Hermann -----Ursprüngliche Nachricht----- Von: Tiago Cruz [mailto:tiagocruz@forumgdh.net] Gesendet: Donnerstag, 31. Jänner 2008 13:46 An: Hoeld, Hermann Cc: xen-users@lists.xensource.com Betreff: Re: [Xen-users] lspci in domU shows nothing Hello, On Thu, 2008-01-31 at 09:26 +0100, Hoeld, Hermann wrote:> I have installed SLES 10 SP 1 in dom0 and SLES 9 SP3 in domU in > paravirtualized mode.I''m using Red Hat AS 5.1, and I have this problem too :) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Hermann, On Thu, 2008-01-31 at 17:40 +0100, Hoeld, Hermann wrote:> Type zcat /proc/config.gz > .config > grep XEN_PCIDEV .config > in your domU to see, if it is right configured.I don''t have this file :( # zcat /proc/config.gz > .config zcat: /proc/config.gz: No such file or directory # uname -a Linux ftp-xen 2.6.18-8.el5xen #1 SMP Fri Jan 26 14:29:35 EST 2007 x86_64 x86_64 x86_64 GNU/Linux # ls /proc/ 1 1484 1743 2 79 execdomains loadavg sys 10 1513 1758 218 80 fb locks sysrq-trigger 1196 1537 1759 22 81 filesystems mdstat sysvipc 1198 1569 18 22507 82 fs meminfo tty 1216 1587 1803 236 9 ide misc uptime 1219 1611 1806 24 buddyinfo interrupts modules version 1269 1619 1807 265 bus iomem mounts vmcore 1306 1636 1808 299 cmdline ioports net vmstat 1347 1651 1819 3 cpuinfo irq partitions xen 1374 1680 1822 4 crypto kallsyms schedstat zoneinfo 1389 17 184 5 devices kcore self 1395 1709 1841 6 diskstats keys slabinfo 1417 1726 1852 622 dma key-users stat 1464 1742 1863 7 driver kmsg swaps _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
You shouldn''t see any PCI devices in lspci if you''re in a paravirt domU. In an HVM (full virtualisation) domU you will see output from lspci. HVM has to fake out a real PC so the guest OS won''t know it''s being virtualised; real PCs always have pci, so it has to fake a PCI bus ;-) PV guests know they''re running on Xen, so none of this faking-out is needed. They don''t get given any fake PCI devices because it''s not needed to make them happy ;-) What you''ve observed in lspci output is perfectly normal, nothing to worry about :-) Cheers, Mark -- Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Tiago! The procedure for testing if the kernel-option CONFIG_XEN_PCIDEV_FRONTEND=y is set, works for SuSE SLES. But you have installed Red Hat AS 5.1. Maybe that''s the reason why the file /proc/config.gz does not exists. You have to know if the kernel-option CONFIG_XEN_PCIDEV_FRONTEND=y is set. In the file /proc/config.gz is the kernel-configuration saved. You have to find an equivalent file for your system. Tiago, sorry, I can not say more, because I''m not familiar with Red Hat AS 5.1. Best Regards! Hermann _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 04 February 2008 03:44:51 am Hoeld, Hermann wrote:> You have to know if the kernel-option CONFIG_XEN_PCIDEV_FRONTEND=y is > set. > In the file /proc/config.gz is the kernel-configuration saved. > You have to find an equivalent file for your system.In fedora, and I would assume redhat, look in /boot/config-<kernel version>xen . _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users