Bug #481

IM driver not reporting free mem

Added by Tino Vázquez about 10 years ago. Updated about 10 years ago.

Status:ClosedStart date:02/08/2011
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:

0%

Category:-
Target version:-
Resolution: Pull request:
Affected Versions:

Description

Thus scheduling is not working properly for VMware installs. Reported by Luigi Fortunati <>

http://lists.opennebula.org/pipermail/users-opennebula.org/2011-February/003840.html

0001-Free-mem-calculated-not-provided-by-libvirt.patch Magnifier (1.89 KB) Tino Vázquez, 03/25/2011 12:12 PM

0002-Take-just-running-and-suspended-machines-in-free-mem.patch Magnifier (996 Bytes) Tino Vázquez, 03/25/2011 12:12 PM

Associated revisions

Revision 7358422f
Added by Abel Coronado over 3 years ago

B #5159: User quotas take into account group quotas more restrictive (#481)

Revision 6040b46e
Added by Abel Coronado over 3 years ago

B #5159: User quotas take into account group quotas more restrictive (#481)

(cherry picked from commit 7358422f92268f5bbf48a4fddb4ea569dc4e36d0)

History

#1 Updated by Tino Vázquez about 10 years ago

Due to libvirt not reporting back free mem, and the infeasibility of running probes in the ESX servers, we are going to implement the free mem calculation in the im driver as total memory minus used memory (used by the VMs) . This has as drawback that the free memory is probably less than the calculated one, due to memory consumption by the hypervisor itself. A possible workaround would be to apply a correcting coeficient to the free mem (80%, for instance. This will be configurable.

#2 Updated by Tino Vázquez about 10 years ago

  • Status changed from New to Closed

Fixed in VMware Driver Addon

Also available in: Atom PDF