Am 09.01.19 um 12:51 schrieb Michal Skrivanek:
On 9 Jan 2019, at 11:12, Lucie Leistnerova <lleistne@redhat.com> wrote:
Hi Matthias,
On 1/9/19 10:13 AM, Matthias Leopold wrote:
Hi,
when a user is managing a "higher number" (couldn't find the exact number yet, roughly >10) of VMs in VM Portal and wants to edit a VM he gets a "[Cannot edit VM. Maximum number of sockets exceeded.]" error message in the browser, which I also see in engine.log. I couldn't find the reason for this. I'm using squid as a SPICE Proxy at cluster level. oVirt version is 4.2.7, can anybody help me?
What exactly are you editing by the VM? The error sounds that CPUs number is higher than engine configuration value allows
# engine-config -g MaxNumOfVmSockets MaxNumOfVmSockets: 16 version: 3.6 MaxNumOfVmSockets: 16 version: 4.0 MaxNumOfVmSockets: 16 version: 4.1 MaxNumOfVmSockets: 16 version: 4.2
I don’t think we’re changing topology in VM Portal and so you’re stuck with the restriction in the original template or whatever was set in webadmin. I guess we’re chagning just the sockets? But then..e.g. if the VM has 4cores/socket you could only set 4, 8, 16, up to 64, and there’ sno indication nor validation in the UI, is there?
Thanks, michal
thanks for answers everybody this phenomenon seems indeed to be related to VMs with a "higher" count of vCPUs (topology chosen by oVirt in admin portal when creating VM), now I saw it with VMs with >40 vCPUs. i always thought "sockets" was related to a communication protocol in webUI or engine or something... but the thing is: the user isn't trying to change vCPUs, he only wants to insert a cd and when trying to update the VM for that he gets that error. that is annoying thx matthias