Why was dynamic memory allocation deprecated?
Hi! I’m currently a proxmox user but I’ve been thinking of moving to xcpng! I really don’t like the way thing are going with proxmox so I’m looking for an alternative. Still one of the features I like with prox is that it supports dynamic memory allocation ( not fully reserved as vm is turned on). From what I could understand this has been deprecated from Xcp-ng a while back and I would like to know why.
@danp maybe i should have used the term over provisioning...
I really don’t like the way thing are going with proxmox
Can you be more specific? Always interested to learn what's going on elsewhere
Anyway, DMC is available with XCP-ng, there's just caveat to be able to use it correctly, but obviously, feedback welcome in case of issues
@olivierlambert performance has bit taken a hit lately. Also vms not booting after reboot or power failure, failing backups...just a few exemples. Not to mention that in 6 months it's the second ssd proxmox kills for me. Apparently it's a know issue with the PVE kernel
there's just caveat to be able to use it correctly, but obviously, feedback welcome in case of issues
Care to to explain the caveat
P.S. I'm cloning my vm's using clonezilla as week speak to migrate them to XCP-NG
So when you live migrate a VM, Xen will decrease memory dynamically to the minimum. If you didn't plan correctly dynamic min to a value that's OK for your system, you might have memory problems for your operating system (eg if you system can't survive with less than 4GiB RAM and the dynamic min is set to 3GiB, this will cause problems!). So planning is important.
There's some edge cases also in migration when you have to tell Xen about memory management when you grow/reduce amount of RAM. But it works generally OK if you took care of dynamic min as I said.