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

    Pfsense 2.1 vmware cpu host high usage

    Scheduled Pinned Locked Moved Virtualization
    50 Posts 21 Posters 22.3k 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.
    • C
      cmb
      last edited by

      Has one of the minority who's seeing this actually contacted VMware support? It only happens to a tiny fraction. The VM isn't using that much CPU, if the hypervisor is…guess whose fault that is? More than likely not ours or FreeBSD's.

      1 Reply Last reply Reply Quote 0
      • K
        kenshirothefist
        last edited by

        @cmb:

        Has one of the minority who's seeing this actually contacted VMware support? It only happens to a tiny fraction. The VM isn't using that much CPU, if the hypervisor is…guess whose fault that is? More than likely not ours or FreeBSD's.

        As somebody already noted in one of previous posts - it is likely that the majority is hitting this issue, but are simply unaware of it. Because under low or modest load you never notice the high CPU usage in VMware, if you aren't explicitly monitoring the VM from VMware side (and many users are only monitoring load inside pfsense).

        If there are any users, who are not seeing this issues (make sure you actually look at VMware virtual machine CPU usage under modest load) - please, post your configuration or VMware environment description.

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          Just today I'm being hit with 90+Mbps of external junk traffic.  I started getting VMware alarms telling me that my pfSense CPU usage was excessive.  When I check via pfSense dashboard, CPU is at ~45%.  When I check VMware performance, CPU is at 90+%.  See image.

          CPU.png
          CPU.png_thumb

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            @kenshirothefist:

            As somebody already noted in one of previous posts - it is likely that the majority is hitting this issue, but are simply unaware of it.

            And as I've already noted, that's not true, I've reviewed this with many customers with a wide range of specifics in the config. Including our own high load production systems, and our dev/test systems.

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              And as I've already noted, that's not true

              The problem here is that we trust you and pfSense, but we also trust VMware and were getting conflicting information.  Right now this very moment, pfSense says 2% CPU and VMware says 7%.  Resource Alloc page says I'm using 316 MHz out of 4520 MHz, which is ~7%.  I don't have budget for a VMware service contract so calling them is not an option for me.  They are a much larger organization with a metric buttload of production installations, and you would think that such a CPU usage discrepancy would have been caught by them long ago.  Kind of a stalemate.

              1 Reply Last reply Reply Quote 0
              • T
                Terrabit_AH
                last edited by

                i can give a developer access to our cloud platform. we can also open a vmware ticket.

                but i need help to solve this problem.

                the problem only occurs when high load is present.

                i have 50 pfsense online one have the problem. it is the border router with bgp connection to the internet.

                the error occurs if the load takes more than one cpu. this is the result of my actual tests.

                i routet my heavy traficc between the datacenters now over a windows 2012 r2 machine with softether.
                i need för 500mbit load 3 cpu's with 2,6 Ghz. 2 l3 routing instances and encryption.

                1 Reply Last reply Reply Quote 0
                • C
                  cmb
                  last edited by

                  @Terrabit_AH:

                  i can give a developer access to our cloud platform. we can also open a vmware ticket.

                  but i need help to solve this problem.

                  I could pursue it sometime in January if you're willing to do it as a professional services engagement. I'd give you a break on the hours as I'm curious what's going on here, though still talking probably a $1000 USD project to evaluate the issue and determine its source. Couldn't promise any fix, especially since the problem is likely VMware's, but that'd be enough to assemble a proper problem report to escalate to VMware if that's the source of the issue, or elsewhere if it's elsewhere. Email <professional.services <at="">pfsense <dot>org> if that might be of interest and we can discuss further and put together a scope and statement of work.

                  Otherwise, at some point post-2.2 release I might take you up on it. Professional services is the only way I'll be able to look at it in the next couple months.</dot></professional.services>

                  1 Reply Last reply Reply Quote 0
                  • 2
                    2qik
                    last edited by

                    We have the exact same issue and are running 2.1 on ESXi 5.1.
                    But it isn't only VMware environments that are having the issue.  There are reports above of it happening on KVM too.  Therefore doesn't it seem more like something in pfsense/FreeBSD itself?

                    I am also happy to open a case with VMware if you think there is a chance they will look at it seriously.  But I am sure they are more likely going to point it back at FreeBSD/pfSense.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      If you're seeing that, I'd first upgrade to the latest available 2.2 snapshot (which is very close to what will be release), or wait at most a few days for the official release.

                      The only CPU-related complaints I've seen related to KVM is in high CPU usage within the VM, it's the same CPU usage outside the VM. That's generally solved enabling virtio, but for those who found that inadequate, upgrading to 2.2 resolved the issue.

                      1 Reply Last reply Reply Quote 0
                      • M
                        Marv21
                        last edited by

                        Its 2.2.4 with VMWaretools. VMWare - Workstation

                        In Pfsense 8-9%
                        Hosttaskmanager 30%

                        PFsense224highcpu.jpg
                        PFsense224highcpu.jpg_thumb

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