Recently I found a bug with numbering four (and probably more) vmxnet3
interfaces under ESXi 6.5 (FreeBSD 11.0-RELASE, 10.0-RELEASE and ESXi 5.5U1
It seems that this is an old bug
Just reproduced this bug on ESXi 6.5 with FreeBSD 11.0-RELEASE-p9 with four
Obviously problem goes from wrong FreeBSD vmx interface numbering in
compare to VM ethernet interface order.
In my case mapping was follows:
ethernet0 -> vmx1
ethernet1 -> vmx2
ethernet2 -> vmx3
ethernet3 -> vmx0
I think something goes wrong on PCI probing/mapping stage.
I've tried (not all options) to change pci bus numbers for ethernet
interfaces in vmx config but without success.
Is any chance to fix it?
If I fix it by taking into account vmx renumbering, VM migration will
problem in future, if this is pci probe issue.
email@example.com mailing list
To unsubscribe, send any mail to