How I know in 3.6 we will have possibility for memory hotplug(http://www.ovirt.org/Features/Memory_Hotplug), so you can increase vm memory without stopping vm, so I believe your friend can try to implement some external load balancing module(http://www.ovirt.org/Features/oVirt_External_Scheduler): 1) Run vms 2) if one of tasks not success to run because memory limitation on host migrate it on host with enough memory 3) hotplug vm memory to new size
I hope it will help you. Thanks ----- Original Message ----- From: "Jiří Sléžka" <jiri.sle...@slu.cz> To: users@ovirt.org Sent: Tuesday, March 24, 2015 6:04:16 PM Subject: [ovirt-users] running vm when its configured memory is bigger than host memory Hello, my colleague uses oVirt3.5 for scientific purposes and has a question. As I know he needs to run virtual machine with huge amount of over allocated memory (more than one host has) and when it is really needed then migrate it to host where is much more memory. It looks to me like nice use case for oVirt. But here is his own question. > Currently, the virtual machine of given memory size S cannot be run > on the host with less than S physical memory. > > We need to run several virtual machines (with unpredictable memory > requirements) on the cluster consisting of several different hosts > (with different amount of physical memory) in such the way that any > virtual machine can be run on any host. > > Due to Ovirt limitation, virtual machines memory sizes has to be set > to the MINIMUM of host physical memory sizes (in order to be able to > run any virtual machine on any host). As far as I know, this rule has > no connection to cluster's Memory optimization 'Max Memory Over > Commitment' parameter. > > But we cannot predict memory needs of our virtual machines so we need > to set the memory size of all of them to the MAXIMUM of host's > physical memory sizes. > > Explanation: > > We are running several computational tasks (every one on single > independent virtual machine). We have several (and different) host > machines (see Figure 1). > > 1. At the beginning, every task consumes a decent amount of memory. > > 2. After a while, some task(s) allocate a huge amount of memory > (Figure 2). At this moment, some of them cannot continue (due to > unavailable memory on its current host) without migration to the host > with higher memory available. > > 3. After migration (Figure 3), all tasks may continue. > > 4. Some tasks finally consumes a LOT of memory (Figure 4). > > The algorithm above cannot be realized, since every virtual machine > (i.e. task) has predefined (and fixed when running) its memory size > set to the MINIMUM of hosts physical memory sizes. Thanks in advance Jiri Slezka _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
