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

    NOT_SUPPORTED_DURING_UPGRADE() When Creating Or Editing VMs

    Scheduled Pinned Locked Moved Management
    solved
    7 Posts 3 Posters 28 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.
    • B Offline
      bonzo
      last edited by bonzo

      Hi,
      I recently upgraded my server from 8.2.1 to 8.3 and then ran updates for XO. All my existing VM's work fine and most other functions in xsconsole and XO seem OK as well.
      However, if I try to create a new VM or make changes to an existing VM, I get the above error message. I'm sure I'm missing something elemental but any help would be great.

      Thanks,
      Eric

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

        have you upgraded all your hosts in the pool?

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bonzo @olivierlambert
          last edited by

          @olivierlambert AH! Great question. I no longer have but one actual host in the pool but have not been able to remove the remnants of the "ghost" hosts, no matter what I try. There are also a couple of VMs that had been running on those old hosts that I think are preventing me from removing the old hosts.
          Unfortunately, I did not get a chance to remove the hosts properly before they were physically gone from my possession so I can't rectify that by booting them up and going through the proper process.
          I suppose I need to know the CLI commands and order for which to manually remove them before I proceed?

          Thanks

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

            You need to "forget" those hosts first.

            B 1 Reply Last reply Reply Quote 0
            • B Offline
              bonzo @olivierlambert
              last edited by

              @olivierlambert I was able to do that for one of them, via XO. However, the other two hosts there are two VM's that were running the last time the hosts were online and now I'm in a catch 22 where i can't shut down the hosts without stopping the VM's but when I try to send a command to manually stop the VM's, it says it couldn't contact the host.

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

                Have you tried resetting the VM's power state?

                xe vm-reset-powerstate uuid=<UUID_of_the_VM> --force

                B 1 Reply Last reply Reply Quote 0
                • B Offline
                  bonzo @Danp
                  last edited by

                  @Danp THANKS! That did the trick. I was able to clean up after doing that. Thanks so much!

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