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

    Host CPU and Max vCPU on VM

    Scheduled Pinned Locked Moved Solved Compute
    14 Posts 5 Posters 7.9k 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.
    • nmymN Offline
      nmym
      last edited by

      Hello

      I'm not sure if this is the correct place to post, but
      I have a server running amd epyc 7402P with 48 threads (24 cores).
      When I install xcp-ng, my host get 16 threads. Is this normal? or another question would be, is it necessary?(atm I'm running a clean install. no zfs etc)

      And on my guests I cannot choose more than 32 vCPU's, is this somewhat related or just a xcp-ng limitation?

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

        You can't use more vCPU than you have physical CPUs:

        1. When it was possible, it would actually reduce VM performance (because Xen will have to schedule on a smaller number of physical cores and it's not free)
        2. Due to Spectre/Meltdown things, it was enforced to NOT create (ever) a VM with more vCPUs than cores.
        B 1 Reply Last reply Reply Quote 0
        • ruskofdR Offline
          ruskofd
          last edited by

          There is indeed a limitation described here concerning the maximum number of vCPU per VM :
          https://docs.citrix.com/en-us/citrix-hypervisor/system-requirements/configuration-limits.html

          1 Reply Last reply Reply Quote 0
          • R Offline
            r1 XCP-ng Team
            last edited by

            You could be able to set more vCPUs via CLI xe or XOA. What client interface are you using?

            1 Reply Last reply Reply Quote 0
            • ruskofdR Offline
              ruskofd
              last edited by

              I heard some issues on a French Discord about a guy who tried to allocate more than 64 vCPU on a Windows VM and he had constants BSOD. So, 32 vCPU should be fine I guess.

              1 Reply Last reply Reply Quote 0
              • nmymN Offline
                nmym
                last edited by

                Thank you both @ruskofd and @ruskofd

                FYI I used the XCP-NG Manager, did not try to add more vCPUs through xe

                1 Reply Last reply Reply Quote 0
                • ruskofdR Offline
                  ruskofd
                  last edited by

                  Have you tried XenOrchestra ? It removes some dumb limits (without further problems), and I guess you can set more than 32 vCPU without using CLI.

                  nmymN 1 Reply Last reply Reply Quote 0
                  • nmymN Offline
                    nmym @ruskofd
                    last edited by

                    @ruskofd Ty
                    Don't have it yet, I'm just running alot of tests back to back. Will probably not need more than 32 vCPU but was just curious why I could only select 32. If it's only a xcp-ng manager problem, then it's all good 🙂

                    1 Reply Last reply Reply Quote 0
                    • ruskofdR Offline
                      ruskofd
                      last edited by

                      Yes, 32 vCPU is for very specific use cases. So, enjoy your experience 😊

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

                        You can indeed set more than 32vCPU in Xen Orchestra 🙂

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

                          @olivierlambert Dear Sir,

                          i have notice that vcpus assignment has to be the maximum number of cores available, for example 4 core cpu, we can have VM's with 1-2-3-4 vcores.

                          When over assign vcores, for example assign 16vcores on 4 core cpu, we have the error :

                          "errors": [
                          "localhost: HOST_NOT_ENOUGH_PCPUS(16, 4)"
                          [no problem on that]

                          But after going back to edit the settings and put 2vcores,

                          63523c6d-a419-4445-89ee-67a2c9a904cc-image.png
                          the machine still not booting and return the same error, (16,4), it seems that is not getting the new setting. Is there any step we can do to update the VM settings?

                          f93ab3d2-a3cf-44f5-b268-ad72babd3976-image.png

                          Site note: creation of a new vm with 4 vcore will boot normally !

                          Thanks for your great support. any comments or suggestions appreciated.

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

                            You can't use more vCPU than you have physical CPUs:

                            1. When it was possible, it would actually reduce VM performance (because Xen will have to schedule on a smaller number of physical cores and it's not free)
                            2. Due to Spectre/Meltdown things, it was enforced to NOT create (ever) a VM with more vCPUs than cores.
                            B 1 Reply Last reply Reply Quote 0
                            • B Offline
                              Bambos @olivierlambert
                              last edited by

                              @olivierlambert yes, agree with everything ! thank you.

                              the question is why XOA not taking the new setting for the 2 vCPU's ?

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

                                Check the max vCPU settings in Advanced tab of the VM.

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

                                  @olivierlambert thank you Olivier. Indeed you are right, we need to change also the max vcpu limits in advanced.

                                  0cc87b88-9234-4671-bf18-4280acd996cd-image.png

                                  Then is booting normally.

                                  1 Reply Last reply Reply Quote 0
                                  • olivierlambertO olivierlambert marked this topic as a question on
                                  • olivierlambertO olivierlambert has marked this topic as solved on
                                  • First post
                                    Last post