Originally Posted by syg00
The swapout will hit an in-memory hipervisor representation of the swap space. Hopefully. If not, the hipervisor will fault and allocate memory for the expansion of the (guest) swap.
Not exactly, the representation is just an empty file, which I want to place on a host ramdisk. Every fault in the guest, adds a little to this file. When the file occupies the entire ramdisk, we have a problem. No page-fault occurs in the hypervisor, it just freezes saying "out of disk space" or something.
Hoping to find a ramdisk that includes some physical disk space in it, so it starts off being as fast as ram and later becomes as fast as a disk if too much data is stored on it.
I have since found tmpfs that seems to use a mixture of ram and disk space. Seems to be just what I need, the place to store those vmware virtual drives that hold guest swap spaces.
But I don't understand the mounting of tmpfs. Why is it mounted at /