One thing you can do is to compile the VM without the external plugins as they are optional. It disables some features (git, Cairo, SDL, ...) but it decreases the memory footprint. This can also be done after the compilation by removing the plugins in the VM folder.

In addition you can use a stack VM instead of a cog VM, which removes the code related to the JIt and the machine code zone.

2016-02-05 5:08 GMT+01:00 Ben Coman <btc@openinworld.com>:

Is there a minimal-VM that can be used to run the minimal-IMAGE [1] ?
It would be nice for [1] to include an a step....
�� PharoVMBuilder buildUnix32minimal.
since the VM is also part of "how small can we go".

My reason for asking is that also less generated VM code might shorten
the edit-compile-run loop when�� I try porting the VM to a Xen Rump
kernel

Also nice would be an example of how to invoke the tests in a minimal
image from the commandline.

cheers -ben

[1] https://github.com/pharo-project/pharo-minimal-scripts