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

    CANNOT_EVACUATE_HOST VM_REQUIRES_SR

    Scheduled Pinned Locked Moved Xen Orchestra
    7 Posts 4 Posters 1.7k 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.
    • tsettleT Offline
      tsettle
      last edited by

      I seem to be missing something, and Google is telling me there aren't any great matches. After scrolling through a few pages of results, I agree.

      When starting the rolling update or trying to put a host into maintenance mode, I get these errors.

      I can migrate VMs manually, so not quite sure what I'm missing or how to begin to troubleshoot this.

      Thanks.

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

        Do you have HA enabled?

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

          Hi,

          You need a shared SR (and a default one set).

          1 Reply Last reply Reply Quote 0
          • N Offline
            NielsH
            last edited by NielsH

            The rolling pool upgrade only works when you're using shared storage sadly.

            We're also using local storage (for disk io performance reasons) and when performing updates it still takes like an entire day for us to do so (about 15 hosts with ~200VMs).
            It is possible to script it though with xo-cli, i.e. what we do now is get a list of all VMs on a host, iterate over it and for each vm we run xo-cli vm.migrate with a predetermined targetHost and to the default SR on that host.

            It's not fully unattended but with a few variables (what host to evacuate and where to evacuate to) at least we can empty each host automatically and just check it a few hours later once it is empty to reboot.

            We'll probably improve the script later to reboot the host as well and once it is back online migrate all VMs back. Then after that we can just do that for every host in the pool to have our own rolling-pool-upgrade script.

            Would still prefer to have it through the interface, but we contacted support a few weeks ago and they said there were no plans to support this (rolling pool upgrades with local SR) anytime soon.

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

              Doing that automatically is possible, but prone to errors (migrating with the disk is VERY complicated because you have to check the destination SRs and "compute" the free space for all migrations, which is very hard). BTW, XAPI got indeed the host.evacuate method for live migration, that's what XO calls.

              I think if there's enough traction to do it, we could, but I would consider it relatively risky for your running VMs.

              tsettleT 1 Reply Last reply Reply Quote 0
              • tsettleT Offline
                tsettle @olivierlambert
                last edited by

                The deeper I go, the more I learn. Thanks for the straight forward answers!

                When I'm done with my migration from Hyper-V, we'll have just 4 hosts, so doing it all manually isn't a huge issue.

                Is this something that XOSAN would resolve?

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

                  More or less yeah, but you are adding more moving pieces.

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