Search results

Someone help me. Is it really such a difficult situation?

syslog

This is the last thing I saw on the screen

Hi. Switched to the new version 6.4-4. The NOD lived a record time of 12 days. People from the servers were disconnected, but the Windows log of the VM's shows that the machines were still running. The node could be accessed via SSH. I wrote the reboot command in SSH and no reaction. In the WEB...

What can I do to at least understand what the problem is in hardware or software?

Do you mean there is not enough memory for the virtual machines or the total for the node? In Windows of the VM, I didn't see the maximum memory load during the crash

Before I configured ballooning, the memory of each VM was under 100 % in the proxmox web interface. In the virtual machines themselves in Windows, the memory load was normal. After configuring ballooning in the web interface, the memory load for each VM is displayed the same as in Windows. The...

It works stably only when there are no users on the virtual machines. It works when there are 5 users on each server. As soon as I let 15 users start such errors. Help me figure it out.

The errors keep appearing. Please help me.

The node still lives for 6 days, but this is not a record. The largest node lived for 10 days.

Disabled backup of both VMs. The weekend node did not fall. Question: Why does the node have a memory usage percentage of 96% and this value is slightly floating? Can this value jump dramatically? How can VM backups affect memory usage? Maybe I should reduce the memory reserve for the VM?

The node now working, but I think it will hang again this weekend.

Yes, it is the node. It works for 6 days and then hangs with errors. Only a hard shutdown helps.

Can anyone help?

Ballooning not help me.

Hello. The server froze on March 7. Help.

Sorry, I didn't install the driver. Now the memory is displayed correctly Thank you. I'll watch the stability. If there is a flight, I will write additionally. Thanks again)

No Ballooning has been turned off. I Enabled Ballooning, but memory still appears to be 96% loaded in WEB.

The problem node has hard disks: 120 GB for a node and two 512 GB for two VMs. On the node where the memory is displayed normally, HDD 120 has both a node and a VM on it, but the VM is small, only 20 GB. A small node is ordinary without forwarding a video card.