Red Hat Bugzilla – Bug 1280004
Balloon device should be enabled by default for new VMs
Last modified: 2016-02-18 06:10:38 EST
Description of problem:
The balloon device is disabled in the Blank template. This causes all VM created from that template to miss a device that we need for any memory related QoS (ballooning, KSM).
It is not possible to hot-plug the ballooning device during VM runtime so all VM started without it have to be restarted to get it.
Average users are not usually checking the Resource allocation subtab when creating new VM and might be surprised by the fact that ballooning does not work for new VMs.
Version-Release number of selected component (if applicable):
Just go to the Blank template and open the Resource allocation subtab.
Ballooning device is enabled by default.
adding it to Blank should solve this
Regression from 3.5
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.
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA
Verified with rhevm-3.6.2-0.1.el6.noarch.
1. Blank template -> Resource allocation tab -> Memory Balloon Device Enabled is checked.
2. Create new vm (Based on Blank template) -> Resource allocation tab -> Memory Balloon Device Enabled is checked.