Date: Fri, 31 Mar 2000 16:41:41 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: nsayer@kfu.com, freebsd-emulation@FreeBSD.ORG Subject: Re: VMware locks FreeBSD 4.0 solid Message-ID: <200004010041.QAA35417@apollo.backplane.com> References: <38E3FB31.3DD4D170@sftw.com> <14564.53252.962047.551231@grasshopper.cs.duke.edu> <200003311728.JAA29464@apollo.backplane.com> <14565.2133.162680.554248@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:To follow up: Taking MFS out of the picture seems to clear up the :problems. I've been beating the heck out of it for a while now, and :the system is still stable. Excellent diagnosis, Matt! : :VMware seems to look at the TMPDIR env variable, so I'll be making :sure to set that to /var/tmp before running VMware ;-) : :I wonder if they just started doing this (mmapping a large file in :$TMDIR) in 2.0? I was running a demo of 1.x with no problems a few :months back... : :Thanks, : :Drew : :------------------------------------------------------------------------------ :Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin It isn't really MFS's fault, and I am sure there are other situations that will lock up the same way. The issue is that we are getting a low-memory deadlock. Perhaps VMWare is wiring too many pages or something like that... I don't know yet. I think Nick's problem is different from the one you were encountering. -Matt Matthew Dillon <dillon@backplane.com> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004010041.QAA35417>