First mitigation was to edit "agent.conf" and add the
host.cpu.manual.speed.mhz - option manually.
So the hosts are availeable for migration purposes.
So actually the warning " [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) (logid:44ab098e) Couldn't retrieve free
memory, ret
Okay, seems even worse imapacts
It seems the values for CPU_Speed are now getting wrong and impacting the
overall allocation... i have 4 identical servers here and all are shown
with different CPU Speed in the CS Management.
Seems like the reported CPU speed for the agent is currently the "liv
Hi,
after upgradeing our CS agents to 4.17 we see in our logfiles some errors
and warnings.
Hosts are running ubuntu 20.04 - latest patches applied.
First:
After start / restart of the Agent we are getting errors that the Agent
can't get the CPU values:
2022-08-28 13:36:51,849 INFO [utils.linux.
Hi everyone,
faceing some challanges again after upgradeing to 4.17.
Did as explained in the docs.
Afterwards I am now not able to migrate system VMs to different hosts.
Getting the error
"Exception during migrate: org.libvirt.LibvirtException: Cannot access
storage file '/usr/share/cloudstack-co
