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

A customization command failed: setting amount of memory #56

Open
JohnFF opened this issue Apr 10, 2020 · 1 comment
Open

A customization command failed: setting amount of memory #56

JohnFF opened this issue Apr 10, 2020 · 1 comment

Comments

@JohnFF
Copy link
Contributor

JohnFF commented Apr 10, 2020

On latest, after running vagrant up for the first time on a fresh instance, and subsequently.

A customization command failed:

["modifyvm", :id, "--memory", 6041]

The following error was experienced:

#<Vagrant::Errors::VBoxManageError: There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["modifyvm", "845e0e02-a047-4a96-acff-e262cbc762e1", "--memory", "6041"]

Stderr: VBoxManage: error: Invalid RAM size: 6041 MB (must be in range [4, 3584] MB)
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "COMSETTER(MemorySize)(ValueUnion.u32)" at line 625 of file VBoxManageModifyVM.cpp

Please fix this customization and try again.

@JohnFF
Copy link
Contributor Author

JohnFF commented Apr 10, 2020

Ah I see what this is - the changes to make it use 1/4 of system memory mean that on a beefy machine it'll blow an internal limit.

Hack the Vagrantfile where it says mem = mem / 1024 / 4 so that it's just maxed out to 3584.

Happy hacking!

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

1 participant