[Bug]: aarch64-darwin: podman installed from nixpkgs uses wrong path for edk2-aarch64-code.fd

[n8henrie]

Issue Description

podman 4.3.1 installed via nixpkgs, I get an error about the path to edk2-aarch64-code.fd upon podman machine start. Several prior related issues and PRs:

• podman machine init fails on M1 Macbook Air with exit status 1 #12379
• podman machine writes absolute QEMU path to the VM config #13394
• nixpkgs podman and qemu on darwin don't play well together NixOS/nixpkgs#169118
• podman: includes missing edk2-aarch64-code.fd on aarch64-darwin NixOS/nixpkgs#163015
• podman machine init fails on M1 Macbook Air with exit status 1 #12379

It looks like the current code requires minimal changes to work with nixpkgs -- just resolve the symlink to the real location of qemu in the nix path and everything works.

Steps to reproduce the issue

Steps to reproduce the issue

1. nix shell nixpkgs#podman
2. podman machine init
3. podman machine start

Describe the results you received

Error about path to edk2-aarch64-code.fd (sorry, now getting a different error about the socket -- will update this with the error output after a reboot).

UPDATE:

$ podman machine start
Starting machine "podman-machine-default"
Waiting for VM ...
Error: qemu exited unexpectedly with exit code 1, stderr: qemu-system-aarch64: -drive file=edk2-aarch64-code.fd,if=pflash,format=raw,readonly=on: Could not open 'edk2-aarch64-code.fd': No such file or directory

Describe the results you expected

Podman starts

podman info output

$ podman --version
podman version 4.3.1


`podman info` gives an error

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

No

Additional environment details

MacOS 13.1, nixpkgs 22.11

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[ashley-cui]

Reopening, as the patch was reverted.

[n8henrie]

@ashley-cui -- thank you kindly, I think this perhaps can be closed as I've found a reasonable workaround. At least it seems reasonable to me :)

For whatever reason, $out/share/qemu/edk2-aarch64-code.fd is not symlinked from pkgs.qemu to anywhere convenient for nix users on nix-darwin that are using a declarative config. It is symlinked into ~/.nix-profile for anyone using nix profile install nixpkgs#qemu, and one can convince nix-darwin to symlink to /run/current-system/sw/share/qemu/edk2-aarch64-code.fd by including the below line in their configuration.nix:

environment.pathsToLink = ["/share/qemu"];

With either route, once one has a semi-durable path to edk2-aarch64-code.fd, this path can be used in e.g. ~/.config/containers/podman/machine/qemu/podman-machine-default.json. The downside to this approach is that one loses the reproducibility for which nix is famous (as there is no guarantee what version of qemu is providing that path), but on the other hand it should work as well as the current homebrew approach.