Date: Wed, 13 May 2015 20:23:25 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-virtualization@freebsd.org Subject: Re: Nested virtualization networking issues with bhyve Message-ID: <5553EAFD.8030406@freebsd.org> In-Reply-To: <CAO8hVipq_5AzxvL%2BkSbpaLFEuP%2BecU5_s1bGR2Rqv_=xM_ampQ@mail.gmail.com> References: <CAO8hVipq_5AzxvL%2BkSbpaLFEuP%2BecU5_s1bGR2Rqv_=xM_ampQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8Wrf0A14qIit10CM3QDFw5t3H4bKGMXLU Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-05-13 19:15, Jonathan Wong wrote: > I've recently tried to experiment with vmware esxi 6 + vmworkstation an= d I > managed to get nested virtualization with freebsd guest and nested bhyv= e > ubuntu VM working. However, the networking doesn't seem to come up prop= erly > while installing, and post install for the ubuntu VM. >=20 > The bridged networking works as expected with freebsd guests and other > network nodes on the network. However, the nested VMs themselves can't = seem > to bring up networking properly. >=20 > lspci seems to bring up the virtio network device, but even configuring= > static ips doesn't help. The VM is not able to receive or route any pac= kets > from any VM >=20 > FreeBSD guest can ssh into the nested VM. The nested VM can ssh into > freebsd guest. The nested VM cannot contact internet or local gateway.= > Tried with E1000 and VMXNET 2. Computers on network can ssh into freebs= d > guest. The freebsd guest can ssh into other computers on the network. > Computers on the network cannot contact the VM. The vmware host cannot > contact the nested VM or vice versa. >=20 > Any tips to getting this to work? >=20 > Thanks. > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 I helped you (or someone else) with this issue on IRC. The answer was to enable promiscuous mode on the nic in ESXi http://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&cm= d=3DdisplayKC&externalId=3D1004099 So that the FreeBSD (middle) host would receive the packets destine for the inner VM. Without promiscuous mode, any packets with an ethernet address other than that of the ESXi virtual nic, will not be passed into the VM. --=20 Allan Jude --8Wrf0A14qIit10CM3QDFw5t3H4bKGMXLU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJVU+r/AAoJEJrBFpNRJZKfIhYP/jBOOfT1vQRFuxhVqtNtkYNf HTJ1b1YWDlKLVviMDGiUtts6CF3bAGoPdkzO0Lqma9aBdyKC49NdffU+YDlIRefs r4J9hareSpO5WiL6Ej7eDuTmAnouKvYkyTqv27pP5VGbHjpc+Xwhd3q2e32ZAeMU YAJhrIFoJQfgyv9f9n1siietksHHPfsP5O49aE8RHaGt4ezsqT4e8UDfu3zpqMpG HuE3ZTnm8WC+FCAGoQOcu2FQa/Soq6xl7SpatrBAd41VBboyt29hbYbH3i6aHn9u 3dQ1kGQzaoCFGwaQlCLGRwvf/PkznZ8iLLW8PQDr+0Z8Rs6USqd+39BE8Pjlwzsc YZewE9Ka5J+gbiAZhZzPrxrQKzAcY2rBwpQWJjJX5JdlQoHsWyNhMNWTjMPKuMCw ruicqbaYIS8wnk7IIu6n1ifpgES22BOl2ME0k27zSyXVo0808+gBzu2nR6meUeMW 08w1xZYDgR6iVLqYA6oFnE26aG8qOH5UzmAHJPVd6LQ+NcubrhNKPsT062nTQASc Nqa6msED4dOpSDok77fKwoT6C0Uj01v8/kvyIwTM1E7P8/ddADGLrYF6lokQ2Tnr j81+sMkGFwxFGTpvQM3HQXAudtltrWvBnslZ/nT4tV/T2x0dmyutjRXe/vtHtkyl z/9kQJamG074kBu0wUoN =Vhcs -----END PGP SIGNATURE----- --8Wrf0A14qIit10CM3QDFw5t3H4bKGMXLU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5553EAFD.8030406>