It makes no real sense to set the maximal allowed value to the total
count of VM cores as this setting controls how much Host CPU time the
whole KVM/QEMU instance can get. This instance does not only contains
the VMs CPU threads but also threads for networking, block IO,
migration, ...
So it can make sense to set more host CPU time than just the guest
CPU processes could get.
Signed-off-by: Thomas Lamprecht <t.lampre...@proxmox.com>
---
no changes
www/manager6/qemu/CPUOptions.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/www/manager6/qemu/CPUOptions.js b/www/manager6/qemu/CPUOptions.js
index 3cadf226..c1554f34 100644
--- a/www/manager6/qemu/CPUOptions.js
+++ b/www/manager6/qemu/CPUOptions.js
@@ -30,10 +30,10 @@ Ext.define('PVE.qemu.CPUOptionsInputPanel', {
xtype: 'numberfield',
name: 'cpulimit',
minValue: 0,
- maxValue: me.maxvcpus,
+ maxValue: 128,
value: '',
step: 1,
- fieldLabel: gettext('CPU limit'),
+ fieldLabel: gettext('Host CPU time'),
allowBlank: true,
emptyText: gettext('unlimited')
},
--
2.11.0
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
