Developers of Xen Orchestra
@Greg_E The RPU is supposed to disable the load balancer, but it's possible that when the load balancer restarts at the end of the RPU, it takes into account the host stats during the RPU, which may create some unexpected migrations.
We'll have to investigate on that. Thanks for the feedback.
@acebmxer at the moment I don't know what could cause this behaviour. I'll try to reproduce it during the following days.
I think setting the memory limit to half of the host RAM is fine if you don't expect too much load, but if you're getting a lot of RAM use on your hosts at some point, I'm not sure the load balancer will migrate VMs from a host at 90% RAM use to a host at 60% RAM use, as both exceed the limit.
Also, could you try again to reproduce the bug after changing the "performance plan behaviour" setting to conservative, to see if it changes something? The "vCPU balancing" mode is quite recent, so maybe there's some bug with it that we didn't discover yet.
@akihu2 Perfect, thanks.
Yes, you can close this topic
Here is the fix for the REST API + XO6
https://github.com/vatesfr/xen-orchestra/pull/9591
@akihu2 Hi.
It appears to be a bug, as the XO6 UI offers the option to choose the number of VCPU when creating a VM (obviously, this doesn't work).
I will fix this immediately.
@MajorP93 we merged a lot of changes yesterday , so it's on master
it clean more aggressively the task log, and more cleanup after backup; We are still looking for other possibilities , but for now it's our best bets
@ElFritto can you do a yarn && yarn build at the root of xen-orchestra ?
edit : found it, we will do a patch
@deligatedgeek we will try to push this branch to master before the end of the month
(we will have a lot of documentation to write on what is solves and what it don't solves)
@flakpyro thanks for the test
we are preparing a branch with some performance improvement , hopefully this time we found the right cause
