Description of problem: Using vdsm-client to get balloon info, the host doesn't get any balloon info on the vms. Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170929123516.git007c392.el7.centos vdsm-4.20.3-121.git77235c7.el7.centos.x86_64 mom-0.5.11-0.0.master.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Connect to a host with a running VM. 2. Run vdsm-client VM getInfo vmID="vmid" -you might use vdsm-client VM getInfo vmID="vmid" | grep balloonInfo Actual results: balloonInfo is not found. Expected results: balloon information, for example: "balloonInfo": { "balloon_max": "1048576", "balloon_cur": "1048576", "balloon_target": "1048576", "balloon_min": "1048576" }, Additional info:
(In reply to Liran Rotenberg from comment #0) > 2. Run vdsm-client VM getInfo vmID="vmid" > -you might use > vdsm-client VM getInfo vmID="vmid" | grep balloonInfo The correct verb is 'getStats', i.e.: vdsm-client VM getStats vmID="vmid" | grep balloon Can you please re-cecheck?
Hi Tomas, my bad. You were right. The correct command is: vdsm-client VM getStats vmID="vmid" | grep balloon The result is the same as above.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified on: vdsm-4.20.7-1.gitc9cf1ee.el7.centos.x86_64 4.2.0-0.0.master.20171114111003.git7aa1b91.el7.centos Steps of verification: 1. Start a VM. 2. Connect to the VM host. 3. Run the command: vdsm-client VM getStats vmID="vmid" | grep balloon Result: The VDSM returns balloon information on the VM.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.