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

    Do you have performance tips for Proxmox virtualized pfSense?

    Scheduled Pinned Locked Moved Virtualization
    18 Posts 4 Posters 4.8k 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.
    • P
      Patch @yobyot
      last edited by Patch

      @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

      VM to the new Proxmox 8 x86-64-v2-AES type.

      I use processor type "Host" as I don't anticipate needing to live migrate my pfsense VM to another Proxmox host,

      @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

      It also has six Intel I225-V 2.5Gbs ports.

      Nice, I recently bought a similar unit.
      Given the generous physical NIC we have, I pass through all NIC pfsense VM uses. Proxmox (and other VM's) connect to the pfsense VM via an external switch.

      @NollipfSense said in Do you have performance tips for Proxmox virtualized pfSense?:

      If you follow the above, you'll see that both WAN and LAN are required to pass-through. It's best to have a separate interface for Proxmox.

      Agree

      @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

      The Netgear switch would will support two Ubiquiti POE+ APs, upstream connection to the ISP, a NAS running at 1Gbps and, possibly, two wired connections.

      That's a bit weird. It is not clear why you are connecting the ISP to the Netgear switch.
      Why are you not using a WAN connection:
      ISP -> pfsense VM (optionally passed through) NIC

      Lan connection
      pfsense VM (optionally passed through) NIC -> Netgear switch
      (if pfsense Lan NIC is passed through, Proxmox & other VM will use a different physical NIC to connect to the Netgear switch / LAN. That also means if your Proxmox install has a problem you can easily connect it to another lan to fix it)

      Y 1 Reply Last reply Reply Quote 0
      • Y
        yobyot @Patch
        last edited by

        @Patch said in Do you have performance tips for Proxmox virtualized pfSense?:

        I use processor type "Host" as I don't anticipate needing to live migrate my pfsense VM to another Proxmox host,

        Interesting. How do you get pfSense to then use hardware AES support, which is crucial for TLS performance?

        That's a bit weird. It is not clear why you are connecting the ISP to the Netgear switch.
        Why are you not using a WAN connection:
        ISP -> pfsense VM (optionally passed through) NIC

        I misstated it. I do plan to connect the ISP directly to the appliance. Not sure what I was thinking. :-)

        Thanks.

        P 1 Reply Last reply Reply Quote 0
        • P
          Patch @yobyot
          last edited by

          @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

          How do you get pfSense to then use hardware AES support

          My understanding is VM processor type "Host" means the VM is told it has the same processor as the Proxmox hypervisor is running on. So if the physical processor supports AES then the VM will be told that's the case.

          Y 1 Reply Last reply Reply Quote 0
          • Y
            yobyot @Patch
            last edited by

            @Patch said in Do you have performance tips for Proxmox virtualized pfSense?:

            @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

            How do you get pfSense to then use hardware AES support

            My understanding is VM processor type "Host" means the VM is told it has the same processor as the Proxmox hypervisor is running on. So if the physical processor supports AES then the VM will be told that's the case.

            Hmmm....until I changed to the AES-specific host, none of the crypto showed as active in the pfSense summary. Weird.

            aes.png

            P 1 Reply Last reply Reply Quote 0
            • P
              Patch @yobyot
              last edited by Patch

              @yobyot
              Proxmox hardware settings for pfsense VM
              11 pfsense VM Hardware information.jpg

              pfsense GUI System information
              12 pfsense System information.jpg

              Y 1 Reply Last reply Reply Quote 0
              • Y
                yobyot @Patch
                last edited by

                @Patch said in Do you have performance tips for Proxmox virtualized pfSense?:

                @yobyot
                Proxmox hardware settings for pfsense VM
                11 pfsense VM Hardware information.jpg

                pfsense GUI System information
                12 pfsense System information.jpg

                Hmmm…I wonder what the difference is between your appliance and mine is when it comes to the “Host” type.

                NollipfSenseN 1 Reply Last reply Reply Quote 0
                • NollipfSenseN
                  NollipfSense @yobyot
                  last edited by

                  @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

                  Hmmm…I wonder what the difference is between your appliance and mine is when it comes to the “Host” type.

                  Looking at this screenshot below, WAN should be vtnet0 and LAN should be vtnet1...

                  Screenshot 2023-08-20 at 10.34.22 AM.png

                  Also, I have only followed the pfSense recipe quoted in earlier post and that required to use BIOS > OVMF for UEFI boot with machine Q35...

                  Screenshot 2023-08-20 at 10.27.29 AM.png

                  pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
                  pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

                  Y 1 Reply Last reply Reply Quote 0
                  • Cool_CoronaC
                    Cool_Corona
                    last edited by

                    Yes. Use ESXi.

                    1 Reply Last reply Reply Quote 0
                    • Y
                      yobyot @NollipfSense
                      last edited by

                      @NollipfSense said in Do you have performance tips for Proxmox virtualized pfSense?:

                      Looking at this screenshot below, WAN should be vtnet0 and LAN should be vtnet1...

                      Actually, no.

                      pfSense was running on an external Vault. When I migrated it to Proxmox, I put it on vmbr1. I haven't found a way to renumber the bridges so that it "looks" right and now I kinda like it.

                      NollipfSenseN 1 Reply Last reply Reply Quote 0
                      • NollipfSenseN
                        NollipfSense @yobyot
                        last edited by

                        @yobyot said in Do you have performance tips for Proxmox virtualized pfSense?:

                        Actually, no.

                        pfSense was running on an external Vault. When I migrated it to Proxmox, I put it on vmbr1. I haven't found a way to renumber the bridges so that it "looks" right and now I kinda like it.

                        Well, if it works for you, hooray...I just shared what the pfSense document says...like I installed using UEFI for pfSense on Proxmox, as well as, install Proxmox on ZFS.

                        pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
                        pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

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