Hi, as explained on the Ovirt workshop there seems to be a bug about calculating the required and avaialbale memory of a target hypervisor before we start a migration. Setup 1) cluster overprovisioning is 140% (for server load) 2) cluster KSM enabled 3) colovn03 Hypervisor: has 24GB physical RAM 4) colovn02 has 3 GB memory used 5) migrate a VM (colvm02) with 14GB RAM (10GB guaranteed) onto hypervisor colovn03 6) migration succeeds 7) hypervisor colovn03 has 18 GB RAM used 8) migrate another VM (colvm53) with 16 GB onto colovn03 9) migration starts 10) colovn03 gets into swapping 11) migration breaks 12) other VMs on host colovn03 are reported as "not repsonding" in ovirt. This should not be possible. Graphs attached.
Created attachment 947717 [details] log
Created attachment 947718 [details] memory
Created attachment 947719 [details] swap
Created attachment 947720 [details] cpu
sorry got a typo in my bug report: it is always colovn03 and not colovn02 like in 4)
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority
Hi, sorry to get to you so late. We have couple of questions: - what was the minimum guaranteed memory configured for colvm53 (the second one) - what caused the 3GB host load?
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant.
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still an issue.