Bug 1153765 - migration to target host does not consider memory usage
Summary: migration to target host does not consider memory usage
Keywords:
Status: CLOSED EOL
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-16 17:41 UTC by Markus Stockhausen
Modified: 2022-03-16 08:58 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-02 10:38:42 UTC
oVirt Team: SLA
Embargoed:


Attachments (Terms of Use)
log (81.53 KB, image/png)
2014-10-16 17:47 UTC, Markus Stockhausen
no flags Details
memory (66.22 KB, image/png)
2014-10-16 17:47 UTC, Markus Stockhausen
no flags Details
swap (26.77 KB, image/png)
2014-10-16 17:47 UTC, Markus Stockhausen
no flags Details
cpu (45.10 KB, image/png)
2014-10-16 17:48 UTC, Markus Stockhausen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45328 0 None None None 2022-03-16 08:58:30 UTC

Description Markus Stockhausen 2014-10-16 17:41:40 UTC
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.

Comment 1 Markus Stockhausen 2014-10-16 17:47:00 UTC
Created attachment 947717 [details]
log

Comment 2 Markus Stockhausen 2014-10-16 17:47:21 UTC
Created attachment 947718 [details]
memory

Comment 3 Markus Stockhausen 2014-10-16 17:47:39 UTC
Created attachment 947719 [details]
swap

Comment 4 Markus Stockhausen 2014-10-16 17:48:00 UTC
Created attachment 947720 [details]
cpu

Comment 5 Markus Stockhausen 2014-10-16 18:11:37 UTC
sorry got a typo in my bug report: it is always colovn03 and not colovn02 like in 4)

Comment 6 Sandro Bonazzola 2015-01-21 16:08:03 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 7 Martin Sivák 2015-07-15 09:57:16 UTC
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?

Comment 8 Sandro Bonazzola 2015-09-04 08:58:36 UTC
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.

Comment 9 Sandro Bonazzola 2015-10-02 10:38:42 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.