Got a weird problem which I can’t find an answer to …
I’ve got Home Assistant installed in a VM in Proxmox. The VM has 4Gb of RAM and it used to work fine showing 4Gb in the OS (ssh into port 22222) but I migrated it to another Proxmox host in the cluster this morning and now it only shows 905Mi.
I’ve found something about this on an RPI from a while back but I don’t think that applies.
I’ve seen this before but it was the first time I’d installed on Proxmox and done the first run with only 1GB of ram and then increased it later so I thought it related to that but this would seem to indicate it wasn’t.
Anyone got any pointers to how I can fix without recreating the VM and restoring from a backup ?
And I found a solution
Came at it from the Proxomox perspective rather than the Hassos perspective, and found a post about a pfsense VM behaving the same way.
It would appear the Memory Hotplug option needs some extra config that would appear to be present on the versions of Linux that I usually deploy but not on the Hassos image : https://pve.proxmox.com/wiki/Hotplug_(qemu_disk,nic,cpu,memory)
Hi there, would you be able to share which file you editied to add the memory hotplug paremeter to the kernel please? I’m not at all familiar with this version of linux.
Sorry to say I went the other way and disabled hotplug for memory (and CPU though not sure if that was needed) in the Proxmox VM. The way I see it futzing with the base os in ways that will possibly be overwritten during an update is a bad idea when compared to the hassle of restarting to increase RAM and CPU obviously your usecase may well be different
I was seeing the same problem that I had assigned 4gb but was only seeing 1 and thought it might be the hotplug memory issue, but actually after setting the “minimum memory” to 2gb in proxmox i’m now seeing 2gb in haos since a reboot (although max is 4gb but i’m only seeing 2) - still better than one!