Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ProxMox crashing after upgrading to pfSense 2.5.1

    Scheduled Pinned Locked Moved Virtualization
    5 Posts 3 Posters 802 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      wblanton
      last edited by

      I’ve virtualized pfSense 2.4.5 with an Intel NIC passed through for months with no issues. After upgrading to 2.5.1, the ProxMox Server started crashing sporadically. It happened 3 or 4 times in about as many days. Ive heard someone else on Facebook mentioning they say similar issues when passing through a NIC. Has anyone where experienced it?

      FYI - I stopped the pfSense on the VM and moved to a pfSense 2.5 “router on a stick” on another node and it has been stable for nearly a week.

      1 Reply Last reply Reply Quote 0
      • H
        helloworld21 Banned
        last edited by

        This post is deleted!
        W 1 Reply Last reply Reply Quote 0
        • W
          wblanton @helloworld21
          last edited by

          @helloworld21 said in ProxMox crashing after upgrading to pfSense 2.5.1:

          Hi @wblanton I have the exact same issue!

          Glad to hear I’m not the only one. Hopefully we can get their attention. A VM crashing a ENTIRE HYPERVISOR is bad. Really bad. Please go add your input here: https://redmine.pfsense.org/issues/11882

          So you would recommend the "router on a stick"?

          At this time, it seems to work ok. You are limited to a single link, but my internet isn’t fast enough to really be affected. It’s either that or roll back to 2.4.5, but o haven’t had the time to do that yet.

          ahking19A 1 Reply Last reply Reply Quote 1
          • ahking19A
            ahking19 @wblanton
            last edited by

            @wblanton >> It’s either that or roll back to 2.4.5, but o haven’t had the time to do that yet.<<

            You had time to install pfSense from scratch with a "router on a stick" config but didn't have time to roll back a VM to a previous restore point?? That does not compute.

            W 1 Reply Last reply Reply Quote 0
            • W
              wblanton @ahking19
              last edited by

              @ahking19 I set it up early last week to test it to see if that would remain stable. After it’s been up for nearly a week, I didn’t have time this weekend to roll back. I also made a few config changes on in the firewall and a VLAN tag that I would need to replicate from the 2.5.1 router that was crashing and the router on a stick back to the 2.4.5 VM. In this case, it’s not quite as simple as just hitting the “roll back” button.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.