From owner-freebsd-emulation Wed Jul 26 8:41:32 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 0A86437BBD0 for ; Wed, 26 Jul 2000 08:41:29 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA193290; Wed, 26 Jul 2000 11:41:18 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <397D5A03.74EC2582@freenet.co.uk> References: <14716.26696.719757.828831@hip186.ch.intel.com> <200007250002.UAA00521@jupiter.delta.ny.us> <14717.14343.423191.404139@whale.home-net> <397D5A03.74EC2582@freenet.co.uk> Date: Wed, 26 Jul 2000 11:41:19 -0400 To: A G F Keahan , John Reynolds From: Garance A Drosihn Subject: Re: Some VMware progress. More questions (was Re: latest VMware port dumping core. ) Cc: emulation@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:12 PM +0300 7/25/00, A G F Keahan wrote: >John Reynolds wrote: > > o In vain, I tried to access my CD-ROM which is a scsi device > > sitting on ahc0 target 3. If I tried to "install" this device > > inside the configuration editor I instantly get a core-dump > > the next time I try to "power on" the VM with the following > > message to the console: > > > > /: write failed, file system is full > > VMware Workstation PANIC: Slave process "SCSI0:3" died > > VMware Workstation PANIC: BUG F(566):524 bugNr=3728 > > Panic loop > >This is probably because your / partition is full. VMWare creates >a large file in /tmp (slightly larger than the amount of RAM you >specified), which you can't see because it's unlink()ed. You could >try symlinking /tmp to /var/tmp or another location that has more >disk space, and see if the problem persists. Do not play around with symlinks for /tmp. One of the readme or hints files talks about setting and exporting an environment variable so that vmware will use a different directory than /tmp for it's purposes. I created a simple shell which just sets that environment variable, and then starts the real vmware. At the very least, /var/tmp is MEANT to be different than /tmp, and thus I expect that you should not symlink the one to the other. It would probably be a good idea to change how vmware does this. Creating very large files in /tmp is not a good idea, given the default disklabel-configuration that freebsd uses. /tmp is in root (/) by default, and by default that is not a very large partition. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message