none
2016 Server Hyper-V Reverts to .XML files after joining a cluster RRS feed

  • Question

  • Has anyone else noticed a behavior in Windows Server 2016 that it reverts to using the old format .XML files for VM configurations after joining a cluster? In this case the cluster was 2012R2 functional level which may affect it?

    The problem we're having is that we had some local VMs on the machines and as soon as the servers joined the cluster, the running machines disappeared from all management. They are still running strangely enough, but they no longer show in Get-VM or in Hyper-V manager. 

    So, I RDP into one of them and shut it down and tried to re-import it, but 2016 would not even let me re-import it with the VMCX configuration files, it said 'No Virtual Machines Found' in that folder. I had to re-create it, attached the VHDX and it created the old style XML files.

    I'm wondering if maybe this has to do with the functional level, but all the VMs on the cluster have XML files, even ones created with 2016, so I'm thinking it might just be intentional?

    Anyone seen this behavior?

    Thanks!

    Sunday, November 17, 2019 4:46 AM

All replies

  • Hi,

    Thank you for posting in forum!

    1.Please provide me with more details:

    How many nodes are there in the failover cluster? What are their OS versions?

    2.If all nodes are Windows 2016 Servers, I recommend you to upgrade the cluster to Windows Server 2016 using Cluster OS Rolling Upgrade.

    For more information about Cluster operating system rolling upgrade, please refer to: https://docs.microsoft.com/en-us/windows-server/failover-clustering/cluster-operating-system-rolling-upgrade

    3.By the way, we don’t recommend the failover cluster run in mixed-OS mode for a long time.

    Hope this can help you. Please let us know if you would like further assistance.

    Best Regards,

    Lily Yang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 18, 2019 8:09 AM
  • Hyper-V 2012 does not understand the VMCX file format.  So if you want to be able to manage virtual machines, they must be configured with the XML format.

    tim

    Monday, November 18, 2019 1:39 PM
  • Hi,

    Just checking in to see if the information provided was helpful. 

    Please let us know if you would like further assistance.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 20, 2019 1:23 AM
  • Hi,

    Was your issue resolved? 

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Lily

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 22, 2019 1:39 AM