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

    Understanding CPU Masking

    Scheduled Pinned Locked Moved Compute
    3 Posts 3 Posters 57 Views 4 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.
    • mauzillaM Offline
      mauzilla
      last edited by

      We want to add a new member to our pool (existing Dell range). Logically I want to add a newer "range" to the pool, but my understanding is that the pool will mask CPU features to whatever the lowest CPU member is in the pool. Given that the other hosts are a generation older, does this then mean the newer generation CPU would effectively be "watered down" to match that of the rest of the pool?

      Likewise, adding an older generation to the pool would have the same affect, moving the entire rest of the pool to the lowest denominator?

      1 Reply Last reply Reply Quote 0
      • bleaderB Offline
        bleader Vates 🪐 XCP-ng Team
        last edited by

        ping @Team-Hypervisor-Kernel

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

          Hi,

          Yes, by default, adding a new host to a pool, it will be lowered on CPU features to the common denominator, in other word, cutting that's not common between all pool members.

          So:

          1. If you add a more recent CPU to an existing pool, the CPU won't use new CPU features
          2. If you add an older host to a pool, it will lower down all features from existing CPUs
          1 Reply Last reply Reply Quote 0
          • First post
            Last post