This is a repeatable issue stemming before version 1.7.0. Every install caps RAM at 834M, regardless of what was allocated from Proxmox. i have used CasaOS for years, since it an application and not a locked distro image, it has worked fine for years. When i notice a new release for ZimaOS, i try it again as CasaOS is not actively maintained, Everytime ZimaOS disappoints.
I will test it in Proxmox. If the issue is confirmed, we will fix it
Hello, thank you for your feedback.
I tested ZimaOS v1.7.1-beta1 on a QEMU virtual machine with 8 GiB of memory on Proxmox, following the installation guide at: https://www.zimaspace.com/docs/zh/zimaos/install-zimaos-on-proxmox-ve
Inside ZimaOS, free -m shows about 7942 MiB, so I have not yet been able to reproduce the 834 MiB memory limit issue you encountered.
Could you please tell me how your Proxmox is configured? I suspect that Proxmox’s memory ballooning mechanism might have reduced the VM memory to around 1 GiB. You could try running the following on the Proxmox host to check:qm config
and see if there is a balloon: 834 entry.
Thank you for your feedback. After enabling Memory Hotplug on Proxmox, I found that indeed only 1 GB of memory was provided. The current ZimaOS lacks the ACPI memory hotplug driver, so the additional memory was not registered by Linux. I have now added the relevant driver and successfully tested it. This issue is expected to be fixed in the next release. As a temporary workaround, please disable hotplug for now. Thank you for your help.
That is great news. I was able to finally migrate casaOS to ZimaOS