none
Server 2012 Gen 2 VM hosted on Server 2012 R2 Hyper-V Host incompatible with Integration Services after Windows update

    Question

  • If you take a Server 2012 R2 Host and update it, and then setup a Server 2012 and 2012 R2 Virtual Machines on it with the latest Integration Services.  Setup SR-IOV on both VMs.  Everything will be ok in the Integration Services status, but when you update the Virtual Machines, the Server 2012 R2 will continue to report that it's up to date.  But the 2012 will show that it needs it's Integration Services updated, when it's already running the latest Integration Services.  I'm not sure which update it is that is causing the conflict, and don't have the time to install 60 of them 1 by 1 to figure it out. 
    Saturday, November 16, 2013 9:20 AM

Answers

  • Yes, we have identified this as a benign state reporting bug and can safely be ignored (although you should ensure the ICs are in fact up to date regardless - if SR-IOV is disabled at guest startup, the state will be correctly reported). It only occurs when using a Windows Server 2012 guest on a Windows Server 2012 R2; the guest has SR-IOV enabled and active; and the guest is started/restarted. It has nothing directly to do with updates, it's the restart that the updates caused. We're working on a KB and identifying a possible fix.

    ________________________

    John Howard, Senior Program Manager, Hyper-V Team, Microsoft Corporation.
     This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.

    Thursday, November 21, 2013 7:41 PM

All replies

  • I did a little testing this weekend, and I can say that the incompatibility and incorrect report that the tools need updating happens after the second round of updates that S2012 shows as available.  So the first 60 updates are ok, but then the next round of updates are the ones that cause the incompatibility.  Why would MS updates be incompatible with their own integration services?  
    Monday, November 18, 2013 3:50 AM
  • Hi ,

    According to your description , if you uninstall the second round of updates the 2012 VM will be ok ?

    May be you can try to update your host first ,then update VMs.

    Any further information , please fell free to  let us know.

    Best Regards

    Elton Ji


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.


    Tuesday, November 19, 2013 4:36 PM
  • We're working on investigating this along with your report on my blog.

    ________________________

    John Howard, Senior Program Manager, Hyper-V Team, Microsoft Corporation.
     This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.

    Tuesday, November 19, 2013 9:15 PM
  • Yes, we have identified this as a benign state reporting bug and can safely be ignored (although you should ensure the ICs are in fact up to date regardless - if SR-IOV is disabled at guest startup, the state will be correctly reported). It only occurs when using a Windows Server 2012 guest on a Windows Server 2012 R2; the guest has SR-IOV enabled and active; and the guest is started/restarted. It has nothing directly to do with updates, it's the restart that the updates caused. We're working on a KB and identifying a possible fix.

    ________________________

    John Howard, Senior Program Manager, Hyper-V Team, Microsoft Corporation.
     This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.

    Thursday, November 21, 2013 7:41 PM
  • Thank you for your attention and care regarding this issue John!  Great job in supporting us.  
    Sunday, November 24, 2013 7:59 AM