Bug 252265
| Summary: | ESXi: network connectivity issues after snapshoting FreeBDS VM with vmxnet3 interfaces | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | vistalba <register> | ||||
| Component: | kern | Assignee: | freebsd-virtualization (Nobody) <virtualization> | ||||
| Status: | Closed Overcome By Events | ||||||
| Severity: | Affects Some People | CC: | franco, markj, mauro.celli76, peter.sopko+freebsd.org, pkelsey, register | ||||
| Priority: | --- | Keywords: | iflib, regression | ||||
| Version: | 12.1-RELEASE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
I did a clean install of 11.4-RELEASE too. Snapshots are working fine in this release. It doesn't matter if open-vm-tools are installed or not. Snapshots without RAM does work as expected. (no issues in this case). Same problem with 12.1 p13 of opnsense Snapshot with memory result in no network. Same no network problem if i make vmotion. After vmotion network not work. I need to restart server, or disconnect and reconnect network, or make ifconfig vmx0 down && ifconfig vmx0 up , or make another vmotion in original place. Esxi 7.0 I can't quite see - did you test 12.2 at all? There are quite a few fixes for vmxnet3 there that are not in 12.1. tested it now for FreeBSD 12.0-RELEASE-p4, FreeBSD 12.1-RELEASE-p10, FreeBSD 12.2-RELEASE-p6 and 13.0-RELEASE VMs (hypervisor VMware ESXi, 7.0.1, 17325551). All appeared to be working correctly, but once (I did multiple test for each FreeBSD version) the FreeBSD 12.1-RELEASE-p10 behaved very similarly to what the original reported described (a moment after the snapshot has been created ping response times went to 50000-60000ms and a few lost packets, when i tried http it appeared as if the server was not responsive). After net reboot all worked just fine. Tried for an hour to reproduce it again, but was unable to, so I suspect it is not only related to vmx3, but there is some other factor to it (that probably changes with time) as well. The best solution would probably be to upgrade to 12.2/13.0 (as those appear to work fine) (In reply to peter.sopko+freebsd.org from comment #4) Thanks for testing. Without any confirmation of a bug in 12.2 or 13.0 I'm going to close the PR. |
Created attachment 221085 [details] 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.