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

High interrupt CPU usage in v2.7.1

Scheduled Pinned Locked Moved Virtualization
26 Posts 16 Posters 6.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.
  • T
    tmb
    last edited by Mar 8, 2024, 8:12 PM

    I have the same issue. Running pfSense CE 2.7.2 in a VM on a XCP-ng host (8.2.1). Interrupt CPU usage is between 60-80%.

    T 1 Reply Last reply Mar 10, 2024, 10:26 AM Reply Quote 0
    • T
      tmb @tmb
      last edited by tmb Mar 10, 2024, 10:26 AM Mar 10, 2024, 10:26 AM

      Some more data:

      Top on the vm:

      last pid: 23296;  load averages:  0.08,  0.14,  0.14                                                   up 0+18:46:31  10:20:03
      286 threads:   2 running, 251 sleeping, 33 waiting
      CPU:  0.0% user,  0.0% nice,  0.0% system, 84.0% interrupt, 16.0% idle
      Mem: 85M Active, 142M Inact, 299M Wired, 56K Buf, 403M Free
      ARC: 171M Total, 46M MFU, 118M MRU, 4096B Anon, 841K Header, 5776K Other
           143M Compressed, 278M Uncompressed, 1.94:1 Ratio
      Swap: 1024M Total, 1024M Free
      

      Top On the hypervisor:

      top - 10:16:34 up 9 days, 12:45,  1 user,  load average: 651.11, 650.81, 649.76
      Threads: 1763 total,   1 running, 1696 sleeping,   0 stopped,   0 zombie
      %Cpu(s):  0.4 us,  0.7 sy,  0.0 ni, 98.6 id,  0.0 wa,  0.0 hi,  0.0 si,  0.3 st
      KiB Mem :  1329412 total,    39032 free,   892192 used,   398188 buff/cache
      KiB Swap:  1048572 total,   951548 free,    97024 used.   277052 avail Mem 
      

      vmstat -i

      interrupt                          total       rate
      irq1: atkbd0                        1094          0
      irq15: ata1                        44975          1
      irq23: uhci0                          20          0
      cpu0:xen                        23137567        342
      irq2102: xen_et0:c0              7093144        105
      irq2103: xenstore0                  8039          0
      irq2105: xbd0                     599431          9
      irq2106: xn0                      925434         14
      irq2107: xn0                      501940          7
      irq2108: xn0                      437785          6
      irq2109: xn0                     4301938         64
      irq2110: xn1                     2861373         42
      irq2111: xn1                     1348751         20
      irq2112: xn1                     1813507         27
      irq2113: xn1                     3541821         52
      irq2114: xn2                       44963          1
      irq2115: xn2                       15997          0
      irq2116: xn2                       50798          1
      irq2117: xn2                      133775          2
      irq2121: xn3                           6          0
      Total                           46862358        693
      
      1 Reply Last reply Reply Quote 0
      • R
        Raghnall
        last edited by Raghnall Mar 10, 2024, 11:58 AM Mar 10, 2024, 11:57 AM

        I am seeing the same thing, though it looks like it might be an accounting bug and not a real issue - see: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277231

        Regardless, it does not seem to be related to the network cards or the version of Xen.
        I see the same thing with only a physical Intel X520-DA2 passed through to the VM.
        I also tested on XCP-ng 8.3-beta2 with Xen 4.13 as well as with Xen 4.17; all show the same issue.

        T 1 Reply Last reply Mar 10, 2024, 8:12 PM Reply Quote 1
        • T
          tmb @Raghnall
          last edited by Mar 10, 2024, 8:12 PM

          @Raghnall Thank you for finding the bug report! I did search on the FreeBSD forums but couldn't find anything.

          1 Reply Last reply Reply Quote 0
          • P
            pfsense2023
            last edited by Mar 25, 2024, 12:39 PM

            Same thing here, running pfSense 2.7.2 on XCP-ng 8.3.0

            It appears that this is just a bug on pfSense reporting itself because the VM stats show everything peacefully working.

            b877b6f2-2de1-4aad-9232-c405aff7f3af-image.png

            7a19f36e-da71-4a1d-ad96-d1fffee4b0c4-image.png

            C 1 Reply Last reply Apr 6, 2024, 7:15 AM Reply Quote 0
            • C
              cougarmaster @pfsense2023
              last edited by Apr 6, 2024, 7:15 AM

              @pfsense2023

              In top it shows high interrupt
              fcff96ff-3aae-46e4-bb8d-4a36c88e9f7a-image.png

              1 Reply Last reply Reply Quote 0
              • S stephenw10 referenced this topic on Apr 6, 2024, 11:34 PM
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received