locked
Impossible to live-migrate VMs with .vhdx RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello everyone,

    I have a Windows Server 2012 R2 and a new server with Server 2019.

    I'm trying to live migrate VMs' from Server 2012 R2 to Server 2019 and noticed that VMs with .vhdx fail to be live migrated on the new host. The migration starts and progress until the end (or close to then end ?) of the process and then fail.

    - On the 2012 R2 host, I can see the following error in the eventvwr: "Event 21026 Hyper-V-VMMS - Virtual machine migration operation for SERVER_NAME failed at migration destination SERVER_DST. (Virtual machine ID VM_ID)".

    - On the 2019 host, I can see the following error in the eventvwr: "The absolute path 'C:\Windows\system32\vmguest.iso' is valid for the " ISO Disk Image pool, but references a file that does not exist.

    FYI: The guest OS that we are trying to move are 2008 R2 and 2012 Servers.

    Live migration is enabled on both host and I tried to do it via CredSSP.

    Migration of .vhd is working fine.

    Does anyone have an idea on why this is happening ?

    Thank you very much by advance for the help you can provide.

    Cheers.

    Wednesday, May 8, 2019 2:32 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I know it's a late answer but I can confirm you can't live migrate VMs between these 2 versions. We had to use an intermediary Server 2016 (so 2012 -> 2016 and 2016 -> 2019).

    It's probably due to the fact that Microsoft officially support up to N-2 versions and 2012 is too old to live migrate correctly to 2019.

    Thank you anyway to all of you.

    • Marked as answer by dd-cges Tuesday, October 15, 2019 3:00 PM
    Tuesday, October 15, 2019 3:00 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Remove the ISO that is mapped to the VM and then try to live migrate

    Regards,
    Bala N

    Wednesday, May 8, 2019 2:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Agree with Naathan, looks like your VM has the integration services media mounted. Unmounte the iso file and you should be able to migrate the VM. 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Wednesday, May 8, 2019 6:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I unmounted the media and then tried again.

    The error about the vmguest.iso disappeared but still I can't make the live migration working.

    Here are the errors in the eventvwr:

    On the old host (Server 2012)  at the time the error appeared:
    - Event 21026 Hyper-V-VMMS: "Virtual machine migration operation for VM_SERVER_NAME failed at migration destination DST_SERVER (Virtual machine ID: VM_ID)".

    On the new host (Server 2019) at the time the error appeared:
    - Event 13003 Hyper-V-VMMS: "The virtual machine VM_SERVER_NAME was deleted (Virtual machine ID: VM_ID)"

    I wanted to precise that migration works if I shutdown the VM but we need to be able to use live migration to avoid downtime.
    Live migration worked with VMs that have VHD. Only VMs with VHDX have issues.
    The checkbox "Migrate to a physical computer with a different processor version" is ticked.
    Integration services are installed.

    Does anyone have other clue on how to fix that ?

    Thursday, May 9, 2019 6:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I personally do not recommend using live migration from 2012 R2 to 2019, because there were/are some issues with booting those VM's. The live migration could be successful, but once you restart your VM it might not boot correctly. That is why I would probably recommend using offline migration if that is possible of course. 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Thursday, May 9, 2019 7:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    When doing a quick migration or a migration after shutting down, are you able to power on the VM in the destination host?

    Can you also check the logs in Hyper-V worker in the destination host?

    Regards,
    Bala N

    Thursday, May 9, 2019 8:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I have the following in the Hyper-V-Worker logs:

    "Event 12080 - VM_NAME Microsoft RDV Component (Instance INSTANCE_ID): Failed to restore with Error 'Catastrophic failure0 (0x8000FFFF). (Virtual machine ID VM_ID)."

    @Naathan: for the VMs that I was able to live migrate (the ones with VHD): yes, I could power the VM on. 

    I could potentially go with an offline migration when I will replace the physical servers by the new ones but I'd need to be sure that live migration will work find between to Windows Server 2019 because it is a critical feature for us. Honestly, I'd rather to be able to live migrate between Server 2012 R2 and 2019 if possible.

    Any other ideas on how to do it that way ?

    Regards,

    dd

    Thursday, May 9, 2019 9:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What generation version is the VM that you are not able to migrate? What about the ones that they were migrated? 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Thursday, May 9, 2019 10:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It is generation 1 because they were created on Server 2012 R2.
    This is the same for the migrated VMs.

    Thursday, May 9, 2019 12:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Generation 2 VM's were supported on Windows Server 2012 R2. You can run Get-VM | select name,Generation just to make sure that all VM's are indeed generation 1.

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Thursday, May 9, 2019 12:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Please also check this blog which talked about troubleshooting for Hyper-V Live Migration to see if it helps.

    https://www.altaro.com/hyper-v/troubleshooting-hyper-v-live-migration/

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Highly appreciate your effort and time. If you have any question or concern, please feel free to let me know.

    Best regards,

    Michael

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

    Thursday, May 9, 2019 12:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    @Klemenci: yes, you're right.

    Running that CLI show "generation" column as empty so I assume it's gen 1 but am not sure.

    @Michael: 
    - It's not clustered.
    - I read the article but it didn't help for that case (but thank you anyway).

    [EDIT]

    I wanted to add the below compare-vm result I used in Powershell followed by the Incompatibilites list it listed:

    Message
    ----------
    Virtual machine migration operation for VM_NAME failed at migration destination SRV_DST (Virtual machine ID VM_ID)  MeesageID=21026

    The virtual machine VM_NAME is not compatible with physical computer SRV_DST. MessageID=24000

    Virtual Hard Disk file not found. MessageID=40010
    -----------

    What I find weird here is that CPU are from the same manufacturer and compatibility chekbox is ticked.

    Also I don't understand why it doesn't find the virtual hard disk file.

    • Edited by dd-cges Thursday, May 9, 2019 1:50 PM Added more info
    Thursday, May 9, 2019 1:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is your Windows Server 2019 fully patched? 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Thursday, May 9, 2019 7:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, it is.
    Friday, May 10, 2019 6:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I would recommend trying an offline migration of one of the VM's to see if that works. 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Friday, May 10, 2019 6:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Offline migration works but this is not something we can do with production servers for specific VMs.
    Friday, May 10, 2019 7:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would recommend doing some additional testing to see if it's somehow related to the VM's itself. If possible deploy Generation 1 and 2 test VM's and try to live migrate. Also you could try to migrate a VM with static and dynamic memory if there is any difference. There are also some known issues with network adapters when live migrating to Windows Server 2019, so you could also test without an adapter. This way you might pinpoint the exact VM configuration that you are having issue migrating. 

    Maybe someone else will also have an idea and will reply to the thread. The other options is of course to contact Microsoft Support.

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Friday, May 10, 2019 9:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Here's an article demonstrated Hyper-V virtual machine Live Migration, you could refer it to check if the migration pre-configuration.

    https://www.vembu.com/blog/hyper-v-virtual-machine-live-migration-without-failover-clustering/

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Highly appreciate your effort and time. If you have any question or concern, please feel free to let me know.

    Best regards,

    Michael

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

    Friday, May 10, 2019 10:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I doubt this will help, as he was able to live migrate some VM's. It's more of a migrate issue between Windows Server 2012 R2 and Windows Server 2019.

    PS. I didn't found official statement if Live Migration is supported from 2012 R2 to 2019 directly, I personally do not prefer skipping versions with live migration (Windows Server 2016). 

    Microsoft Certified Professional

    [If a post helps to resolve your issue, please click the "Mark as Answer" of that post or click Answered "Vote as helpful" button of that post. By marking a post as Answered or Helpful, you help others find the answer faster. ]

    Friday, May 10, 2019 10:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote


    @Klemencic: I couldn't find an official statement neither. I agree for the versions but these are the only Server versions I have. I assume it should be possible as some VMs (the ones with VHD) were able to move. Among them, some had dynamic memory and other didn't. I also tried by removing the Network adapter before but same results.

    Friday, May 10, 2019 12:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Sorry for my delay.

    For now, I still couldn't find any clue about your issue. I suspect that VHDX was not supported in this live migration of your current situation. We could try to convert VHDX to VHD, then migrate the VMs with these new VHDs. 

    Please refer to the following article which talked about how to convert VHDX to VHD to see if it works.

    https://virtualizationreview.com/Blogs/Virtual-Insider/2012/10/VHD-VHDX-Hyper-V-3.aspx

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Hope this helps. If you have any question or concern, please feel free to let me know.

    Best regards,

    Michael

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

    Thursday, May 16, 2019 3:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Just want to confirm the current situations.

    Please feel free to let me know if you need further assistance.

    Best regards,

    Michael

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


    Monday, May 20, 2019 9:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    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,

    Michael

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

    Friday, May 31, 2019 7:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I know it's a late answer but I can confirm you can't live migrate VMs between these 2 versions. We had to use an intermediary Server 2016 (so 2012 -> 2016 and 2016 -> 2019).

    It's probably due to the fact that Microsoft officially support up to N-2 versions and 2012 is too old to live migrate correctly to 2019.

    Thank you anyway to all of you.

    • Marked as answer by dd-cges Tuesday, October 15, 2019 3:00 PM
    Tuesday, October 15, 2019 3:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Thanks for your update.

    Highly appreciate your effort and sharing, as it would be very helpful to others who encounters a similar issue.

    Thanks~

    Have a nice day!

    Best regards,

    Michael

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

    Thursday, October 17, 2019 2:39 AM