Build is beta 22009
Host info
Propriatary hardware
Quad Xeon 2.8Ghz processors
8GB RAM
Win2003 Enterprise Server
Guest info
4x -- Win2003 Std & 1 Win2KPro Workstation
Single Processor allocated to each with ACPI Uniprocessor HAL
256 allocated to Win2KPro
512MB allocated to each 2003 VM
VM Disks are preallocated contiguous files (converted from ESX export using "vmdiskmanager... -r -t 2)
Same disks are accessed through host with LightPulse 1050 on EMC SAN
Latest VMTOOLS installed on each.
LSI SCSI drivers being used on Win2K3
BusLogic used in Win2KPro
If I do a "dir /s" CSRSS runs between 70 and 80 percent until "dir" is complete. (processor is pegged at 100%)
Any help is greatly appreciated!
Jason
Message was edited by:
jkopp 3/23/06
After various further tests, "DIR" pegs a processor on ESX guests as well. It's not a beta issue, but rather VM in general? What causes this and how do I avoid it and other programs from pegging my host CPU usage?
It also seems as though the beta doesn't limit processor access on the guests to one processor. When I do a looping dir on a guest (uniprocessor HAL 1 processor assigned), running task manager on the host will show the quad processor usage jumping from 20% to 80%. This jump is level across all 4 processors.