From owner-freebsd-stable@freebsd.org Fri May 22 14:53:43 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4A7502CAD44; Fri, 22 May 2020 14:53:43 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 49T8d13sRcz4Ps4; Fri, 22 May 2020 14:53:41 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Fri, 22 May 2020 16:51:27 +0200 Received-SPF: SoftFail (connect.ultra-secure.de: domain of ultra-secure.de does not designate 127.0.0.10 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=127.0.0.10; helo=connect.ultra-secure.de; envelope-from= Received: from connect.ultra-secure.de (webmail [127.0.0.10]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 2B60CD6B-4416-4F13-AA5D-C47C16105522.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Fri, 22 May 2020 16:51:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit 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? In-Reply-To: <20200522140133.GA93041@thismonkey.com> References: <34c87fb8aa97ce4fa20deaf25da738f2@ultra-secure.de> <20200522140133.GA93041@thismonkey.com> Message-ID: <8a574476a6eee9df62e03bd93872a550@ultra-secure.de> X-Sender: rainer@ultra-secure.de User-Agent: Roundcube Webmail/1.2.0 X-Haraka-GeoIP: --, , NaNkm X-Haraka-GeoIP-Received: X-Haraka-p0f: os="undefined undefined" link_type="undefined" distance=undefined total_conn=undefined shared_ip=Y X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=ALL_TRUSTED,BAYES_00, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 1192, bad: 0, connections: 1198, history: 1192, pass:all_good, relaying X-Rspamd-Queue-Id: 49T8d13sRcz4Ps4 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rainer@ultra-secure.de designates 88.198.71.201 as permitted sender) smtp.mailfrom=rainer@ultra-secure.de X-Spamd-Result: default: False [-0.23 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.45)[-0.448]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[ultra-secure.de]; NEURAL_HAM_LONG(-0.37)[-0.367]; NEURAL_HAM_SHORT(-0.21)[-0.213]; FROM_NO_DN(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.198.0.0/16, country:DE]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2020 14:53:43 -0000 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