Hide Forgot
Currently hot plugging memory to a virtual machine requires that the delta is a multiple of 256 MiB, and clients need to be aware of this and provide the right size, otherwise the memory isn't updated. We need either modify the engine so that it adjusts the memory so that it will work, or else provide in the API a mechanism for the client to find out this value. For example: GET /ovirt-engine/api/clusters/123 <cluster_level> ... <memory_policy> ... <hot_plug_delta_unit>268435456</hot_plug_delta_unit> ... </memory_policy> ... </cluster_level> Not 100% sure if the cluster is the right place for this.
We should probably begin with proper documentation.
the granularity of hotplug is a CL/arch detail. I suggested to add API for generic VdcOptions access holding these values. Support of hot(un)plug is also in osinfo which doesn't have API either today. Also could be added Adding specificic items to API for each of VdcOption value kind of defeats the purpose of a general low-level configuration store. Alternatively it was suggested to round up the requested numbers. That's also possible
We didn't get to this bug for more than 2 years, and it's not being considered for the upcoming 4.4. It's unlikely that it will ever be addressed so I'm suggesting to close it. If you feel this needs to be addressed and want to work on it please remove cond nack and target accordingly.
ok, closing. Please reopen if still relevant/you want to work on it.