That's great news mate! I see you're running pfSense on top of Proxmox. In my experience, pfSense (FreeBSD) was much more stable than Linux VMs for whatever reason, but even when I ran the same settings as those you're using, my VM still eventually froze.
VM freezes irregularly
- Thread starter thimplicity
- Start date
That's great news mate! I see you're running pfSense on top of Proxmox. In my experience, pfSense (FreeBSD) was much more stable than Linux VMs for whatever reason, but even when I ran the same settings as those you're using, my VM still eventually froze.
A fellow member has pointed me to this discussion. I am not certain if any of you have resolved the issue. I would like to add my experience as it is based on AMD 4900H and 5900HX APUs. I do get a random freeze of Proxmox with a blank green screen.
The problem manifests whenever is activate a Mosquitto MQTT broker and Frigate NVR using it. I have tried all possible combinations with combined and separate CTs and VMs for the apps to no avail. Strange thing is that the dev of Frigate has hundreds if not thousands of deployments and I am the only ever reported such an issue. I thought it might be the architecture I am using - AMD - the culprit, but as I have seen other people reporting this issue with NUCs it might not be CPU architecture related.
In the next few days I will be experimenting on different platforms and see if I can get to the bottom of this. Kernel logs provide no useful information as to where the issue lies.
The problem manifests whenever is activate a Mosquitto MQTT broker and Frigate NVR using it. I have tried all possible combinations with combined and separate CTs and VMs for the apps to no avail. Strange thing is that the dev of Frigate has hundreds if not thousands of deployments and I am the only ever reported such an issue. I thought it might be the architecture I am using - AMD - the culprit, but as I have seen other people reporting this issue with NUCs it might not be CPU architecture related.
In the next few days I will be experimenting on different platforms and see if I can get to the bottom of this. Kernel logs provide no useful information as to where the issue lies.
ugh, that's a bad choice on their end and must have changed some time recently. you must either extract and repackage them (with xz/gz, skip the modification of package contents part
), or build the kernels yourself :-/Hello,ugh, that's a bad choice on their end and must have changed some time recently. you must either extract and repackage them (with xz/gz, skip the modification of package contents part
Unfortunately, I couldn't do that.
I think I'll go for VmWare ESXi for once since the feedback seems to be pretty good...
This machine works fine as such, it's been running stable for days but it fails to provide VM support.
I'm crossing my fingers that it works with ESXi.
Thanks
Hi. We have a proxmox-cluster with local storages (simple dedicated disk, ext4, no lvm) on some nodes.
Also we have a several guest vms on this storages with big ( > 200gb) disks.
In this case we have a guest stuck on shapshot-delete: can't connect to guest via ssh/console and if we interrupt snaphot-delete, guest still stuck until restart VM
Also we have a several guest vms on this storages with big ( > 200gb) disks.
In this case we have a guest stuck on shapshot-delete: can't connect to guest via ssh/console and if we interrupt snaphot-delete, guest still stuck until restart VM
Last edited:
How do you who migrate to esxi create bridges over virtual nic? I was running my opnsense on top of proxmox with 3 cards designed for lan and one for wan. I tried the same setup on esxi but asa I create the network bridge on opnsense and migrate the lan assignment from for ex "vmx0" to "bridge" I lose all connection and must reset default config. Already tried enabling promiscuous mode in all vwitchs on esxi but nothing changes.
I am in the process of thinking. I try ESXi but I find it quite heavy compared to Proxmox and something worries me.
There is no possibility to back up your VMs visibly as Proxmox offers. My heart swings between the 2.
I wonder if I wouldn't make a script that pings the VM to see if it has frozen to reset it within a minute, but it's still DIY and I don't like it. ..
I don't really know what to do, except that I spent +- 400€ for a N5105 1TB NVME and 32 GB of ram...
Great machine but useless...
There is no possibility to back up your VMs visibly as Proxmox offers. My heart swings between the 2.
I wonder if I wouldn't make a script that pings the VM to see if it has frozen to reset it within a minute, but it's still DIY and I don't like it. ..
I don't really know what to do, except that I spent +- 400€ for a N5105 1TB NVME and 32 GB of ram...
Great machine but useless...
Update on ESXi. Same VM running a number of Docker containers migrated across from Proxmox up for almost 3 days - rock solid. No issues with my pfSense VM either. Previously, this VM would hang multiple times a day on Proxmox, at best once a day.
Note: I would much prefer to run Proxmox since it's a much more viable solution for home labs/networks but I need stability.
Note: I would much prefer to run Proxmox since it's a much more viable solution for home labs/networks but I need stability.
Last edited:
You use virtual switches on ESXi instead of Linux bridges. Follow the ESXi setup guide from pfSense to give you a rough idea of how to coonfigute your virtual network: https://docs.netgate.com/pfsense/en/latest/recipes/virtualize-esxi.html
I followed that guide. Created two virtual switches, one for wan and one for lan but instead assigning one uplink for lan I did three. Vlan did not work this way. I use vlan to separate guest and iot network.
Last edited:
This probably isn't the best forum to discuss this. You'd be best asking any of your questions in the VMware community forums.
It's not a motherboard issue.hello,
had a same problem with a dead motherboard... If this can help you
Little feedback from having switched to ESXi.
As for gyrex, these are the same VMs that were running on Proxmox with random crashes...
Here on ESXi, the VMs have been running for almost 2 days without problems...
I hope that Proxmox takes our problem encountered with this N5105 seriously and finds a solution so that we can come back to Proxmox again!
As for gyrex, these are the same VMs that were running on Proxmox with random crashes...
Here on ESXi, the VMs have been running for almost 2 days without problems...
I hope that Proxmox takes our problem encountered with this N5105 seriously and finds a solution so that we can come back to Proxmox again!
we do take it seriously, but without affected hardware to test we rely on users running into the issue to help narrowing down the cause. it is likely a kernel bug (affecting just this hardware), I posted the steps for testing above in this thread, until we get results from that we cannot do anything.
which would be a data point for "something in Ubuntu's kernel patch set"
could you try with the corresponding mainline kernel I linked above? on Ubuntu you should be able to just install them without the need to repack, since their dpkg is patched to support zstd.