- VMware resource usage (again)
- Posted by Rohan Beckles on February 26th, 2004
Hello --
I have another question concerning VMware 4 Workstation. I have allocated
384MB to the instance running Windows 2000, and I have set the overall
reserved memory figure to 512MB.
Under Windows 2000 Professional, I'm running WinMX, a P2P client. WinMX
saves its files to a Samba share running on the Linux host. After a day or
two, my Linux swap memory (512MB) is all but used up, yet according to the
Windows 2000 Task Manager only 90MB out of 384MB is being used. Obviously,
Windows 2000 hasn't started to swap yet, so why is Linux doing so?
I would really appreciate some help on this. Thanks in advance,
Rohan Beckles
rohan.beckles@virgin.net
--
ABit VP6
2x Intel Pentium III "Coppermine" @ 1.0GHz
1GB Crucial SDRAM
Seagate Barracuda 20.4GB
3D Hercules Prophet II GTS Pro 64MB
NetGear FA310TX
Linux kernel 2.4.23
----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
- Posted by John-Paul Stewart on February 27th, 2004
Rohan Beckles wrote:
Sounds like a memory leak in VMware itself, rather than anything to do
with the guest OS. Or some other *Linux* process is using all of your
swap. Does the problem persist if you exit VMware (but doing everything
else the same)? If not, that indicates VMware is at fault. If exiting
VMware but leaving Linux up for a day or two still fills swap, then you
know its some other process within Linux that's eating swap.
It's possible (even likely) that some overnight cron job (e.g.,
'updatedb', which likes to use as much RAM as possible) is pushing other
tasks (including VMware itself) out to swap, and there they stay until
they need to be swapped in again.
- Posted by peter pilsl on February 27th, 2004
Rohan Beckles wrote:
you should analyze the linux-memory to realize whats happening and check if
its really vmware that uses up all the memory. There are tools like top
(use M to sort by mem) or infos in the /proc-structure that will aid you:
cat /proc/meminfo and look into /proc/SYS_ID_OF_VMWARE
peter
--
peter pilsl
pilsl_usenet@goldfisch.at
http://www.goldfisch.at