Date: Wed, 10 Jul 2019 13:54:45 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 198406] More than 4 esxi vmxnet3 interfaces causes vlans attached to vmxnet interfaces to stop working Message-ID: <bug-198406-227-JuyjQDepWp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-198406-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198406 --- Comment #10 from Luca Lesinigo <luca@lesinigo.it> --- I stumbled on this issue as well, so I'll add a few data points, hope it helps. - host VMware ESXi 6.5 build 13635690 (latest patch as of this writing) - guest pfSense 2.4.4_p3 (latest patch, based on FreeBSD 11.2-RELEASE-p10 amd64) - VM: initially version 10 (ESXi 5.5), with four VMXNET3 interfaces Adding the fifth VMXNET3 interface did not do any harm to the previous ones or their ordering, but the fifth simply didn't show up, instead getting this in dmesg: pci7: <ACPI PCI bus> on pcib4 vmx4: <VMware VMXNET3 Ethernet Adapter> at device 0.0 on pci7 vmx4: Ethernet address: 00:50:56:ad:b8:21 vmx4: detached pci7: detached Trying to upgrade VM to latest hardware (version 13, ESXi 6.5) did not change anything. Using VMXNET2 for the fifth interface (keeping the first four ones as VMXNET3) did not change anything. I couldn't try Shawn's workaround and I couldn't use that in production anyway, so I resorted to keeping the first four interfaces as VMXNET3 and adding the fifth as E1000. The system is now working correctly with all five interfaces. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198406-227-JuyjQDepWp>