[PVE-User] Proxmox 4.2 : Online Migration Successful but VM stops

[Alexandre DERUMIER]

>>Yeah I don't know, looks like it works fine for our debian guests at least, 
>>don't need much more. And unplug isn't as important as hotplug anyway for us. 
>>The goal is to increase ressources of a VM when some website hosted on it 
>>appears on TV and we get thousands of visitors at once, if unplugging still 
>>requires a reboot from time to time it's fine. 

hot-plug is working  100%, hot-unplug is the real problem currently




>>I never could make that work. When I try to use ballonning and I change 
>>the ram value, it just shows in red waiting for the VM to be powered off 
>>to apply. I can use the monitor to do it by hand, and that works, but 
>>for example if I have a 16 Gb VM with a 8 min and I try to reduce it to 8 
>>using the command, it goes slowly down to 8 then back up to 16 on it's own. 

You can't change maxmemory, but you should be able to change min memory in gui online.
with shares=0, proxmox should force the memory to go to min size.


>>
>>There is also the fact that the VM always boots with the max value of ram 
>>that makes it way too annoying to use, even if it worked. Guess the ideal 
>>would be for it to boot with the min value instead. 

>>Maybe all of this was a bug, didn't try balloning since mach or april, 
>>might have been fixed now. In anycase the max value doesn't make 
>>much sense for us, I'd rather have no max like with hotplugging. 


Note that you can mix both ballloning && memory hotplug.

memory hotplug should allow you to change max_memory online.
and you can reduce it with changing min_memory + shares=0   for example

best of both worlds.


----- Mail original -----
De: "Kevin Lemonnier" <lemonnierk at ulrar.net>
À: "proxmoxve" <pve-user at pve.proxmox.com>
Envoyé: Dimanche 2 Octobre 2016 10:13:52
Objet: Re: [PVE-User] Proxmox 4.2 : Online Migration Successful	but	VM	stops

> 
> for memory unplug, as I said, it don't work 100% (linux kernel limitation), 
> 

Yeah I don't know, looks like it works fine for our debian guests at least, 
don't need much more. And unplug isn't as important as hotplug anyway for us. 
The goal is to increase ressources of a VM when some website hosted on it 
appears on TV and we get thousands of visitors at once, if unplugging still 
requires a reboot from time to time it's fine. 

> but you can do it another way, use ballonning, with shares=0. 
> 

I never could make that work. When I try to use ballonning and I change 
the ram value, it just shows in red waiting for the VM to be powered off 
to apply. I can use the monitor to do it by hand, and that works, but 
for example if I have a 16 Gb VM with a 8 min and I try to reduce it to 8 
using the command, it goes slowly down to 8 then back up to 16 on it's own. 

There is also the fact that the VM always boots with the max value of ram 
that makes it way too annoying to use, even if it worked. Guess the ideal 
would be for it to boot with the min value instead. 

Maybe all of this was a bug, didn't try balloning since mach or april, 
might have been fixed now. In anycase the max value doesn't make 
much sense for us, I'd rather have no max like with hotplugging. 

-- 
Kevin Lemonnier 
PGP Fingerprint : 89A5 2283 04A0 E6E9 0111 

_______________________________________________ 
pve-user mailing list 
pve-user at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user