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 376436 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.
Parents
  • 0

    Hi All,

    We have received all the output and our Dev Team is working on this. I will be more transparent by saying that we are trying to get remote access to some of the customers who are affected by this issue. Enabling access ID and allowing SSH access to our IP address can help us investigate. If anyone can share these access to us then please DM me the details. You will be informed prior to any changes or access. 

    Thanks

  • 0 in reply to sachingurung

    It's been 16 days since your post, has there any movement on this issue? I think i pretty clearly laid out the source of the problem.

    Either remove mem= from the kernel options and use some other method to limit memory or calculate the proper value of mem= taking into account the systems memory map.

    I understand development takes time, but this issue has been known for well over a month.

  • 0 in reply to Kevin Brierly

    Does anyone have a test firewall with this issue to give them access to for diagnosis. I imagine that may be what's holding it up. I think many of us just don't feel right about giving an outside entity access to our live configs, but i don't think it will go anywhere without it.

     

    I've looked around a bit and don't see any way to replicate the remapping in a VM in KVM or virtualbox.

Reply
  • 0 in reply to Kevin Brierly

    Does anyone have a test firewall with this issue to give them access to for diagnosis. I imagine that may be what's holding it up. I think many of us just don't feel right about giving an outside entity access to our live configs, but i don't think it will go anywhere without it.

     

    I've looked around a bit and don't see any way to replicate the remapping in a VM in KVM or virtualbox.

Children
  • 0 in reply to Kevin Brierly

    I have given them full access to my boxes in previous UTM and XG betas. They need access when the problem is limited to a single user that they can't replicate in the lab. This issue is wide spread and has been identified by you and others correctly.

    The last UTM rollout broke antivirus scanning for ALL users. It took sophos almost a week to fix that even though paying customers were being affected. During XG 16.05RC1, a bad rollout caused WINGc to crash breaking web categorization for EVERYONE. That took almost 3 days to fix, although the bad IPS updated affected paid and home users alike.

    This problem is only affecting home users. I am sure sophos is hard at work fixing it as we speak[:^)]

  • 0 in reply to Kevin Brierly

    I was able to replicate the issue in a VM that I gave 8GB of RAM in an earlier post. Others should be able to replicate it as well I think.

    community.sophos.com/.../326292

  • 0 in reply to MichaelHigginson

    I spun up a vm and was able to get a memory map with the issue as well. If i could figure out how to get a second home license i'd put XG on it and let them go crazy.

    Hopefully they can work it out from the one person that's offered up access. As stated a couple times now i think they have everything needed to know what's wrong, they just need to come up with a fix. Be it changing the home license limit to 8G, or calculating mem= to take into account memory maps, or using a memory balloon time service to consume the extra memory