- Original Message -
From: Doron Fediuck dfedi...@redhat.com
To: engine-devel@ovirt.org, Adam Litke a...@us.ibm.com
Sent: Sunday, May 27, 2012 10:31:22 PM
Subject: [Engine-devel] Enabling guest memory balloon device
Hi All,
In the following wiki, there's a design for enabling the balloon
device,
which is currently disabled in engine setups. Other than enabling the
device,
this is also a step forward in the path to vdsm and MoM sub-project
integration.
More details can be found here:
http://www.ovirt.org/wiki/Features/Design/memory-balloon
P.S.
UI mockups should be updated soon.
--
/d
“Funny,” he intoned funereally, “how just when you think life can't
possibly get any worse it suddenly does.” --Douglas Adams, The
Hitchhiker's Guide to the Galaxy
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
what does it mean template is not supported? (and why is it under ovf section?)
this value will not pass to a template created from a vm? (although its
mentioned in Backend-vdsm parts section)
if this is a vm-device, why do we need it in vm_static?
can you explain means the change in VmOldInfoBuilder?
shouldn't we just ignore it to keep old behavior? or we want to support
ballooning in all clusters?
(in Validations section it says only 3.1 is supported)
maybe validation is needed on changing vm cluster command, in case changing to
3.0 cluster and balloon enabled.
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
