Date: Fri, 14 May 2021 10:20:34 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 252265] ESXi: network connectivity issues after snapshoting FreeBDS VM with vmxnet3 interfaces Message-ID: <bug-252265-27103-OiltmWqYeO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252265-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-252265-27103@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=3D252265 peter.sopko+freebsd.org@backbone.sk changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.sopko+freebsd.org@bac | |kbone.sk --- Comment #4 from peter.sopko+freebsd.org@backbone.sk --- 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, 173255= 51). 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 creat= ed ping response times went to 50000-60000ms and a few lost packets, when i tr= ied http it appeared as if the server was not responsive). After net reboot all worked just fine.=20 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 probab= ly changes with time) as well. The best solution would probably be to upgrade to 12.2/13.0 (as those appea= r to work fine) --=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-252265-27103-OiltmWqYeO>