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

    migrate xen orchestra vm itself failed

    Scheduled Pinned Locked Moved Management
    4 Posts 2 Posters 477 Views 2 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.
    • T Offline
      tbuijvoets
      last edited by

      Hi all,

      I wanted to remove a host from my xen orchestra install. The only vm on this host was xen orchestra itself. I wanted to migrate it to another host. So I used the built-in migrate function in XO.

      For a long time the migrate was stuck on 89%. Later I lose the connection to it. Also a ping is not working. I looked in my router and also there was no arp anymore. So the whole vm is not on the network anymore. What it's state is, I'am not sure.

      When I run:
      xe vm-list on the original host I see the vm still in running state.

      When I run:
      xe vdi-list on the new destination host I don't see the new disk for it

      Then I tried to stop the current vm on the original host with command:
      xe vm-shutdown vm=xen\ orchestra force=true
      I get an error stating:
      The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Object with type VM and id b3b0ba0b-6534-1935-23fa-c512591debd0/config does not exist in xenopsd

      Has anybody an idea how I can recover my xen orchestra vm.

      If possible I want to fix the current vm. If needed, I have full vm backup and xo config backup from the xen orchestra vm. I can restore them but I have created new vm's after the backup. What will happen to the newly created vm's?

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        You entered a case where the migration failed (we are pushing a fix in XAPI to gracefully fail and get the original VM back online instead of this "limbo" state. The VM is likely dead is reality despite XAPI thinking it's not. You need to do a VM power reset with xe vm-reset-powerstate uuid=<uuid_of_vm> force=true.

        T 1 Reply Last reply Reply Quote 0
        • T Offline
          tbuijvoets @olivierlambert
          last edited by

          @olivierlambert

          Thank you!

          I fixed it prior to your reply by rebooting the host where the vm was. This also fixed the problem.

          Is it even possible to migrate the XO vm when it is initiated from the same XO vm?

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Yes, it should work if the migration doesn't fail 🙂 It's hard to know exactly why it failed in your case, but it's unrelated on being XO VM.

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