Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

packer hangs when I set the memory size to 8196 - for creating virtualbox-iso #39

Closed
yqian1991 opened this issue Aug 10, 2015 · 8 comments

Comments

@yqian1991
Copy link

I want to create a box by OSX Yosemite 10.10.4,

the default memory size is 2048 in template.json, when I changed the size to 8196 and use packer to build the vbox, then packer hangs and show
Waiting for SSH to become available...

The GUI is just black, and nothing happened.

@timsutton
Copy link
Owner

I've heard reports from @chilcote before that he had a similar problem - at least, SSH not responsive - with VMware Fusion as well once he bumped the RAM size up to 4096.

This all seems odd, given that I can make an OS X VM manually with plenty of RAM and it functions as expected.

@chilcote
Copy link

The vmware-vmx provider seems to work irt to ssh with >2048 set.

@mattieb
Copy link
Contributor

mattieb commented Nov 5, 2015

This seems to be a VirtualBox problem. I can't create a straight OS X VM with 4 GB RAM either—it simply fails to boot.

@cybertk
Copy link

cybertk commented Nov 30, 2015

I fixed this by increasing vram to 128mb

["modifyvm", "{{.Name}}", "--vram", "128"]

@mattieb
Copy link
Contributor

mattieb commented Nov 30, 2015

I wonder if this is what was causing the problems referenced in PR #49.

On Nov 29, 2015, at 9:37 PM, cybertk [email protected] wrote:

I fixed this by increasing vram to 128mb

["modifyvm", "{{.Name}}", "--vram", "128"]

Reply to this email directly or view it on GitHub.

@mattieb
Copy link
Contributor

mattieb commented Nov 30, 2015

This is a different problem than #49, but it is true that the box finishes booting if it has 4096 MB RAM and at least 128 MB VRAM. 64 MB VRAM didn't work. Build is still running; I'll see how that goes.

@mattieb
Copy link
Contributor

mattieb commented Nov 30, 2015

The above-mentioned build went fine. It did not solve the ARD problem (I'm perpetually on the lookout for a fix for that… but I digress.)

I would be okay with bumping up the VRAM to 128 MB (which is the maximum) by default, to make adjusting the RAM size less obtuse.

@timsutton
Copy link
Owner

Thanks all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants