Bug #481
IM driver not reporting free mem
| Status: | Closed | Start date: | 02/08/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due 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 <luigi.fortunati@gmail.com>
http://lists.opennebula.org/pipermail/users-opennebula.org/2011-February/003840.html
Associated revisions
History
#1
Updated by Tino Vázquez over 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 over 10 years ago
- Status changed from New to Closed
Fixed in VMware Driver Addon
#3
Updated by Tino Vázquez over 10 years ago
- File 0001-Free-mem-calculated-not-provided-by-libvirt.patch
added - File 0002-Take-just-running-and-suspended-machines-in-free-mem.patch added
Attaching the patch for the fix.