Hello there, I''ve been using a monitor system which requires information on PCI devices (collected via /proc/bus/pci/). Apparently, Xen''s DomU has an empty pci directory, therefore it''s unable to fetch such information. Is there a way to allow DomUs to "see" the PCI devices trough /proc/ ? Thanks. -- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Felipe Franciosi +55-51-91230557 CPAD/HP/PUCRS - Centro de Pesquisa em Alto Desempenho http://www.cpad.pucrs.br/ ozzy@cpad.pucrs.br Porto Alegre, RS - Brazil =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 24 Nov 2006 at 22:30, Felipe Franciosi wrote:> Hello there, > > I''ve been using a monitor system which requires information on PCI devices > (collected via /proc/bus/pci/). Apparently, Xen''s DomU has an empty pci > directory, therefore it''s unable to fetch such information.I can only conform this: # cat /proc/bus/pci/devices #> > Is there a way to allow DomUs to "see" the PCI devices trough /proc/ ? > > Thanks. > > -- > =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+> Felipe Franciosi +55-51-91230557 > CPAD/HP/PUCRS - Centro de Pesquisa em Alto Desempenho > http://www.cpad.pucrs.br/ ozzy@cpad.pucrs.br > Porto Alegre, RS - Brazil > =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
We found out that it''s possible to use a pci backend hack to hide a device from Dom0 and bind it to a specific DomU. The thing is that this will not fix my problem, as all I need is to the DomU to see specific data about the network controller. I can''t hide this device from Dom0, or several other things will stop working. :) I was thinking about writing a module that will assign a fake PCI device just to provide my software with the information needed, but I was hoping some expert soul on this list would help me get through with an easier solution. Thanks -- =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Felipe Franciosi +55-51-91230557 CPAD/HP/PUCRS - Centro de Pesquisa em Alto Desempenho http://www.cpad.pucrs.br/ ozzy@cpad.pucrs.br Porto Alegre, RS - Brazil =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ -----Mensagem original----- De: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] Em nome de Ulrich Windl Enviada em: segunda-feira, 27 de novembro de 2006 05:43 Para: xen-users@lists.xensource.com Assunto: Re: [Xen-users] Listing PCI Devices in a DomU On 24 Nov 2006 at 22:30, Felipe Franciosi wrote:> Hello there, > > I''ve been using a monitor system which requires information on PCI devices > (collected via /proc/bus/pci/). Apparently, Xen''s DomU has an empty pci > directory, therefore it''s unable to fetch such information.I can only conform this: # cat /proc/bus/pci/devices #> > Is there a way to allow DomUs to "see" the PCI devices trough /proc/ ? > > Thanks. > > -- > =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+> Felipe Franciosi +55-51-91230557 > CPAD/HP/PUCRS - Centro de Pesquisa em Alto Desempenho > http://www.cpad.pucrs.br/ ozzy@cpad.pucrs.br > Porto Alegre, RS - Brazil > =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/27/06, Felipe Franciosi <ozzy@cpad.pucrs.br> wrote:> The thing is that this will not fix my problem, as all I need is to the DomU > to see specific data about the network controller. I can''t hide this device > from Dom0, or several other things will stop working. :)XenMon is doing statistical stuff on dom0 - maybe this has the information you need. Also, Xenstats and dtc-xen generate statistics, the latter also for network stuff. But I don''t know what data you want to collect exactly. What forces you to collect the data in domU? I think, most interesting data is available in dom0, as all I/O has to go through dom0 anyway. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users