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
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
