Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The QEMU-based VM registered with limactl start-at-login in launchd does not start. #2444

Open
norio-nomura opened this issue Jun 25, 2024 · 1 comment
Labels
area/homebrew Homebrew formula component/qemu QEMU

Comments

@norio-nomura
Copy link
Contributor

Description

launchd only sets the PATH environment variable to /usr/bin:/bin:/usr/sbin:/sbin, so limactl fails to start because it cannot find qemu-system-<arch>.

The VM can be started by adding the following configuration to io.lima-vm.autostart.<instance>.plist:

	<key>EnvironmentVariables</key>
	<dict>
		<key>PATH</key>
		<string>/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin</string>
	</dict>

It would be beneficial if one of the following were done:

  • The above configuration is automatically added to io.lima-vm.autostart.<instance>.plist.
  • The path to the QEMU to be used can be set in lima.yaml, and limactl can utilize it.
  • An equivalent to the QEMU_SYSTEM_<ARCH> environment variable can be set in lima.yaml, and limactl can utilize it.

Thanks,

@AkihiroSuda AkihiroSuda added area/homebrew Homebrew formula component/qemu QEMU labels Jun 25, 2024
@afbjorklund
Copy link
Contributor

This needs to go in _config (somewhere), and not be recorded in the instance lima.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/homebrew Homebrew formula component/qemu QEMU
Projects
None yet
Development

No branches or pull requests

3 participants