VMware vSphere

 View Only

  • 1.  Which kinds of pci device will be added into hidden list

    Posted Mar 05, 2013 10:13 AM

    Except device owned by VM passthrough, is there any other pci device will be added into hidden list?



  • 2.  RE: Which kinds of pci device will be added into hidden list

    Posted Mar 06, 2013 02:33 AM

    When the vmkernel boot up, the pci device 00:15:00.0 was found and owned by vmkernel:

    0:00:00:04.635 cpu0:4096)PCI: 973: scanning pci bridge 0x41000f612bf0 @ seg/bus 00:15
    0:00:00:04.636 cpu0:4096)PCI: 3400: Device 00:15:00.0 is disabled by the BIOS
    0:00:00:04.636 cpu0:4096)PCI: 6344: 15:00.0: PCIe v2 PCI Express Endpoint
    0:00:00:04.636 cpu0:4096)PCI: 5327: 00:15:00.0: Found Advanced Error Reporting support
    0:00:00:04.636 cpu0:4096)PCI: 5327: 00:15:00.0: Found Single Root I/O Virtualization support
    0:00:00:04.636 cpu0:4096)PCI: 5327: 00:15:00.0: Found Endpoint Association support
    0:00:00:04.636 cpu0:4096)PCI: 6277: 15:00.0: PCIe v2 PCI Express Endpoint
    0:00:00:04.636 cpu0:4096)PCI: 6282: Not a ACS capable device
    0:00:00:04.636 cpu0:4096)PCI: 3520: 00:15:00.0 1014:034a 1014:035d added
    0:00:00:04.636 cpu0:4096)PCI: 3522:   classCode 0104 progIFRevID 0000
    0:00:00:04.636 cpu0:4096)Device: 527: Registered device: p=0x41000f612bf0 0x41000f611440 00:15:00.0 1014:034a 1014:035d bd=0x4100016ee160
    0:00:00:04.636 cpu0:4096)PCI: 5402: Enabling device (00:15:00.0), Command register mask: 0x6
    0:00:00:04.636 cpu0:4096)VMK_PCI: 317: device 00:15:00.0 event: Device inserted: new owner vmkernel
    0:00:00:04.636 cpu0:4096)Device: 196: Found driver pci for device 0x41000f612bf0

    But when the vmklinux module load, the device 00:15:00.0 did not be allocated the vector:

    2013-02-27T02:57:38.152Z cpu9:4604)vmklinux: init_module:2016: vmklinux module load starting...
    2013-02-27T02:57:38.152Z cpu9:4604)vmklinux: init_module:2019: Module Version = 5.1.0-9.2
    2013-02-27T02:57:38.152Z cpu9:4604)vmklinux: init_module:2022: max_pfn = 0x67ffff
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1654: for module c
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:01.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:0b:00.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:0b:00.1 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:02.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:10:00.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:10:00.1 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:03.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:07.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.1 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.2 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.3 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.4 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.5 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.6 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:16.7 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1a.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1a.1 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1a.7 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1c.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:01:00.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1c.4 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:06:00.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1d.0 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1d.1 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1d.2 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1d.7 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1224: device 00:00:1f.2 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)WARNING: VMK_PCI: 1170: device 00:00:1f.3 has no legacy interrupt(s)
    2013-02-27T02:57:38.162Z cpu9:4604)VMK_PCI: 1227: device 00:00:1f.3 failed to allocate 1 vectors (intrType 1)
    2013-02-27T02:57:38.162Z cpu9:4604)WARNING: LinPCI: LinuxPCILegacyIntrVectorSet:80:Could not allocate legacy PCI interrupt for device 0000:00:1f.3
    2013-02-27T02:57:38.163Z cpu9:4604)VMK_PCI: 1224: device 00:00:1f.5 allocated 1 vectors (intrType 1)
    2013-02-27T02:57:38.164Z cpu9:4604)<6>DMI 2.5 present.
    2013-02-27T02:57:38.164Z cpu9:4604)<6>mice: PS/2 mouse device common for all mice

    The device 00:15:00.0 was NOT configured as passthrough. So which kind of pci device can be added into hidden list



  • 3.  RE: Which kinds of pci device will be added into hidden list

    Posted Mar 06, 2013 07:49 AM

    What do you mean with "hidden list"?

    Is this causing any problems or symptoms for you?

    // Linjo



  • 4.  RE: Which kinds of pci device will be added into hidden list

    Posted Mar 06, 2013 08:48 AM

    Hi Joel,

    Thanks very much for your reply! There are two lists in vmkernel for pci device: pci_devices and pci_hidden_devices. My device was put into the pci_hidden_device list when vmkernel bootup. So driver can not probe the pci device. The pci device is new generation. But the older one can be probe and work with the driver. I do not understand which kinds of pci device will be added into vmkernel pci_hidden_devices list. Do you have any idea about it or how to debug the problem?

    Best regards

    Mengze

    Joel Lindberg -2013/03/06 15:41:00-Joel Lindberg replied to the discussion "Which kinds of

    From: Joel Lindberg <communities-emailer@vmware.com>

    To: Meng Ze Liao/China/IBM@IBMCN

    Date: 2013/03/06 15:41

    Subject: New message: "Which kinds of pci device will be added into hidden list"