locked
PCI ID for hyper-V Network adapter? RRS feed

  • Question

  • Hi experts,

    I have a custom Linux running on Hyper-V. I need to check the PCI ID for the Network Adapter. It is not ther in the PCI devices list here: http://pci-ids.ucw.cz/read/PC/1414

    #lspci  command doesn't list the Network Adapter.

    Is the Network adapter in Hyper-V having an ID?

    What is the PCI ID for the network adapter in Hyper-V VMs?

    Thanks,

    Saleem


    • Edited by A Saleem Wednesday, April 2, 2014 10:50 AM
    • Moved by BrianEhMVP Wednesday, April 2, 2014 2:55 PM
    Wednesday, April 2, 2014 10:48 AM

Answers

  • Is it feasible for you to the check the PCI ID from the host? If not then you can attach the network card as a legacy adapter and check if it shows up under the PCI tree. The network adapter can only be attached as a synthetic network adapter or a legacy network adapter. Once it has been configured to be a synthetic network adapter, there is no way to check its PCI ID from the guest.

    Please let me know if this answers your question.

    Thanks,

    Abhishek


    Thursday, April 3, 2014 7:16 PM

All replies

  • Hi,

    http://support.microsoft.com/kb/2844106

    Do you have Integration Services installed?


    http://OpsMgr.ru/

    Wednesday, April 2, 2014 10:58 AM
  • Yes. Version 3.4 is installed.

    Wednesday, April 2, 2014 11:29 AM
  • Unfortunately, lspci will not list Hyper-V devices because synthetic devices on Hyper-V use the Hyper-V bus and that is not visible in the pci device tree. Could you tell me why you need the PCI ID for each device?

    Furthermore, Hyper-V devices can be found by using the following command in the root directory:

    [root@localhost LNXSYSTM:00]# find . -name vmbus*

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_10

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_11

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_12

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_13

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_14

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_16

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_1

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_2

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_3

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_4

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_5

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_7

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_8

    ./device:00/PNP0A03:00/device:08/VMBUS:00/vmbus_0_9

    Each of the above lines represents a directory wherein you can find further details for the device. Please let me know if this serves your purpose.

    Thanks,

    Abhishek

    Thursday, April 3, 2014 12:54 AM
  • Thanks Abishek.

    I need to check the network adapters before vmbus registers the devices. So that I can know the hardware before.

    The DEC 21140 is for the legacy network adapter. Is there any way to check the network adapters present from Linux VM?

    Thanks,

    Saleem

    Thursday, April 3, 2014 3:23 PM
  • Is it feasible for you to the check the PCI ID from the host? If not then you can attach the network card as a legacy adapter and check if it shows up under the PCI tree. The network adapter can only be attached as a synthetic network adapter or a legacy network adapter. Once it has been configured to be a synthetic network adapter, there is no way to check its PCI ID from the guest.

    Please let me know if this answers your question.

    Thanks,

    Abhishek


    Thursday, April 3, 2014 7:16 PM