Hyper-V Heartbeat: Lost Connection

hi,

it's second time have critical error hyper-v - lost connection. os server 2008 r2 hyper-v role , there 6 vms on it, lost connection state vm exchange 2010. i'm unable start rdp on lost vm , virtual machine connection in hyper-v console can show vm's desktop only! of' course network connection vm unavailable.

there lots of errors on vm during state, no errors on host machine.

error    11/04/2010 11:56:41 p.m.    msexchange adaccess    2501    general
error    11/04/2010 11:54:16 p.m.    msexchange adaccess    2122    topology
error    11/04/2010 11:54:16 p.m.    msexchange adaccess    2104    topology
error    11/04/2010 11:53:41 p.m.    msexchange adaccess    2604    general
error    11/04/2010 11:48:45 p.m.    msexchange rpc on http autoconfig    2001    general
error    11/04/2010 11:43:08 p.m.    msexchange adaccess    2102    topology
error    11/04/2010 11:41:41 p.m.    msexchange adaccess    2501    general
error    11/04/2010 11:41:27 p.m.    msexchangeapplicationlogic    9106    serverpicker
error    11/04/2010 11:41:15 p.m.    msexchangesa    9153    general
error    11/04/2010 11:38:41 p.m.    msexchange adaccess    2604    general
error    11/04/2010 11:36:25 p.m.    msexchange mailbox replication    1005    service
error    11/04/2010 11:34:31 p.m.    msexchange adaccess    2122    topology
error    11/04/2010 11:34:31 p.m.    msexchange adaccess    2104    topology
error    11/04/2010 11:33:45 p.m.    msexchange rpc on http autoconfig    2001    general
error    11/04/2010 11:33:00 p.m.    msexchangeis mailbox store    7200    general
error    11/04/2010 11:26:41 p.m.    msexchange adaccess    2501    general
error    11/04/2010 10:48:00 p.m.    msexchangeis mailbox store    7200    general
error    11/04/2010 10:45:09 p.m.    msexchange adaccess    2102    topology
error    11/04/2010 10:41:18 p.m.    msexchangesa    1031    general
error    11/04/2010 10:39:09 p.m.    msexchangesa    9153    general
error    11/04/2010 10:24:24 p.m.    msexchange mailbox replication    1005    service
error    11/04/2010 10:24:12 p.m.    msexchangeapplicationlogic    9106    serverpicker
warning    11/04/2010 10:23:04 p.m.    msexchange certificate deployment    2006    general
error    11/04/2010 10:23:04 p.m.    msexchange edgesync    1025    topology
error    11/04/2010 10:18:45 p.m.    msexchangeis    9662    general
error    11/04/2010 10:18:20 p.m.    msexchange adaccess    2122    topology
error    11/04/2010 10:15:22 p.m.    msexchange adaccess    2103    topology
error    11/04/2010 10:15:22 p.m.    msexchangesa    9154    general
warning    11/04/2010 10:12:55 p.m.    msexchange mailbox replication    1007    service
error    11/04/2010 10:12:18 p.m.    msexchange transportservice    1015    processmanager
error    11/04/2010 10:11:59 p.m.    msexchangeapplicationlogic    9106    serverpicker
error    11/04/2010 10:08:34 p.m.    msexchange adaccess    2917    general
error    11/04/2010 10:08:17 p.m.    msexchange adaccess    2104    topology
error    11/04/2010 10:07:55 p.m.    msexchangemailsubmission    1026    msexchangemailsubmission
error    11/04/2010 10:07:55 p.m.    msexchangeapplicationlogic    9106    serverpicker
error    11/04/2010 10:07:06 p.m.    msexchange transportservice    1033    processmanager
warning    11/04/2010 10:06:59 p.m.    msexchange search indexer    118    general
error    11/04/2010 10:06:52 p.m.    msexchangetransport    17012    storage
error    11/04/2010 10:06:35 p.m.    msexchange adaccess    2102    topology
warning    11/04/2010 10:04:25 p.m.    msexchange mailbox replication    1007    service
error    11/04/2010 10:03:46 p.m.    msexchange rpc on http autoconfig    2001    general
error    11/04/2010 10:03:11 p.m.    msexchange autodiscover    1    web

found 1 way solve - turn off vm, turn on, it's annoying , danger.

did have issue before?

hello,

i've seen similar power settings in windows server 2008 r2 , latest intel processors.  this:

* disable c states in bios

* enable "high performance" power management on host systems

* apply patch: http://support.microsoft.com/default.aspx/kb/975530?p=1

* disable offloading on network cards

i hope helps out

nathan lasnoski

Windows Server  >  Hyper-V