none
Virtual Machine Settings delay +10 minutes to show attributes

    Question

  • A chyper-v cluster that actually has 6 nodes, all of them with Graphical WIndows Server 2012 R2 Datacenter.

    After adding a node to the cluster, VM takes more than 10 minutes to show settings, even if the virtual server is not on cluster.

    I created a vm without vhd into c:\ and the problem persists.

    The problem doesn´t happen if i remove the node from the cluster. 

    after adding again the node to the cluster, the problem happens again. 

    There are no errors in event viewer that i could relate to that problem . 

    Any suggestion how to troubleshoot this problem?

    Thanks in advance.

    FM

    Thursday, February 16, 2017 5:57 PM

Answers

All replies

  • First thing to do is the run the cluster validation wizard against the cluster.  Errors are obvious - they have to be fixed.  Warnings and informational messages each need to be examined.  If you do not have a logical explanation for why the warning message or information message shows up, there is a chance that you might need to change something in your cluster.

    Yes, you can run the validation wizard on a running Hyper-V cluster.  You just need to be selective in the tests you run.  For the storage tests, you do not want to run storage tests on all storage as that will cause VMs to fail back and forth.  If you have a disk witness, only select that as a target for the storage tests.  If you do not have a disk witness, create another volume that is configured the same as the other volumes in your cluster (you don't need it the same size), so the storage tests are working against something that looks like everything else.


    . : | : . : | : . tim

    Thursday, February 16, 2017 9:32 PM
  • OBS.:

    We don´t have VMM managing that cluster.

    Cluster Validation with no errors. 

    Cluster migrated from Windows 2008 R2 with more than 100 VMs.

    Friday, February 17, 2017 4:42 PM
  • Hi,

    >>The problem doesn´t happen if i remove the node from the cluster. 

    after adding again the node to the cluster, the problem happens again

    I'm afraid I could not find any related information about this phenomenon.

    I would suggest you try to perform a reinstallation to see if still the same.

    Also check if the device is certified:

    https://www.windowsservercatalog.com/

    Best Regards,

    Leo


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

    Tuesday, February 21, 2017 1:57 AM
    Moderator
  • Hi,

    Are there any updates?

    You could mark the reply as answer if it is helpful. 

    Best Regards,

    Leo


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

    Thursday, March 09, 2017 12:19 PM
    Moderator
  • KB3087856 + reboot
    Monday, May 29, 2017 8:53 PM