This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
VM CPU and Memory Allocation
When you create a new VM, you can allocate virtual CPUs, specify the number of cores-per-socket you would like to present to the VM’s vCPUs, and set initial memory resources to the new VM. You can change the settings at anytime after the new VM is created.
The vCPU hotplug feature in XenCenter enables customers to dynamically increase the number of vCPUs assigned to a running Linux VM, without having to restart the VM.
Options
Number of vCPUs
(for Windows VMs)
Enter the number of virtual CPUs (vCPUs) you would like to allocate to the new VM.
To ensure you get the best performance out of the new VM, the number of vCPUs you assign to the VM should not exceed the number of physical CPUs on the server.
Note:
This value can be changed later, if needed. For more information, see Change VM properties: CPU. For information about the maximum number of vCPUs supported on a VM, refer to the XenServer Configuration Limits document.
Maximum number of vCPUs
(for Linux VMs)
Select the maximum number of virtual CPUs (vCPUs) you would like to allocate to the new VM from the drop-down list.
To ensure you get the best performance out of the new VM, the maximum number of vCPUs you assign to the VM should not exceed the number of physical CPUs on the server.
Note:
This value can be changed later, if needed. For more information, see Change VM properties: CPU.
Topology
Specify the topology for the vCPU.
By default, XenServer allocates one core per socket for each vCPU. For example, allocating 4 vCPUs will appear as 4 sockets with 1 core per socket. Click the Topology drop-down list to change this setting and select an option from the list.
Note:
The cores-per-socket setting depends on the number of sockets present on the server and the operating system installed. Some operating systems have restrictions on the number of CPUs. You should comply with the operating system requirements when setting this option.
Initial number of vCPUs
(for Linux VMs)
This option displays the initial number of vCPUs allocated to the VM. By default, this number is equal to the Maximum number of vCPUs set in the previous step. You can select from the drop-down list and modify the initial number of vCPUs allocated to the VM.
Memory
Enter the amount of memory you want to allocate to the VM.
The XenServer templates provide typical VM configurations and set reasonable defaults for the memory, based on the type of guest operating system. You should also take into account the following considerations when deciding how much memory you initially allocate to a new VM:
- The kinds of applications that will run on the VM.
- Other virtual machines that will be using the same memory resource.
- Applications that will run on the server alongside the virtual machine.
You can adjust the memory allocation after the new VM is created on the VM’s Memory tab, where you can also enable Dynamic Memory Control (DMC) to allow dynamic reallocation of memory between VMs in the same pool. See the Help topics in the Configuring VM memory folder for details.
VM Power State Scenarios
The following table lists the three VM power states and describes their various vCPU scenarios.
VM Power State | Maximum Number of vCPUs | Initial number of vCPUs | Current number of vCPUs |
---|---|---|---|
Running | Cannot be increased/decreased | N/A | Can only be increased. |
Shutdown | Can be increased/decreased | Can be increased/decreased | N/A |
Suspended | Cannot be modified | N/A | Cannot be modified |
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.