Resolve symlink path for qemu directory if possible

[n8henrie]

Fixes #17026
Fixes NixOS/nixpkgs#169118

Related: NixOS/nixpkgs#163015

Does this PR introduce a user-facing change?

None

[n8henrie]

Please write a regression test for what you're fixing. Even if it
seems trivial or obvious, try to add a test that will prevent
regressions.

Adding [NO NEW TESTS NEEDED] as I don't see any related existing tests, the only change is following symlinks on darwin (not fedora).

However, an analogous change may be useful for nix users of aarch64-linux -- I don't know, will experiment.

[n8henrie]

@rhatdan -- it seems that @Luap99 thinks this PR belongs in podman, and I think it makes sense here as well (at least for now -- going forward, if similar issues pop up for other projects or architectures it could be adopted for them as well).

As shown here, this patch seems to work well and would make a big difference for podman users on aarch64-darwin that are using nix (as opposed to homebrew) for package management, which I think is a growing group.

I'm not sure what's going on with those test failures though. My only code change was in pkg/machine/qemu/options_darwin_arm64.go, so I have to assume the windows failure is unrelated.

[rhatdan]

This is fine with me.

[n8henrie]

@rhatdan thanks for your help and feedback with this issue. It looks like you're in the list of approvers. Is this blocked on anything else from my side?

It looks like the CI failure is probably unrelated:

Error: copying system image from manifest list: ... dial tcp: lookup cdn03.quay.io: no such host

[Luap99]

@n8henrie Can you please rebase? While it is not required we often have issues with older PRs that where not fully rebased on main.

I will merge it then.

[n8henrie]

@Luap99 done, thanks!

[Luap99]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, n8henrie

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Luap99]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Luap99]

/lgtm
/cherry-pick v4.4

[openshift-cherrypick-robot]

@Luap99: once the present PR merges, I will cherry-pick it on top of v4.4 in a new PR and assign it to you.

In response to this:

/lgtm
/cherry-pick v4.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@Luap99: new pull request created: #17429

In response to this:

/lgtm
/cherry-pick v4.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.