Replies: 11 comments 3 replies
-
This issue is expected to be resolved with Rosetta support.
|
Beta Was this translation helpful? Give feedback.
-
@tnk4on But how did it work before? I have another installation with the older machine where it works. I see the difference only in the machine image. |
Beta Was this translation helpful? Give feedback.
-
So, after additional testing it works with recent fedora 39 build. When you create machine with hardcoded previous Example: podman machine init --disk-size 60 --rootful --cpus=4 --memory=8192 --image https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/39.20240407.3.0/aarch64/fedora-coreos-39.20240407.3.0-applehv.aarch64.raw.gz |
Beta Was this translation helpful? Give feedback.
-
This is most likely a qemu-user-static regression then if it worked before so you should check |
Beta Was this translation helpful? Give feedback.
-
sounds like https://gitlab.com/qemu-project/qemu/-/issues/2168 I move this to a discussion as this is not really a podman bug and given the Rosetta implementation should make it in the next version |
Beta Was this translation helpful? Give feedback.
-
for now, using f39 as suggested by @arzahs have fixed the issue here. |
Beta Was this translation helpful? Give feedback.
-
podman is not working for me on MacOS; I've tried 5.0.3, 5.1.0-RC1, and 4.9.4. I've tried enabling rosetta. I've tried the alternate machine image (I get 'Error: short-name resolution enforced but cannot prompt without a TTY' from that image on all podman versions). podman info:
|
Beta Was this translation helpful? Give feedback.
-
Hi, I'm using linux aarch64 and get the same issue. Is there any workaround like updating qemu-user-static? |
Beta Was this translation helpful? Give feedback.
-
When is a new fedora coreos image going to be rebuilt and is this going to contain the fix? |
Beta Was this translation helpful? Give feedback.
-
The issue is still existing. I manually compiled qemu 9.0.2 on fedora 40 and the issue https://gitlab.com/qemu-project/qemu/-/issues/2168 is resolved. |
Beta Was this translation helpful? Give feedback.
-
Having this issue on my Fedora 40 Asahi Remix with M1 Apple Silicon:
|
Beta Was this translation helpful? Give feedback.
-
Issue Description
I got a weird error
qemu-x86_64-static: QEMU internal SIGSEGV {code=MAPERR, addr=0x20}
when trying to run a container withamd64
arch on the arm Macbook after recreating machine with latestmachine init
.It worked well before.
Steps to reproduce the issue
The issue is reproducing for me on all mac machines which has an arm processor.
Describe the results you received
I got error with qemo:
Describe the results you expected
podman info output
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions