I am trying to wrap my head around what logic vEOS uses to map PCI network cards to EthernetX numbers.
I am running a lab in ESXi with 1x E1000 interface which always gets mapped to Ma1 – so far so good. However when I add 10x VMXNET 3 interfaces with ordered PCI IDs EOS seems to jumble the order. Ethernet1 ends up being the 4th VMXNET, Ethernet2 is the 8th. It is seemingly random to me.
It seems this would be a severe limitation if it is indeed random, so I must assume I am missing some crucial step.
Relevant parts of my .vmx:
lspci output from my vEOS instance:
Inside vEOS this is what I observe:
I also have no idea why Ethernet1 considers itself “down”, but that might be another issue. All the interfaces are connected to the same VLAN and configured identically.
In summary: I would appreciate any insights in how the EthernetX mapping is to PCI ID or MAC address for ESXi.
Each adapter you add to the VM is assigned a specific value for "pciPassthruX.pciSlotNumber". These values dictate the interface numbering on the vEOS.
Unfortunately, these decimal values are not in an order when we add a new adapter.We need to swap these values from one adapter to another to get the numbering right on vEOS. VMware cover this in more detail here.
Lowest value will be Ethernet1, and so on. Make sure not to alter the numbering in the list and rather just swap the value of one pciSlotNumber with another.
Post your Answer
You must be logged in to post an answer.