Love/Hate relationship with Administering Hyper-V Hosts


i have doing wrong, not first time.... )-:

i have 3 hyper-v hosts setup. 40gb ram, 16 cores on one, , 24 on other two. hyper-v hosts os drives local raid 1 sata drives.  hyper-v guest imaged reside on iscsi san.

i remtoe desktop hyper-v host , administer guests. not typically connect guest on host unless being brought online.

the response of host guests running pathetic. clicking around in server manager or switching windows makes me think of old win95 days... there piii in there.

if remote desktop 1 of guests dont see increase in cpu usage on host , guest's response time super.  have sql server, web server, ad dc , others spread among 3 hosts. web server gets data sql server nice , speedy...

it seems bogs down after run 3-4 vm guests?

 

suggestions things for?


thanks!

i exact same thing , see exact same behavior.  let describe experience , see if parallels.

the key using parent partition management client.  , have found things go south.

the key have found need log out of parent partition whenever done administering using gui managment console.  if walk away, or disconnect rdp session on time gui wil worse , worse.

folks install hyper-v on workstations , use management os client machines suffer in same way.  , underlying casue same.

much of design - management os not supposed take resources away vms.  giving things up.  when first login - experience good.  things degrade.

log out, wait for the profile clean up, log in , things again.

i have found using management console installed on remote server or client not have same problems.

 


brian ehlert (hopefully have found useful) http://itproctology.blogspot.com


Windows Server  >  Hyper-V



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group