VM Crash

agreen

Active Member
Jul 1, 2018
11
1
41
43
hello,
i have a problem with my proxmox enviroment. if i starting a VM, then crash a other VM.
for example if i start the VM ID 114, then crash the 117. if i start the VM ID 117, then crash the VM ID 114.

Code:
root@proxi7:~# tail -f /var/log/syslog
Mar 15 10:19:01 proxi7 systemd[1]: Starting Proxmox VE replication runner...
Mar 15 10:19:02 proxi7 kernel: [498175.831124] oom_reaper: reaped process 12144 (kvm), now anon-rss:0kB, file-rss:36kB, shmem-rss:4kB
Mar 15 10:19:02 proxi7 kernel: [498175.846062] fwbr117i0: port 2(tap117i0) entered disabled state
Mar 15 10:19:02 proxi7 kernel: [498175.846277] fwbr117i0: port 2(tap117i0) entered disabled state
Mar 15 10:19:02 proxi7 systemd[1]: 117.scope: Succeeded.
Mar 15 10:19:02 proxi7 pvedaemon[15784]: VM 114 qmp command failed - VM 114 qmp command 'guest-ping' failed - got timeout
Mar 15 10:19:02 proxi7 systemd[1]: pvesr.service: Succeeded.
Mar 15 10:19:02 proxi7 systemd[1]: Started Proxmox VE replication runner.
Mar 15 10:19:03 proxi7 qmeventd[713]: Starting cleanup for 117
Mar 15 10:19:03 proxi7 kernel: [498176.726207] fwbr117i0: port 1(fwln117i0) entered disabled state
Mar 15 10:19:03 proxi7 kernel: [498176.726281] vmbr0: port 15(fwpr117p0) entered disabled state
Mar 15 10:19:03 proxi7 kernel: [498176.726416] device fwln117i0 left promiscuous mode
Mar 15 10:19:03 proxi7 kernel: [498176.726421] fwbr117i0: port 1(fwln117i0) entered disabled state
Mar 15 10:19:03 proxi7 kernel: [498176.754032] device fwpr117p0 left promiscuous mode
Mar 15 10:19:03 proxi7 kernel: [498176.754034] vmbr0: port 15(fwpr117p0) entered disabled state
Mar 15 10:19:03 proxi7 qmeventd[713]: Finished cleanup for 117
Mar 15 10:19:09 proxi7 pvedaemon[15784]: worker exit
Mar 15 10:19:09 proxi7 pvedaemon[1153]: worker 15784 finished
 
Mar 15 10:19:02 proxi7 kernel: [498175.831124] oom_reaper: reaped process 12144 (kvm), now anon-rss:0kB, file-rss:36kB, shmem-rss:4kB
Could it be a memory issue? How much ram do you have in your system and how much is assigned to each vm?
 
RAM usage 86,50% (26,55 gib of 30,69 gib)
Swap usage 99,55%

i set for this 2 VMs 3.5 GiB Ram and now the VMs working.
i will check it for some days and will give an update

THX
 
Last edited:
With that Swap usage, I'd say it was definitely due to over commitment of RAM. In general, try to ensure that the total memory assigned to all running VMs is less than the total available system memory. Otherwise a memory build up in one VM can crash the system.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!