search

oraclebase / vagrant

Vagrant Builds
https://oracle-base.com/
GNU General Public License v3.0
190 stars 167 forks source link

Problem with node1 #9

Closed jfekete1 closed 3 years ago

jfekete1 commented 3 years ago

Hello Tim, I'm trying to use the ol7_19. The dns and the node2 machine sets up itself and starts without any problems, however when I try to do a vagrant up on node1 I get the following error: C:/HashiCorp/Vagrant/embedded/gems/2.2.7/gems/net-scp-1.2.1/lib/net/scp.rb:398:in 'await_response_state': scp: /tmp/vagrant-insert-pubkey-1600895252: Cannot allocate memory (RuntimeError)

I have 16GB memory in my laptop and for this version it used to be enough.

jfekete1 commented 3 years ago

Sorry, the issue is not with your code. https://github.com/hashicorp/vagrant/issues/11166

This is caused by the latest windows update...

oraclebase commented 3 years ago

Hi. Sorry for the late reply. I was in bed when this came through. :)

Similar to you, and that post, I have seen this several times on my main laptop (Windows 10). I have 32G of RAM, but still get this from time to time. When I first looked into it I found a reference to the way VirtualBox allocates memory. Basically, if you ask for 7G RAM for a VM, it looks for a contiguous chunk of memory of the size 7G. If it can't find it, it fails. This means that even systems with large amounts of memory can fail to grab something like 7-10G of RAM, if they are unlucky about where in the memory the existing programs are sitting.

Sometimes I could work around this by closing a couple of programs or tabs in a browser (I have a lot) and starting the VM. Sometimes I had to close more stuff. On occasion I had to reboot my laptop and start the VMs before I opened any other programs. The experience varied. At one point I found my NVIDIA control panel service always seemed to be the blocker. :)

I've never seen this issue on Linux or Mac hosts. I test most of my builds, especially RAC builds, on a 16G RAM MBP and an old 24G Linux host (from back in the day when 24G was a big deal). I've never seen the problem on them. I don't know if there is something different about the implementation of VirtualBox on Linux and Macs, or weather the underlying OS system calls for memory react differently on them compared to Windows.

Either way, the workaround seems pretty consistent for me. Hopefully for you too.

Good luck! :)

jfekete1 commented 3 years ago

Hi Tim,

Thank you very much for your answer. Your workaround did help. If disable NVIDIA control paneI and reboot my laptop, then even my 16GB RAM is enough. So I think you are right, the problem must be with the way how VirtualBox allocates memory and how certain Windows 10 services are wasting memory.

Thank you again for helping me out, you are truly awesome !! 👍

oraclebase commented 3 years ago

Great news. I'm glad it worked for you.

FYI: I put out a video this weekend explaining the overall process.

https://www.youtube.com/embed/Tmm9o5MusA8

Clearly you don't need it as you've already done it, but it might help you if you are explaining it to someone else. 👍

Have fun!

Tim...