none
VMM Agent corrupted after Windows Updates + Migration issue RRS feed

  • Question

  • We are currently running a small three host setup on Hyperv + VMM and have been for the past few months. It is running on HPE Proliant G10 servers all with the same CPUs and Microsoft patch level. All four Gbit network cards have been teamed.

    We have run in to an issue twice now where all of the sudden, we are no longer able to migrate virtual machines between hosts due to so called CPU incompatibillity errors. In this case, we were able to move some VMs, but not others. And, we could move VMs to one host, but not the other.

    We found that installing latest Microsoft patches and/or rebooting the hosts resolved the issue. However, after we rebooted, we found that the network configuration seemed to have been corrupted when looking at it from the VMM. When we would open up the Virtual Switches tab on the properties of a host, we would see only one NIC still connected to the Team, the "Hyper-V Management - Microsoft Network Adapter Multiplexor Driver", and none of the actual physical NICs that are in the server.

    We found that the VMMagent seemed to be corrupted as can be seen from the application log event at the  bottom of this post, causing this issue. 

    We had to remove the server from the VMM, and add it back in, which automatically reinstalls the agent. After this was done, all was back to normal. 

    This doesn't sound like something we would want to be doing once we get 50+ servers in our VMM. Seeing we have seen this on 4 out of 6 Windows update installation cycles, we think we must be doing something wrong and hopefully, somebody in this forum will be able to point us in the right direction?

    ========================================

    Faulting application name: vmmAgent.exe, version: 4.1.3403.0, time stamp: 0x5b33b02b
    Faulting module name: vmmAgent.exe, version: 4.1.3403.0, time stamp: 0x5b33b02b
    Exception code: 0xc0000005
    Fault offset: 0x0000000000165d05
    Faulting process id: 0xbfc
    Faulting application start time: 0x01d5230935694961
    Faulting application path: C:\Program Files\Microsoft System Center\Virtual Machine Manager\bin\vmmAgent.exe
    Faulting module path: C:\Program Files\Microsoft System Center\Virtual Machine Manager\bin\vmmAgent.exe
    Report Id: 0a0ef5c5-8507-4dd3-b802-20b181f46aa1
    Faulting package full name: 
    Faulting package-relative application ID: 

    ================================
    • Edited by Herman Bonnie Thursday, June 20, 2019 7:04 AM It needed more spaces
    Thursday, June 20, 2019 7:03 AM

All replies