Any differences in how you have the virtual machines set up? (Amount of RAM, vCPUs, etc.)
no, same configration, same virtual disk
windows 2000 server now work well, after some microsoft update,
windows 2003 server still bad performance, i suppose that i have bed performance because windows is using full CPU (100%) on disk i/o.
Anyone can help me ?
i still have a bad windows 2003 server disk performance \!!!
What kind of disks are you using ?
2 GB of memory is not to small ? How much memory the host is using, and how much are you allocating to the VM ?
Did you consider the possiblity of memory swapping on the disk ?
Do you use the same physical disk for the host and the VM ?
hi, tanx for reply.
i had tested virtual SCSI disk (LSI and BUSLOGIC) and ide disk but all them have the same problem.
I also had tried to add following option to my vm:
MemTrimRate = "0"
mainMem.useNamedFile = "FALSE"
with no result.
After upgrading vmware server from 1.02 to 1.03 preformance are better but not enough. I do other tests, and i see that my performance problem is in high cpu utilization on disk i/o. when i do test on same machine but with windows 2003 server native (host system) i give about 100 MB / sec with a 3% of CPU utilizzation, same system with windows 2003 as guest and linux mandriva + vmware server 1.03 as host system give me a 80 MB /sec with 100% cpu utilizzation.
When i had test windows as host system i installed 2 GB of ram, while in other test i installed 4 GB of ram, givin guest the same 2 GB ram, leaving linux host system 2 GB of ram as difference.
Linux host and windows guest are on different disks, i also try giving to the vm an intere phisical disk, but still the problem.
It seems to me that windows 2003 server is not using dma for disk or similar.
Any help ?
anyone can help me ?
i would try a few things and compare your results
1. try using different NTFS allocation sizes in your virtual disks (e.g. explicitly formatting with 8K, 16K, 32K, etc, insted of the default 4K).
e.g. "format e: /fs:ntfs /a:8192 /y"
2. try using the buslogic adapter type instead of lsilogic (or viceversa)
running whatever disk io benchmarking tool you have been using against these different configuratons will give you an idea what setup will work best on your hardware.
you may also want to try different underlying HOST filesystems and/or allocation sizes. generally i format my HOST NTFS volumes which contain the vmdk files at 64K. on linux there is a wide range of different filesystems and YMMV with each