AppScale on virtualBox errors on customization command.

38 views
Skip to first unread message

Moussa Jimi

unread,
Mar 1, 2017, 5:54:45 AM3/1/17
to AppScale Community
Hi,
I have tried to deploy  appscale 3.1.0 on Virtualbox 5.1.14
I ran the steps:

- install virtualbox
- install vagrant
- download appscale virtual machine
- vagrant init & configuration
- than vagrant up
when i make vagrant up, i have a problem with customization command.
Here are the errors when running vagrant up:

cloud@cloud-TravelMate-P253:~/appscale$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'appscale/releases' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
A customization command failed:

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

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", "16ffd4b5-19b6-4573-9242-c7f6effd7baf", "--memory", "4098"]

Stderr: VBoxManage: error: Invalid RAM size: 4098 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 599 of file VBoxManageModifyVM.cpp>

Please fix this customization and try again.
cloud@cloud-TravelMate-P253:~/appscale$

Chris Donati

unread,
Mar 1, 2017, 11:19:07 AM3/1/17
to appscale_...@googlegroups.com
Hi,

It sounds like your computer may not have enough available memory to give the virtual machine 4GB. You can edit your Vagrantfile (generated by the `vagrant init appscale/releases` command) and change the memory from 4096 to something like 3072. Though at least 4GB is recommended for production, 3GB should work for basic testing.

--
You received this message because you are subscribed to the Google Groups "AppScale Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appscale_community+unsub...@googlegroups.com.
To post to this group, send email to appscale_community@googlegroups.com.
Visit this group at https://groups.google.com/group/appscale_community.
For more options, visit https://groups.google.com/d/optout.

Moussa Jimi

unread,
Mar 1, 2017, 6:29:03 PM3/1/17
to AppScale Community
Hi Chris. It's okay, it runs now. Thank you.
To post to this group, send email to appscale_...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages