Open nkushman opened 4 years ago
Hi Nate,
AFAIK the VMA configuration options have not been thoroughly tested after MaxineVM v2.1. I think that it must have been working at Maxine v2.0 (the version which those documents are based on) but probably somewhere in the process they must have broken.
@zakkak I recall you did some work on VMA, any recall?
I'm having trouble building v2.0. Do you know what version/tag of the mx repo I should be using with v2.0 of Maxine?
Whenever I run mx build I get the error: "no primary suite found" This is because there's no mx.maxine directory. I tried playing around by renaming the directory, and renaming commands.py to suite.py, etc. but I think the version of mx I'm using is probably just not compatible.
I tried syncing mx to version/tag: 5.116.0 (which is was the most recent version as of the v2.0.0 Maxine release date) but that didn't seem to help either.
Any suggestions @kotselidis ?
@zakkak I recall you did some work on VMA, any recall?
@kotselidis I don't recall working on the VMA TBH (just touching some shared code maybe).
I'm having trouble building v2.0. Do you know what version/tag of the mx repo I should be using with v2.0 of Maxine?
@nkushman You will need the mx
from https://github.com/beehive-lab/Maxine-Graal for that.
Hello,
I've compiled and run Maxine with the docker image, following the instructions here: https://maxine-vm.readthedocs.io/en/latest/build.html#developing-using-a-docker-container
mx helloworld runs successfully:
I then compile the VMA image using the command from here: https://maxine-vm.readthedocs.io/en/latest/Virtual-Machine-Level-Analysis.html#building-handlers-into-the-boot-image
(fixing the typo in the documentation to change handler --> handlers)
When I run:
The VM crashes generating the below stack trace. It seems that either there's a problem with the code or the documentation, but I'm not sure which: error.txt