Replies: 3 comments 2 replies
-
If you are on a M1 you installed the wrong podman version, you need the aarch64 one. |
Beta Was this translation helpful? Give feedback.
-
Yes! Thank you, that was the clear explanation I needed. Clearly, the bug is in the Brew install script that STILL installs to intel path. Much obliged. Again, this is a Brew install script error - it installs to the Intel path, and then, when you have gotten the new /opt path up - use "arch -arm64 brew install XXX" to make it work. Thanks again! PS. Bloody odd that Brew et al. worked flaw- and seamlessly on my work M2 machine without all this monkey business....DS. |
Beta Was this translation helpful? Give feedback.
-
@ashley-cui do we have anything to do with the brew install script? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
for a couple of weeks I've been searching the web for the solution to "qemu exited unexpectedly with exit code -1, stderr: qemu-system-x86_64: Unknown Error" on my Apple M1 Max, Mac OS Venture 13.4.1 machine. Podman installed via brew. (Oddly enough my work machine, M2, does NOT have these problems)
There are fragments of thoughts out there , some say "hey, this worked for me" and then som exotic hack in the deeper intestines and belly of the OS... which probably makes you destroy other things. Then try a couple of them and you'll be happy if your machine ever starts again...
I find this very unsatisfactory. There is clearly a bug, a huge one. Is there any action on it at all? I'm just a developer wanting to use the great tool, not a hacker with clandestine, secret knowledge of how a linux kernel behaves in depth.
There should be some clean, distinct "do this"-list to resolve it.
Any tips about one?
Regards,
Beta Was this translation helpful? Give feedback.
All reactions