From 8b6696bf7b59e8d223ac04ca2bcf9ad73ecdfda3 Mon Sep 17 00:00:00 2001 From: Olivier Lambert Date: Wed, 11 Nov 2015 18:33:50 +0100 Subject: [PATCH] Update administration.md --- administration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/administration.md b/administration.md index 171710c6f..39e3472c8 100644 --- a/administration.md +++ b/administration.md @@ -86,4 +86,6 @@ To do that: go inside your running VM, then edit the Disk panel. You can change You can edit your VM RAM or CPUs in live, like you edit a VM name or description. But there is some XenServer limitations and configuration not exposed directly in Xen Orchestra: * each VM has a vCPU maximum number. This value can't be change while the VM is running. You can reduce the number of vCPUs, but can't assign more than max. In XO, while your VM is halted, allow the max vCPUs you would need, then boot it. Now you can reduce it and then expand it later to this maximum. -* the same limitation apply for the RAM. \ No newline at end of file +* the same limitation apply for the RAM. + +You can learn more about XenServer resource management here: https://wiki.xenserver.org/XCP_FAQ_Dynamic_Memory_Control \ No newline at end of file