MEMORIA RAM NO LIMITE

[Airton]

Olá a todos,
Tenho um Ambiente Virtual 7.4-3 instalado com 12 GB de RAM e apenas utilizo uma VM, mas não entendo porque o resumo do PVE indica o consumo de memória quase no total de sua capacidade de uso.

Você pode me ajudar a resolver por favor?
Já a VM está ok

 

[Lukas Wagner]

Hello,
first of all, please ask your questions in English (or German in the appropriate sub-forum).

It seems like you have assigned all memory of the host (pve) to VM 103. You should not do this, the host needs at least of 1-2GB for itself (or more, if you use ZFS). See [1] for details on the system requirements of Proxmox VE.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_system_requirements

 

[Airton]

Hello friend Lucas,
But I'm not using ZFS. I only use a VM with a .ext directory to store the .doc.xls.pdf files. This VM has a Windows server installed to share files over the network to users, simple as that and it works well, but it is overloaded.
I have a 4 Tera HD and two 1 Tera HD. Adding 6 Tera of HD linked to the single VM in use. I have a total of 12 Gb of RAM in the PVE.

Hello,
first of all, please ask your questions in English (or German in the appropriate sub-forum).

It seems like you have assigned all memory of the host (pve) to VM 103. You should not do this, the host needs at least of 1-2GB for itself (or more, if you use ZFS). See [1] for details on the system requirements of Proxmox VE.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_system_requirements

 

[beisser]

what i see here is that your vm103 has 12GB ram configured.
your server has only 12GB ram in total.
this means this vm takes all the memory and everything else basically runs off the swap space (which you can see to the right on your first screenshot).
this is bad practice as the system will run very slow and may even crash because its running out of memory. it also trashes your disk because swap is permanently using it.

my suggestion would be to reduce the configured memory on your vm103 to 6GB and also make sure that the other vms running do not consume more than another 4 GB in total, so that the host has a bit of memory for its management tasks.

cpu you can overcommit without harsh repercussions (stuff still runs, just slower because of shared resource).
on memory this does not work. you can use memory only once and it cannot be shared (besides KSM).
that means you have to manage it carefully and make sure you do not use more than you have.