Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Sep 2017 06:58:47 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-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-8-s8xZN5HpcI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198406-8@https.bugs.freebsd.org/bugzilla/>
References:  <bug-198406-8@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D198406

Shawn <c.lilwah@outlook.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |c.lilwah@outlook.com

--- Comment #9 from Shawn <c.lilwah@outlook.com> ---
for those of you who are still running into this problem:

The issue seems to be on the VMWare side with the ethernet pciSlotNumber (w=
hich
is generated only on booting the VM with new vmxnet3 interfaces)

The interfaces, as they are presented to the VM, are out of order.=20
You will see this since the MAC addresses do not correspond between VMWare =
and
the VM's ifconfig.

the pci slot mapping is explained here

https://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&cmd=
=3DdisplayKC&externalId=3D2047927

we worked around this problem my editing the VM.vmx file and re-arranging t=
he
slotnumber values

Lab environment: ESXi 5.5.0 2068190, FreeBSD 10.1, FreeBSD 10.2 (sorry have=
n't
tested FreeBSD 11 as yet)

After adding all your interfaces to the VM (>4), boot up the VM then shut it
down.

SSH to the VMWare Host (you could theoretically download the vmx file from =
the
datastore, edit it and upload it again but we didn't do it that way)

cd /vmfs/volumes/DATASTORE/VM

vi into VM.vmx and remove all lines with ethernetX.pciSlotNumber

at the end of the file input this mapping (for as many interfaces as you ne=
ed)

ethernet0.pciSlotNumber =3D "160"
ethernet1.pciSlotNumber =3D "1184"
ethernet2.pciSlotNumber =3D "192"
ethernet3.pciSlotNumber =3D "1216"
ethernet4.pciSlotNumber =3D "224"
ethernet5.pciSlotNumber =3D "1248"
ethernet6.pciSlotNumber =3D "256"

save file and exit

boot up your VM.

All interfaces should match up with the correct MAC addresses now. You can
confirm with ifconfig and correlating it with the VM's settings in VMWare

If you are adding more than 8 interfaces the mapping should look like this

PciSlot# --------------------Interfaces ----------Hex values for Pcislot#
160 1184 2208   =3D=3D=3D>    vmx0    vmx1    vmx2    =3D=3D=3D>    A0     =
 4A0     8A0
192 1216 2240 =3D=3D=3D>      vmx3    vmx4    vmx5    =3D=3D=3D>    C0     =
 4C0     8C0
224 1248 2272 =3D=3D=3D>      vmx6    vmx7    vmx8    =3D=3D=3D>    E0     =
 4E0     8E0
256 1280 2304   =3D=3D=3D>    vmx9    vmx10   vmx11   =3D=3D=3D>    100    =
 400     900

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198406-8-s8xZN5HpcI>