Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • +9 person also asked this people also asked this
  • Locked Locked
  • Replies 130 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 376380 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Did the RAM limits change for Home edition for 16.05.2 to 4GB?

MichaelHigginson

Did the limits for RAM on Home edition get changed with SFOS 16.05.2 MR2? I'm only seeing 4GB after update. Still only showing 4GB after rolling back to SFOS 16.05.1 MR-1. I was seeing 6GB usable before upgrade.



This thread was automatically locked due to age.
  • 0 in reply to MichaelHigginson

    No idea I'm fairly new to sophos XG and have only used the 16.05 line.

  • 0

    Hey,

     

    after a new Installation on an ESXI 6.5 Server, it is possible to use the 6 GB of Ram.

     

    My old Installation still having the 4GB of RAM Problems.

     

  • 0

    Ok so I did a test upgrade from 16.01.3 to 16.05.1 to 16.05.2 on a virtual machine with 8GB of ram to try and simulate what those with physical HW with greater than 6GB are seeing. For those who are using virtual appliances running 16.05.2 try taking a snapshot/checkpoint and increasing your VMs memory to 8GB.

     

    Here's what 16.01.3 looks like booting up with 8GB of RAM.

    Here's its boot params


    16.05.1 boot after upgrade from 16.01.3

    its boot params

    16.05.2 boot image. Note on this one it first showed 8000MB, but as soon as I tried to sign into the cmdline the system rebooted and then showed 4968MB.

    Here's what 16.05.2 boot params look like after I was able to get signed in. To me it seems like before this release there wasn't a check/restriction being set but now with 16.05.2 it is doing a restriction via those kernel boot params. For whatever reason they're not getting applied correctly.

  • 0 in reply to MichaelHigginson

    Yep this is a very visual representation of what i was saying. As soon as the mem=6G was added the memory gets mapped out of use. i'm thinking it might be more of a rehash of the memory hole for device drivers issue than a PCI address collision as i didn't see anything about a collision in the boot messages

    There might be other ways to limit available memory like memmap= instead of mem= but obviously from our side we can't play with the kernel options.

    trying to get exactly 6G into a system is going to be hard. I think a 6GB dimm or 2 x 3GB dimms are hard to come by. I'm not a big fan of running mismatched dimms(2G+4G)

     

  • 0 in reply to MichaelHigginson

    I'm thinking the parameter is not applied properly for some reason:

    Clear documentation for this kernel parameter is hard to come by unfortunately.

    As for my device, I only have one slot of memory and as far as I know, sticks of 6gb do not exist so I'm stuck with that.

  • 0 in reply to MichaelHigginson

    I wonder if all of this is causing my next problem.

    When the "Patterns" update .... the firewall stops working. ( Own post )


    If this is related to my singel 8GB and 64bits bios and the 6GB limit in the software i dont know.

    But if the problem resists over the next month, I have to go back to my SmoothWall again.

    Sadley.

  • 0 in reply to John Atkins

    I'm wondering if we need to open a new forum topic for this. I haven't seen any input from sophos for quite a while.

    I think at least 2 of us have discovered what the trigger was for having 4G of ram out of 8G. The mem=6G kernel option.

    It's not working like they thought and needs to be revisited. 

    As far as the answer on the memory license not changing for MR2 their previous statement that nothing was changed is WRONG.

    They introduced a kernel memory limit, and that kernel memory limit is not working as they intended on certain hardware configurations.

     

  • 0 in reply to Kevin Brierly

    started a new discussion to see if they respond.

  • 0

    Nothing new for a few days, thought I would post and I see nothing new on  new post about the issue.

    Just to add something, I am seeing the same boot image memory restriction too.

    BOOT_IMAGE=16_05_2160 quiet maxcpus=4 mem=6G ZD=80 SM=0 ro console=tty0 console=ttyS0,38400n8 console=ttyS0,9600n8

  • 0

    Hi All,

    We are investigating the issue, please be sure, we are gathering as much information to provide a better RCA on this matter.  Can we get the output of the following two commands:

    1. cat /proc/meminfo | grep -i memtotal
    2. free

    3. dmidecode -t memory

    Alongside, the users who saw 8 GB RAM utilization for the Home editions was a defect in the initial implementation due to which the SFOS, used to scale up to full available capacity. The defect (NC- 16008) got resolved recently.

    Thanks