XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Migrating VM Status

    Scheduled Pinned Locked Moved Management
    4 Posts 2 Posters 279 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J Offline
      jimmymiller
      last edited by jimmymiller

      I'm in the process of live migrating a large VM (~30T) from one host to another. The process had been going smoothly for the last 2 days, but now the task no longer appears in XO. The VM status is showing "Busy (migrate_send)", but the task isn't visible in the XO task list. Is there a timeout in XO for tasks running a long time? Is there a way to actually verify the status of the task and whether the VM is still moving? According to the states, there is still IO on the SR so it appears to still be in progress.

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        There is a default timeout of 24 hours for XAPI tasks. See https://xcp-ng.org/docs/api.html#_24h-task-timeout for details on how to increase this.

        To see the current running tasks, you can issue xe task-list on your XCP-ng host.

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jimmymiller @Danp
          last edited by

          @Danp

          Hrm. xe task-list is showing nothing, but there is clearly something still happening based on the stats.

          Screenshot 2024-06-19 at 11.47.39.png

          1 Reply Last reply Reply Quote 0
          • J Offline
            jimmymiller
            last edited by

            Well I guess that was the coalesce process because now that one has just stopped. Any ideas on how to find out why it worked fine for essentially 2 days then stopped?

            I get the impression a live migration of a 30T VM may not be the best way to go about moving something of this size between pools? Maybe a warm migration will work better, but I'm also curious how much capacity we're going to need on the source in order to complete this move.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post