Description of problem: The VM memory usage is sometimes reported incorrectly. Version-Release number of selected component (if applicable): vdsm-4.17.13-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1.Run the following on the host where a VM with installed guest agent is running a couple of times in row: # vdsClient -s 0 getAllVmStats 2. The result is correct the first time. The second time is already incorrect. Actual results: Incorrect memory usage is reported Expected results: Correct memory usage is reported
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Verified with vdsm-4.17.19-0.el7ev.noarch according to description. memUsage values didn't not change.
Hi, would it be possible to fix the code in https://bugzilla.redhat.com/show_bug.cgi?id=1295428#c1 ? It is a bit confusing to handle a variable in this way.
(In reply to Roman Hodain from comment #5) > would it be possible to fix the code in > https://bugzilla.redhat.com/show_bug.cgi?id=1295428#c1 ? I agree the code is not the best invention but we are a bit paranoid about possibly breaking things and/or backward compatibility. Renaming either input or output memUsage might be dangerous. Maybe we could duplicate input memUsage under a different name; then the new name could be used in _getGuestStats() and make the code cleaner while the old name would be still available in case it's used anywhere (yes, still not very nice). Whatever you think is appropriate, feel free to post a patch to gerrit and we can discuss it there. (The fix chosen for this bug is a safe fix of a general problem; improving _getGuestStats() is another issue.)