locked
Hyper-V Cluster 2012 shows VM's in a saved state RRS feed

  • Question

  • Hello, I have a 5 node hyper-V cluster setup. All nodes are running Windows 2012.  We had an issue with one of nodes wherein we couldnt live migrate any VM's to that node. A cold/quick migration would however go thru successfully to that node. 

    What i am seeing is, The Hyper-V manager on this node shows couple of VM's in a SAVED state.  But if i check in "Failover Cluster Manager" this node is not holding the roles of these 2 VM's.  The cluster manager correctly shows other nodes as the owner of these VM's.   Is there any way to remove / clear the Saved VM's from Hyper-V settings of this node ?


    • Edited by Neeraj_Shah Thursday, September 5, 2013 8:34 PM
    Thursday, September 5, 2013 7:16 PM

Answers

  • Hi,

    According to your description, the issue may be due to the wrong operation during the migration process.

    Did you perform a quick migration that two VMs to that node?

    Based on my experience, a quick migration needs the VM in a closed state.

    Best regards,

    Susie Long

    • Marked as answer by Susie Long Friday, September 13, 2013 2:03 AM
    Friday, September 6, 2013 1:03 PM
  • OK you were tying to do a quick migration and the machines stuck in saved state, you have two options if you don't want the saved state you can right click and delete the saved state, or you can right click and start the machine back up, deleting the saved state is like pulling the plug on a physical server. once the state is off you can also turn it back on.

    so yes deleting the saved state will clear the state to off and either saved or off you should be able to start it up.

    if you have some machines that will not migrate look here

    http://social.technet.microsoft.com/Forums/windowsserver/en-US/4a5814e4-5579-4c51-954a-cf56fc05331c/hyperv-2012-live-migration-fails-with-event-id-21502#1cfc8426-c80c-412b-8eb3-6513806a88bc

    • Proposed as answer by Susie Long Tuesday, September 10, 2013 3:21 AM
    • Marked as answer by Susie Long Friday, September 13, 2013 2:03 AM
    Friday, September 6, 2013 5:18 PM
  • I found it expedient to shut down VMs briefly when moving them to another server. This way the file move of the VHD is faster (assuming the use of local storage)

    if you are using a storage box for the VHDX files, then there is no need to shut them down.


    Corsair Carbide 300R with window & Corsair TX850V2 70A@12V

    Asus M5A99FX PRO R2.0 CFX/SLI & AMD Phenom II 965 C3 Black Edition @ 4.0 GHz & G.SKILL RipjawsX DDR3-2133 8 GB 

    GTX 260 SLI 216 core (GT200 Tesla) & Asus PA238QR IPS LED HDMI DP 1080p

    ST2000DM001 & Windows 8.1 Enterprise x64

    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!


    Hardcore Games Legendary is the Only Way to Play

    • Proposed as answer by Susie Long Tuesday, September 10, 2013 3:19 AM
    • Marked as answer by Susie Long Friday, September 13, 2013 2:03 AM
    Monday, September 9, 2013 5:49 PM

All replies

  • right click VM you should see remove saved state...
    Thursday, September 5, 2013 8:37 PM
  • Hi,

    According to your description, the issue may be due to the wrong operation during the migration process.

    Did you perform a quick migration that two VMs to that node?

    Based on my experience, a quick migration needs the VM in a closed state.

    Best regards,

    Susie Long

    • Marked as answer by Susie Long Friday, September 13, 2013 2:03 AM
    Friday, September 6, 2013 1:03 PM
  • @ Susie, yes you are correct, it was due to quick migration without shutting down the VM's. Curious , Where does MS says that VM's need to be shutdown during live migration.  I couldn't find any such best pratice article.  .  Thanks for the reply.

    @ Darren, thanks again but after doing a "Delete State" , the VM's show in an "OFF" state.   Do i need to right click the VM and delete it again ?

     
    Friday, September 6, 2013 2:19 PM
  • OK you were tying to do a quick migration and the machines stuck in saved state, you have two options if you don't want the saved state you can right click and delete the saved state, or you can right click and start the machine back up, deleting the saved state is like pulling the plug on a physical server. once the state is off you can also turn it back on.

    so yes deleting the saved state will clear the state to off and either saved or off you should be able to start it up.

    if you have some machines that will not migrate look here

    http://social.technet.microsoft.com/Forums/windowsserver/en-US/4a5814e4-5579-4c51-954a-cf56fc05331c/hyperv-2012-live-migration-fails-with-event-id-21502#1cfc8426-c80c-412b-8eb3-6513806a88bc

    • Proposed as answer by Susie Long Tuesday, September 10, 2013 3:21 AM
    • Marked as answer by Susie Long Friday, September 13, 2013 2:03 AM
    Friday, September 6, 2013 5:18 PM