lima fails to start on a fresh OS, fresh install on M3 Pro: Error: Image at 0013FD41000 start failed: Not Found ... Instruction abort: Translation fault, first level
#1996
Labels
Comments
|
AkihiroSuda
changed the title
Instruction abort: Translation fault, first level
|
@AkihiroSuda : I can't easily downgrade any of my machines to test on MacOS <14. And the only Apple Silicon I have is an M3. So, I can't give much useful information to the other questions. Thank you! I didn't even see that |
|
@AkihiroSuda |
|
@ethanzway Could you report to https://gitlab.com/qemu-project/qemu/-/issues ? |
|
rancher-sandbox/rancher-desktop#5943 is another report of this issue with an M3 Max chip: @AkihiroSuda I realize that this seems to be an upstream problem, but shouldn't we keep this issue here open until it is resolved in QEMU, and we have information on which version is required to fix it? At least it makes it obvious to other people running into this problem that it is still unresolved. |
AkihiroSuda
changed the title
Instruction abort: Translation fault, first levelError: Image at 0013FD41000 start failed: Not Found ... Instruction abort: Translation fault, first level
6 tasks
|
Linking the issue on the QEMU repo: |
|
The bundled firmware image lacks the following patch 5ce29ae84db3 ArmPkg/ArmMmuLib AARCH64: Add missing ISB after page table update which addresses an issue that resulted in very similar symptoms on a different system. Please confirm whether the issue is reproducible with this firmware image |
|
Opened a Homebrew PR as an interim workaround until the QEMU upstream bumps up EDK2: EDIT: reverting for compatibility with M1: |
5 tasks
|
Can anybody try the current master? ( https://gitlab.com/qemu-project/qemu/-/issues/1990#note_1673436549 |
|
@AkihiroSuda with |
@AkihiroSuda I'm not sure if your question was directly answered but I am unable to reproduce this issue on my M1 or M2 machines but can reproduce on my M3. What's a bit unusual with the M3 is that I can get Lima to successfully boot 1 per approximately every 5 attempts. |
|
I was able to install with --HEAD on m3 pro |
This is actually quite symptomatic for issues due to missing barrier instructions, such as the one in question. |
|
Can anybody try this on M3? This should work on M1 too. |
got same issue, tried it on m3, worked after following above commands. thanks @AkihiroSuda M3screenshot
Beforelimactl start logsserial*.logAfterlimactl start logs |
5 tasks
|
The issue is expected to be fixed in Lima v0.19.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tip
(EDIT by @AkihiroSuda)
Workaround
Specify
--vm-type=vzinlimactl createlimactl create --vm-type=vz ...Proper fix
Expected to be fixed in Lima v0.19.1
Description
Using Homebrew to install lima on MacOS 14.1.1 (23B2082), Apple M3 Pro, the installation completes successfully, but starting up lima freezes at "INFO[0000] [hostagent] Waiting for the essential requirement 1 of 5: "ssh"" and eventually fails. The log files seem to indicate some type of build error: "Error: Image at 0013FD41000 start failed: Not Found", "Instruction abort: Translation fault, first level".
Checking the logs (serial.log):
The text was updated successfully, but these errors were encountered: