Date: Wed, 17 May 2017 00:23:50 +0300 From: Andrew Vylegzhanin <avv314@gmail.com> To: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org Subject: vmx bug? Message-ID: <CA%2BBi_Ygn89Tg5DVG=x%2B0-NLQxCk_BTQj4dK2jBN63nUGc5%2BU5w@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hi! 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 reproduced). It seems that this is an old bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406 : ====> Just reproduced this bug on ESXi 6.5 with FreeBSD 11.0-RELEASE-p9 with four vmxnet3 interfaces 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. WBR, -- Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BBi_Ygn89Tg5DVG=x%2B0-NLQxCk_BTQj4dK2jBN63nUGc5%2BU5w>