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

    1 core per socket (Invalid configuration)

    Scheduled Pinned Locked Moved Compute
    4 Posts 3 Posters 498 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.
    • M Offline
      msteini
      last edited by

      I facing a "Invalid configuration" message in xcp-ng center when i deploy a vm with the following cpu settings:

      19d0a778-bee2-4ebe-bdf5-14f4f509bad5-grafik.png

      If the VM is down i got the following error in the properties section:

      acd2dbed-af5c-4a5b-8358-6f9d23d84b1d-grafik.png

      Message in XCP-ng under "General -> CPUs":

      d529d150-4dde-4598-8780-6cffd93d3b75-grafik.png

      I can reproduce this in two environments:

      1. XCP-ng Cluster Version 8.2
      2. Cloudstack 4.17.2 with XCP-ng Version 8.2

      The VMs are running and on the command line in the VM i can see all 24 Cores.

      Is there any known issue or limitation with that?

      Thank you!

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

        Hi,

        XCP-ng Center isn't a supported client for XCP-ng. Try to reproduce to XO so we can understand if it's the client or a host issue. Thanks!

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          msteini @olivierlambert
          last edited by

          @olivierlambert

          Thank you for your feedback. I checked it in xoa. If i take a look at the VM with 24 cores in advanced tab -> "VM limits", it shows the following:

          7c42a1b8-7ca0-4989-acb0-d271151176af-grafik.png

          If i take a look for example at a VM with 8 Cores, it looks like this:

          51c847b6-f373-4adf-885f-58d5d98d5ba1-grafik.png

          What does under VM limits ->Topology "Default behavior" mean at the VM with 24 core?

          Thanks!

          1 Reply Last reply Reply Quote 0
          • A Offline
            andyhhp Xen Guru
            last edited by

            You're trying lie to the VM and tell it that it's running on a system with 24 physical sockets, each with a single core.

            For reference, 2 sockets is the biggest AMD server that you can buy (these days), and Intel top out at 8. If you want a larger system, you could buy a SuperDome which can manage up to 32 sockets (before hitting other limits of UPI switching).

            The various historical enumeration schemes can't encode that high, which is why there's a sanity check in XenCenter.

            You typically want 1 socket, so select 24 cores / socket.

            ~Andrew

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