diff options
| -rw-r--r-- | emulators/vmware2/files/Hints.FreeBSD | 29 | ||||
| -rw-r--r-- | emulators/vmware3/files/Hints.FreeBSD | 29 |
2 files changed, 40 insertions, 18 deletions
diff --git a/emulators/vmware2/files/Hints.FreeBSD b/emulators/vmware2/files/Hints.FreeBSD index 63617d56341f..f1528c31697a 100644 --- a/emulators/vmware2/files/Hints.FreeBSD +++ b/emulators/vmware2/files/Hints.FreeBSD @@ -75,17 +75,28 @@ empty or when you're about to eject the media. (Obtain the write permission on /dev/rfd0 if you write floppy disks) -- Consider making a link /compat/linux/tmp if your /tmp doesn't have -sufficient free space or is slow. VMware uses /tmp to back the VM's -memory. +- VMware creates a file that is about 25% larger than the guest OS's +RAM size, unlinks it and mmap's on it on the first startup of the VM. -e.g. - ln -s /usr/tmp /compat/linux/tmp +The default directory for the mmap is the value of TMPDIR environment +variable, or if it's undefined, /tmp. -Also, be very careful if /tmp/ is an MFS partition. VMware -creates a file that is about 25% larger than the guest's RAM size, -unlinks it and does mmap on it. Such a large, active file in -MFS can lead to deadlocks. +Therefore, it would be a good idea to have your TMPDIR variable +defined as a directory 1) that performs fast, 2) that has sufficient +free space, and 3) that isn't on MFS; if your /tmp doesn't meet those +three conditions. + +1 is because that will significantly improve the performance, 2 is +because the VM cannot even boot when the mmap fails, and 3 is because +such a large, active file on MFS could lead the system to deadlocks. + + +Alternatively, you can make /compat/linux/tmp to fake /tmp, however, +you should note that it would cause you silly troubles: Imagine a +Linux application (say, Linux Netscape) which creates a temporary file +in /tmp and passes it to some external program; you'll see it actually +creates a file in /compat/linux/tmp when the external program searches +/tmp literally. - Don't miss the VMware FAQ available on the official site. diff --git a/emulators/vmware3/files/Hints.FreeBSD b/emulators/vmware3/files/Hints.FreeBSD index 63617d56341f..f1528c31697a 100644 --- a/emulators/vmware3/files/Hints.FreeBSD +++ b/emulators/vmware3/files/Hints.FreeBSD @@ -75,17 +75,28 @@ empty or when you're about to eject the media. (Obtain the write permission on /dev/rfd0 if you write floppy disks) -- Consider making a link /compat/linux/tmp if your /tmp doesn't have -sufficient free space or is slow. VMware uses /tmp to back the VM's -memory. +- VMware creates a file that is about 25% larger than the guest OS's +RAM size, unlinks it and mmap's on it on the first startup of the VM. -e.g. - ln -s /usr/tmp /compat/linux/tmp +The default directory for the mmap is the value of TMPDIR environment +variable, or if it's undefined, /tmp. -Also, be very careful if /tmp/ is an MFS partition. VMware -creates a file that is about 25% larger than the guest's RAM size, -unlinks it and does mmap on it. Such a large, active file in -MFS can lead to deadlocks. +Therefore, it would be a good idea to have your TMPDIR variable +defined as a directory 1) that performs fast, 2) that has sufficient +free space, and 3) that isn't on MFS; if your /tmp doesn't meet those +three conditions. + +1 is because that will significantly improve the performance, 2 is +because the VM cannot even boot when the mmap fails, and 3 is because +such a large, active file on MFS could lead the system to deadlocks. + + +Alternatively, you can make /compat/linux/tmp to fake /tmp, however, +you should note that it would cause you silly troubles: Imagine a +Linux application (say, Linux Netscape) which creates a temporary file +in /tmp and passes it to some external program; you'll see it actually +creates a file in /compat/linux/tmp when the external program searches +/tmp literally. - Don't miss the VMware FAQ available on the official site. |