+++ This bug was initially created as a clone of Bug #1337834 +++
Description of problem:
In the past MOM was only responsible for ballooning. But now it also manages some CPU and storage QoS settings. When there is no ballooning device on the VM, MOM completely ignores that VM and therefore does not set QoS attributes for CPU and storage.
The policy already checks whether balloon info is available, but mom configuration needs to be changed to use the new GuestBalloonOptional collector.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1) Create a VM with no ballooning device or with
2) Add QoS attributes through vdsm to the domain XML metadata section
MOM does not apply them and writes to the logs that it ignores the VM because of no ballooning device.
MOM applies QoS attributes to the libvirt domain xml.
This prevents QoS update of a VM disk.
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.
Moving to Assigned since build 3.6.9 is not available yet.
Then wait for the build please. FailedQA means you tested it and it did not work.. apparently that is not the case here.
3.6 is gone EOL; Please re-target this bug to a 4.0 release.
verified on :
Red Hat Virtualization Manager Version: 4.0.4-0.1.el7ev
1. create vm with ballooning disabled
2. check mom logs for :
2016-09-05 13:42:35,922 - mom.GuestMonitor.Thread - INFO - GuestMonitor-golden_env_mixed_virtio_0 starting
2016-09-05 13:42:35,941 - mom.Monitor - INFO - golden_env_mixed_virtio_0 is ready