Bug #2179
Wrong VMware CPU monitoring
| Status: | Closed | Start date: | 07/17/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | Drivers - VM | |||
| Target version: | Release 4.2 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.0 |
Description
It's returning the percentage over all the physical CPUs on the host, instead of the requested CPUs in the VM template
Associated revisions
bug #2179: Fix for Host & VM CPU monitoring for VMware
VM CPU % - percentage of requested CPUs used (max 100%)
HOST CPU % - percentage of available CPUs used (max 100*numCPUs%)
bug #2179: Fix for Host & VM CPU monitoring for VMware
VM CPU % - percentage of requested CPUs used (max 100%)
HOST CPU % - percentage of available CPUs used (max 100*numCPUs%)
(cherry picked from commit decccf80fbc75eadcd33a0afa9bb980673b922e5)
bug #2179: Avoid negative monitor values in VMware polling
bug #2179: Avoid negative monitor values in VMware polling
(cherry picked from commit 1a70cffab08276a6019fb876b3ce5f20875d1256)
History
#1
Updated by Tino Vázquez almost 8 years ago
- Status changed from Pending to New
#2
Updated by Carlos Martín almost 8 years ago
- Category set to Drivers - VM
#3
Updated by Tino Vázquez almost 8 years ago
- Target version set to Release 4.2
#4
Updated by Tino Vázquez almost 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
- Resolution set to fixed
Now reports:
VM CPU % - percentage of requested CPUs used (max 100%)
HOST CPU % - percentage of available CPUs used (max 100*numCPUs%)