Search results

Well, in my case the unit itself didnt reboot, but VMs crashed at random with a kernel panic (and I found nothing interesing in the logs). Also independed of their load, time ranged between a few minutes and a few days. Keep in mind, I tested the Beelink only for a few days and sent it back as...

I tried many things like changing the SSD, changing memory, changing power and frequency related cpu settings in the bios (I dont know what exactly) - nothing solved my problems. As I said, I sent the device back to the seller.

I also had issues trying to run Proxmox on the Beelink U59 a few months ago. VMs kept crashing after random time intervals (sometimes 5 minutes, sometimes 1-2 days). I have also tested swapping drives or using a 2.5 inch SSD, same problem. In the end I sent the thing back. Seems to be an issue...

In my case I think I updated via apt but did not reboot. Can this cause this much problems?

Looks like that command helped. The node was running fine (already started VMs are still running without a problem, CTs also could be started and stoppen), but at some point the starting of VMs was no longer possible and resulted in the posted error.

Hello, I get the following error if I try to start a VM on a specific host: Does anyone know what is going on?