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

    PfSense Memory only showing 1GB

    Scheduled Pinned Locked Moved Hardware
    19 Posts 3 Posters 1.1k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, well that explains the dashboard. Seems like a hypervisor issue.

      Was it ever set to 1G?

      Has the VM been shutdown since it was changed?

      V C 2 Replies Last reply Reply Quote 0
      • V
        viragomann @stephenw10
        last edited by

        @stephenw10 said in PfSense Memory only showing 1GB:

        Has the VM been shutdown since it was changed?

        Yes, it needs to be shut down. If you only reboot, the hypervisor cannot take over memory changes.

        I tried to reproduce this issue. But I get the correct memory in pfSense, even with ballooning enabled.

        I installed 2.7.2 on Proxmox 7.4 with 2 GB RAM. Then I changed the RAM to 3 GB. After I shut down the VM and booted up the memory was shown up correctly with 3GB again.

        C 1 Reply Last reply Reply Quote 0
        • C
          chrisuan @viragomann
          last edited by chrisuan

          @viragomann Hi Thanks for the response.

          When I changed the memory assignment/allocation in Proxmox from 16GB to 8GB and disable balooning, one of the step to get the VM to take the new configuration is to shutdown and power back on. However, in the PfSense itself I am still seeing it registered with 1GB unfortunately. :(

          1 Reply Last reply Reply Quote 0
          • C
            chrisuan @stephenw10
            last edited by

            @stephenw10....since the initial setup of this PfSense, I've always have it set with 16GB memory. Yes, the VM have been shutdown on numerous occasions. Last shutdown was when I disabled the balooning and reduced the memory size from 16GB to 8GB.

            I have just now shutdown the VM, bumped the memory from 8GB to 10GB and are still seeing the same.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Hmm, something in that VM config is passing only 1G for some reason. I don't know anything in pfSense that would present like that.

              C 1 Reply Last reply Reply Quote 0
              • C
                chrisuan @stephenw10
                last edited by

                @stephenw10 ...Is there anywhere in the PfSense configuration that we can look into and edit to match the configured VM Memory?

                V 1 Reply Last reply Reply Quote 0
                • V
                  viragomann @chrisuan
                  last edited by

                  @chrisuan
                  Not sure, if there is something in pfSense you can do to solve this issue. Possibly it's given by the hypervisor.

                  To get sure that the hypervisor provides the correct virtual hardware, just start the VM with a live-ISO and check the memory inside the OS then.

                  C 1 Reply Last reply Reply Quote 2
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Yeah, like I said, I'm not aware of anything you could set in pfSense that would make it present like that.

                    1 Reply Last reply Reply Quote 0
                    • C
                      chrisuan @viragomann
                      last edited by

                      @viragomann Thanks....will give it a shot.

                      C 1 Reply Last reply Reply Quote 0
                      • C
                        chrisuan @chrisuan
                        last edited by

                        Wanted to provide an update regarding this issue to share awareness for those who are running into the similar issue I was experiencing.

                        I stumbled upon this forum, https://forum.proxmox.com/threads/not-showing-correct-ram-for-vm.70219/ and I confirmed inside of the Proxmox VM configuration, I had HotPlug enabled for both Memory and CPU.

                        As soon as I removed this from the VM Option and reboot, it resolved my issue and now I can see the correct Memory Allocation in the PFSense Dashboard.

                        a312e75c-a55b-48ae-80f0-93883e14f387-image.png

                        9ba076be-333f-4ac2-aa09-643d53798aef-image.png

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