Bug 1338665 - Template of Glance imported VMs have Ballooning device disabled
Summary: Template of Glance imported VMs have Ballooning device disabled
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Tal Nisan
QA Contact: Carlos Mestre González
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-23 08:31 UTC by Roman Mohr
Modified: 2016-07-05 08:01 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-07-05 08:01:17 UTC
oVirt Team: Storage
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
tnisan: devel_ack+
acanan: testing_ack+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 57980 0 master MERGED core: Import template from external provider with balloon device enabled 2016-05-25 08:48:35 UTC

Description Roman Mohr 2016-05-23 08:31:50 UTC
Description of problem:
When importing a VM image for instance via Glance, they have the field "Memory Balloon Device Enabled" unchecked. This is different than the default when creating a fresh VM from the default template.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Import an image from glance as template
2. Check the "Resource Allocation" tab
3. "Memory Balloon Device Enabled" is disabled

Actual results:
VMs from the new tamplate are then created without ballooning device.

Expected results:
Having "Memory Balloon Device Enabled" checked by defualt, like in every other VM flow.

Additional info:

Comment 1 Michal Skrivanek 2016-05-24 08:25:09 UTC
The initial balloon setting is based on either the instance type (default ones have it disabled) or the selected template if no instance type is used, using "Blank" when you don't select any template

Tal, Import from Glance was a storage feature - was this intentional? If not then I suppose it could use "Blank" as well

Comment 2 Tal Nisan 2016-05-24 17:19:16 UTC
No, it was not done on purpose.
most of the settings are not set by default when importing from external provider but since it's a desired behavior I've changed it

Comment 3 Carlos Mestre González 2016-06-17 14:40:33 UTC
> Having "Memory Balloon Device Enabled" checked by defualt, like in every other VM flow.
This happens for the template and for the vms created from the template imported.

version: rhevm-

Comment 4 Sandro Bonazzola 2016-07-05 08:01:17 UTC
oVirt 4.0.0 has been released, closing current release.

Note You need to log in before you can comment on or make changes to this bug.