VM no longer booting after 2.5.2 RC update
-
Tried updating to Version 2.5.2.r.20210615.1851 from 2.5.2-BETA (amd64) built on Fri Jun 04 03:01:13 EDT 2021 and the VM is no longer booting after the update.
-
Does it always stop at the same place?
-
@jimp yes. I restored the VM back to 2.5.2-BETA (amd64) built on Fri Jun 04 03:01:13 EDT 2021 and tried updating it again and the result is the same.
-
What shows up if you hit
^T(ctrl-t) while it's stopped there?What packages do you have installed, if any?
From the screenshot it looks like you have limiters active, do you also have ALTQ shaping active? Or any other firewall features?
How many rules do you have?
-
What shows up if you hit ^T (ctrl-t) while it's stopped there?
Nothing
What packages do you have installed, if any?
acme, Backup, haproxy, iperf, mtr-nox11, nmap, openvpn-client-export, pfBlockerNG-devel, Service_Watchdog, Status_Traffic_Totals, suricata (DISABLED)
From the screenshot it looks like you have limiters active, do you also have ALTQ shaping active? Or any other firewall features?
Don't have any shaper or QoS enabled at this moment.
How many rules do you have?
150-200, including WAN1/2, LAN, Floating
-
@coldfire7 said in VM no longer booting after 2.5.2 RC update:
Don't have any shaper or QoS enabled at this moment.
The modules shown loading on the console screenshot show it's loading modules for Limiters, so they must be in there somewhere.
Though I have a VM with limiters and it is working OK still.
-
@jimp I checked again, I have a few enabled (that's why those are loading) but no firewall rule is using those.
-
maybe it's something else, i have taildrop limiter and kvm
no problem so far,
network em0/1/2/3
package suricata / haproxy / openvpn-client-export
maybe one of your service or some incompatible settings on kvm
🔒 Log in to view -
Could you roll back, remove all the packages, and then upgrade again to see if that makes a difference?
About half my lab VMs are in KVM and most of those are on 2.5.2, none are having problems getting past that point on the current snap.
-
@jimp Updated to a newer version. No crash so far.
