[Bug 252265] network connectivity issues after snapshoting FreeBDS VM with vmxnet3 interfaces

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252265

            Bug ID: 252265
           Summary: network connectivity issues after snapshoting FreeBDS
                    VM with vmxnet3 interfaces
           Product: Base System
           Version: 12.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: register at kad-it.ch

Created attachment 221085
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=221085&action=edit
screenshot ping

I running opnsense with multiple vmx3 interfaces on vmware esxi 7.0.1.
Everyting war working well until the update to 20.7. (20.1 Release was fine).

I run into the issue, that when I take a snapshot of the VM incl. RAM the VM
isn't reachable over the network after this step.

I now installed a fresh FreeBSD install (Version: FreeBDS freebsd-test
12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC amd64) which results in the
same issue.


Steps to reproduce:
- Install new FreeBSD VM on ESXi with one VMXNET3 interface.
- config vmx interface with IP (or use DHCP)
- ping this interface from any other host in the network (constantly)
- create snapshot of the running VM including RAM and wait until snapshot is
finished.
- you can now see that ping isn't working anymore. (Sometimes the NIC is still
available but with very high latency 5000-12000ms).

When you login to FreeBSD console you don't have any network/internet
connectivity at all.

A simple "ifconfig vmx0 down && ifconfig vmx0 up" solves the problem.

If I can provide any other useful information let me know.

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