Currently, I have two virtual machines running on my PVE, one with OpenWRT and the other with TrueNAS. The memory usage of the TrueNAS virtual machine is quite peculiar. After booting up, TrueNAS itself only occupies about 2 GB of memory, and at this point, there is no ARC cache. Regardless of whether I check the memory usage within TrueNAS or the VM Summary, the memory usage is displayed as normal. However, in the Node Summary or when using commands such as 'free', it shows that the TrueNAS virtual machine is utilizing all the memory allocated to it.
Ballooning is turned on, and qemu-guest-agent is running normally.This situation did not occur previously. It arose after I replaced the old equipment and redeployed PVE and TrueNAS. The previous device was based on the Intel N5105 platform, running PVE version 8.2.4 and TrueNAS version 25.04.1. I have now switched to an AMD 5800U platform, with PVE version 8.4.5 and TrueNAS version 25.04.2.
TrueNAS briefly consumes a large amount of memory during startup, after which it stabilizes around 2GB. It seems that PVE does not release this portion of memory; however, I am not entirely certain about this. At least, I do not believe this is an issue with TrueNAS, as they are only separated by a minor version update.
The following screenshot illustrates the abnormal memory usage on my new device.



Ballooning is turned on, and qemu-guest-agent is running normally.This situation did not occur previously. It arose after I replaced the old equipment and redeployed PVE and TrueNAS. The previous device was based on the Intel N5105 platform, running PVE version 8.2.4 and TrueNAS version 25.04.1. I have now switched to an AMD 5800U platform, with PVE version 8.4.5 and TrueNAS version 25.04.2.
TrueNAS briefly consumes a large amount of memory during startup, after which it stabilizes around 2GB. It seems that PVE does not release this portion of memory; however, I am not entirely certain about this. At least, I do not believe this is an issue with TrueNAS, as they are only separated by a minor version update.
The following screenshot illustrates the abnormal memory usage on my new device.


