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

    Incompatible CPU features on live migrations

    Scheduled Pinned Locked Moved Management
    7 Posts 3 Posters 369 Views 3 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
      jdias14
      last edited by

      Hi,

      A few days ago I was migrating a VM from a PowerEdge R420 to a PowerEdge 1950 and received the following warning:

      c8ab9b9d-03c5-48d3-8583-3c16c9fe0a61-imagem.png

      I understand that those are distinct generations of processors and since they do not support the same instruction sets it is not safe to live migrate VMs between them.

      My question is: is there some kind of compatibility matrix that Xen Orchestra uses from where I can see if the migration is ging to be possible or not?

      Thanks in advance.

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

        Hi,

        It's impossible to have a matrix due to the sheer number of different CPU features for each generation. You can always migrate to "less features" to "more features", the opposite might crash your VM during a live migration. But warm migration can do it for you then.

        In any case, you need to be aware of the CPU diff between pools before migrating and assert from here.

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jdias14 @olivierlambert
          last edited by

          @olivierlambert Ok, thanks for explanation. But then how does Xen Orchestra knows whether the destination host CPU is compatible or not?

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

            IIRC, XO doesn't know, it's a message coming from XCP-ng. It will compare the CPU info between source and destination.

            AlexanderKA 1 Reply Last reply Reply Quote 0
            • AlexanderKA Offline
              AlexanderK @olivierlambert
              last edited by AlexanderK

              @olivierlambert
              i have two pcs with the same cpu and i am receiving this error.
              How i can check what is the issue?

              migrate from

              d5eb95c5-2728-48e9-89b2-674f0844cfb9-image.png

              To

              d221081f-af11-4e4c-9608-c7f4e53570b2-image.png

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

                You need to compare the CPU features visible on each host.

                Either: compare the output of xe host-param-get uuid=<UUID> param-name=cpu_info param-key=flags on both hosts, or xl info.

                AlexanderKA 1 Reply Last reply Reply Quote 1
                • AlexanderKA Offline
                  AlexanderK @olivierlambert
                  last edited by

                  @olivierlambert
                  can memory size difference being showed as different cpu?
                  tried both commands

                  Screenshot 2025-01-22 005049.png

                  Screenshot 2025-01-22 005412.png

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