Date: Sat, 21 Feb 2015 22:42:08 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 197884] System with zfs freezes if emulators/virtualbox-ose got all ram Message-ID: <bug-197884-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197884 Bug ID: 197884 Summary: System with zfs freezes if emulators/virtualbox-ose got all ram Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: vbox@FreeBSD.org Reporter: vvd@unislabs.com Assignee: vbox@FreeBSD.org Flags: maintainer-feedback?(vbox@FreeBSD.org) 10.1-p5 amd64, VirtualBox 4.3.12, 4.3.22, root on ZFS, virtual machines on ZFS. Core 2 Quad Q6600, 8Gb RAM. /boot/loader.conf have lines: vfs.zfs.arc_min="67108864" vfs.zfs.arc_max="268435456" vfs.zfs.prefetch_disable="1" Run only 1 VM with different amount of RAM: 6.5Gb or 7Gb. VM is very active using RAM. If 7Gb: after few days (hours?) after run rebuilding of any port, system freezes. Host replaying on ping (guest don't replay), but screen is black and no response on ssh console. Command "VBoxManage controlvm VMNAME savestate" freezes system too. Command top show "ARC: xxxM Total" with xxx < 256Mb (~160-230). Swap is used on ~50-100Mb. Free 10-50Mb. If 6.5Gb: all work fine after many weeks - ports rebuilding are work without freezes, savestate and startvm work correctly too. Command top show "ARC: xxxM Total" with xxx = 256Mb. Swap is used on ~0-50Mb. Free ~200Mb. Few times got same freezes on other hosts: Core i7 920 24Gb RAM with ~10-15 started VMs (RAM usage was near 23Gb). Didn't tested with UFS. P.S. Sorry for my English. --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer vbox@FreeBSD.org -- 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-197884-13>