Sid_F
asked on
Terminal server 2003 slow on hyper V
I recently moved a terminal server to hyper V from physical server. CPU is hitting 100% and staying there consistantly through out the day. I moved it from a raid 5 to a raid 1 to improve performance, with just me logged in and trying to run a defragment the cpu is still high and has peaks of 100%. Is there anything else I can do to improve performance. I have 4 logical processors assigned and 4 gig of memory, the nic is reporting 10Gbps.
ASKER
Yes this is 2008 r2. Will check out the links thanks
ASKER
With a few users logged on it took over ten mins to open perfmon, cpu is running constantly at 100, its running so slow the perfmon window at times is unresponsive. avg disk queue length and page/sec are 50-100% peaks but never stay constant, cpu is %processor time is constantly at 100%
ASKER
Can can I identify what process is taking the cpu 100%, need to delve deeper but am not sure how
ASKER
I checked this setup against another site that is running 2008 ts (not r2) however that site is showing up 4 processors in device manager but this server is showing up as 1 processor even though 4 have been specified in the vm settings
ASKER
The issue relates to the HAL and the machine not picking up the processors properly. Once this was changed and the correct dll's installed, TS performance was massively improved and is now better performance that its original performance directly on hardware.
I will post the details as to the exact fix. Hopefully this will help others experiencing this problem
I will post the details as to the exact fix. Hopefully this will help others experiencing this problem
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Fixed
http://blogs.msdn.com/b/rds/archive/2009/06/24/running-ws08-terminal-server-as-a-virtualized-guest-under-windows-server-2008-r2-hyper-v.aspx
My fear is the 2003 was not optimised for virtual anything. Take a look at the blog
http://social.technet.microsoft.com/Forums/en/winserverhyperv/thread/0753f4dd-fd4e-45e4-be32-6e690cfe9110
you will certainly want to use procmon and perfmon to identify the processs or perfmon issues... can you narrow it to a disk queue legnth or a process? Then the old troubleshooting is applicable. Please post that information after looking at the MS blog for 2003. try to narrow it down to a more specific question.