本文发表在 rolia.net 枫下论坛On my machine, I allocated 160MB RAM for Win2000. When I started Win2000 in vmware, it occupied about 187MB of RAM, no more, no less. If Win2000 is running out of the allocated RAM, it'll just swap to harddrive, which is just a big file (2G) in FreeBSD.
CPU doesn't really need to be that powerful (I was probably a little bit misleading in my previous message). When you just run one task (in our case, Win2000 in vmware), that one task will get most (if not all) of the CPU time. So it will be almost like running it natively.
My suggestion would be, run the OS natively in which you'll spend most of the time, and run the OS you'll spend less time as guest OS running in vmware.
One anoying thing about vmware for linux is that under linux, the file size is limited to 2GB (this limitation could've been lefted in recent kernels). So the max partition size for guest OS is 2GB under vmware (this is using virtual disk). I've never bothered to try other method (like raw disk device) which may not have this limitation.更多精彩文章及讨论，请光临枫下论坛 rolia.net
CPU doesn't really need to be that powerful (I was probably a little bit misleading in my previous message). When you just run one task (in our case, Win2000 in vmware), that one task will get most (if not all) of the CPU time. So it will be almost like running it natively.
My suggestion would be, run the OS natively in which you'll spend most of the time, and run the OS you'll spend less time as guest OS running in vmware.
One anoying thing about vmware for linux is that under linux, the file size is limited to 2GB (this limitation could've been lefted in recent kernels). So the max partition size for guest OS is 2GB under vmware (this is using virtual disk). I've never bothered to try other method (like raw disk device) which may not have this limitation.更多精彩文章及讨论，请光临枫下论坛 rolia.net