Crash/kernel panic - reboot twice in short time
-
I agree with above. Go straight hardware if feasible.
Is your pfsense 64 bits? How many WAN interfaces or WAN IPs do you have?
How much RAM is allocated to pfsense? -
I agree with above. Go straight hardware if feasible.
Is your pfsense 64 bits? How many WAN interfaces or WAN IPs do you have?
How much RAM is allocated to pfsense?Direct hardware install is not possible for us. Our pfSense is i386 with 2Gigs of RAM (a lot of RAM is free). We have one WAN with one IP.
After deleting all rule's "Advanced settings - Maximum new connections / per second" (approx. by 15 rules) we have only one reboot and one freeze. Before that, it happened more often.After next reboot/freeze we will install x64bit version. Virtual host is also x64bit architecture (Linux KVM).
-
This may seem like a counter-intuitive solution, but - Is 2.1 bringing you something you need that 2.03 wasn't? You could always use 2.03 until 2.1 gets a patch that makes it stable for you?
-
Troubles solved. :)
When virtualization host has heavy I/O load (due other virtual guest), pfsense on IDE virtual controller has troubles and fall into reboot or other unexpected state. After we load VirtIO drivers https://doc.pfsense.org/index.php/VirtIO_Driver_Support, pfsense is happy and we too.
But don't allow all VirtIO drivers! VTNET in our case slown down net traffic after few days rapidly.Working configs
virtual guest pfsense:
pfSense 2.1-RELEASE-pfSense (amd64)
cat /boot/loader.conf.local
virtio_load="YES"
virtio_pci_load="YES"
#if_vtnet_load="YES"
virtio_balloon_load="YES"
virtio_blk_load="YES"
virtualization host Ubuntu 12.04 64bit:
Linux xxx 3.2.0-54-generic #82-Ubuntu SMP Tue Sep 10 20:08:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
qemu 1.0+noroms-0ubuntu14.11