Re: VMware's use of /tmp

From: Ken (ng3122_at_ke9nr.#nospam#.net)
Date: 02/23/04 

Date: Sun, 22 Feb 2004 21:16:28 -0800

Hi Nick -

On Mon, 23 Feb 2004 02:08:44 GMT, Nick Landsberg <hukolau@att.net>
wrote:

>In any event. According to the orgininal post & followups,
>VMware uses either your "real" /tmp or $TMPDIR to do the
>paging/swapping for you while you emulate something
>or other.

Having not purchased VMware (though I intend to), I also can only
speak on the basis of what has already been presented in this thread,
but it sounded to me like the problem has nothing to do with swapping,
but with having a virtual drive flagged as "undoable", i.e. you can
reverse the updates done to the drive by the software running in the
virtual machine.

If the updates can be undone, then the original data has to be stored
somewhere. What I got out of this thread was that this saved data is
being stored in /tmp (or $TMPDIR) and the way to avoid using all this
space is to not allow "undo"s.

The swap space for the software running in the virtual machine would
be whatever that software has and would be on a virtual drive. The
swap space for VMware itself should be the Linux swap space.

ICBW. STCWN. YMMV. 

-- 
Ken
http://www.ke9nr.net/