Bug 1114205 - memory overcommitment & vm online migration -> can lead to heavy swap
Summary: memory overcommitment & vm online migration -> can lead to heavy swap
Keywords:
Status: CLOSED DUPLICATE of bug 1093038
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.6.0
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-28 16:21 UTC by Markus Stockhausen
Modified: 2016-02-10 19:42 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-03 15:18:56 UTC
oVirt Team: SLA
Embargoed:


Attachments (Terms of Use)

Description Markus Stockhausen 2014-06-28 16:21:46 UTC
Description of problem:

heavy paging if VM is migrated to target host with less memory available than VM is using

Version-Release number of selected component (if applicable):

ovirt 3.4.2 

How reproducible:

100%

Steps to Reproduce:

- cluster defined with 150% memory overcommitment + ksm enabled
- administrator wants to move a VM to a selected target host
- VM has X GB memory
- Target host has less than X GB free memory
- Due to overcommitment engine allows to move VM to target host

Actual results:

- OVirt starts migrationg VM
- Target host runs out of memory
- paging starts
- Host & VMs stall

Expected results:

- Either a warning should be displayed or migration should be disabled.

Additional info:

Indepedent from the configured overcommitment/ksm policy OVirt should compare memory of VM to migrate versus free memory on target host. KSM might compress memory afterwards but this is too late for the migration process itself.

Comment 1 Doron Fediuck 2014-09-03 15:18:56 UTC
Markus, 
thanks for the detailed report. This is a result of current considerations
while doing balancing and migration, and it will be fixed as a part
of Bug 1093038.

*** This bug has been marked as a duplicate of bug 1093038 ***


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