Date: Fri, 22 May 2020 16:51:20 +0200 From: rainer@ultra-secure.de To: stable@freebsd.org, freebsd-stable@freebsd.org Cc: owner-freebsd-stable@freebsd.org Subject: Re: Is it me or does FreeBSD (12.1 amd64) hang when I manually snapshot it in VSphere 6.7? Message-ID: <8a574476a6eee9df62e03bd93872a550@ultra-secure.de> In-Reply-To: <20200522140133.GA93041@thismonkey.com> References: <34c87fb8aa97ce4fa20deaf25da738f2@ultra-secure.de> <20200522140133.GA93041@thismonkey.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 2020-05-22 16:01, schrieb Scott: >> > #metoo: > > HV: VMware ESXi, 6.7.0, 11675023 > VM: # freebsd-version -kru > > 12.1-RELEASE-p1 > > 12.1-RELEASE-p1 > > 12.1-RELEASE-p1 > > # uname -a > > FreeBSD XXX 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 GENERIC amd64 > # pkg info open-vm\* > open-vm-tools-nox11-11.0.1_1,2 > > doesn't hang but becomes *very* unresponsive over the network. pings > are > shot. Console is fine though. 100% idle on top across 4 cores. And: > > # openssl speed -evp aes-256-cbc > ... > 1024 bytes block: 542595.18k (1593774 in 3 seconds) > > I never noticed that before. I normally turn off snapshotting the RAM > because it's so much faster and I'm happy with crash consistent > rollbacks. > > Rebooting fixes the awful network behaviour. I didn't check the disk > subsystem. OK, I now realized that not snapshotting the memory is way faster and doesn't crash the system. Usually, after I rollback a snapshot I reboot anyway. Because it was sometimes "funky" in the past, too. Thanks. But this should be fixed, too, at some point. Rainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8a574476a6eee9df62e03bd93872a550>