autostart: Ensure instance is started/stopped by `launchd` or `systemctl` #4139

norio-nomura · 2025-10-05T08:51:15Z

This PR is formed with two parts:

autostart: Refactor to add autoStartManager to prepare for the following commit
autostart: Ensure the instance is started/stopped by launchd or systemctl

Refactor to add `autoStartManager`

Hide creating/deleting an autostart entry file into Register/Unregister as the implementation details.
Separate the launchd and systemd-specific code into packages.

Use `launchctl` or `systemctl` to start/stop the instance if it’s registered to autostart.

If the instance isn’t launched by launchd, it won’t be stopped on log out.

Affected sub commands:

limactl start
limactl stop
limactl restart
limactl edit
limactl shell

API changes

`pkg/autostart`

Introduced AutoStartedIdentifier():
- If not empty, it indicates whether the instance was started by launchd or systemd.
Added RequestStart():
- Delegates the operation to launchd or systemd.
Added RequestStop():
- Delegates the operation to launchd or systemd.

`pkg/autostart/launchd`

Added AutoStartedServiceName():
- Uses the XPC_SERVICE_NAME environment variable as the service name.
Added RequestStart():
- Uses launchctl enable service-target to avoid failing bootstrap.
- Uses launchctl bootstrap domain-target plist-path.
Added RequestStop():
- Uses launchctl bootout service-target if the instance is launched by launchd.
Added --progress to the limactl option in io.lima-vm.autostart.INSTANCE.plist:
- Required to support limactl start --progress.

`pkg/autostart/systemd`

Added AutoStartedServiceName():
- Uses CurrentUnitName() by github.com/coreos/go-systemd/v22/util as the service identifier.
Added RequestStart():
- Uses systemctl --user start unit-name.
Added RequestStop():
- Uses systemctl --user stop unit-name if the instance is launched by systemd.
Added --progress to the limactl option in [email protected]:
- Required to support limactl start --progress.

`pkg/hostagent`

Add AutoStartedIdentifier to Info.
- If not empty, it indicates whether the instance was started by launchd or systemd.

`pkg/instance`

StartWithPaths():
- Use autostart.IsRegistered() to check if the instance is registered to autostart.
- If launchHostAgentForeground is true, ignore autostart registration.
- If the instance is registered to autostart, use autostart.RequestStart() instead of launching HostAgent.
StopGracefully():
- Use autostart.RequestStop().
Restart(), RestartForcibly():
- Use autostart.IsRegistered() to skip networks.Reconcile() if the instance is registered to autostart.

AkihiroSuda · 2025-10-06T00:29:19Z

How to test this PR?

AkihiroSuda · 2025-10-06T00:30:04Z

Also please explain what issue is being solved by this PR

norio-nomura · 2025-10-06T00:59:52Z

Also please explain what issue is being solved by this PR

opened #4141

go.mod

AkihiroSuda · 2025-10-09T07:32:09Z

pkg/autostart/systemd/systemd.go

Should be *_linux.go?

Code that is platform-dependent and can only be built on Linux is already isolated in systemd_linux.go. systemd.go has code that can be built on any platform, only the operation is platform-dependent.

If we put the code itself included in systemd.go into systemd_linux.go, I think the number of dummy codes required for systemd_others.go will increase.

AkihiroSuda · 2025-10-09T07:32:22Z

pkg/autostart/systemd/[email protected]


 [Service]
-ExecStart={{.Binary}} start %i --foreground
+ExecStart={{.Binary}} start %i --foreground --progress


AkihiroSuda · 2025-10-09T07:33:08Z

pkg/autostart/launchd/launchd.go

Should be *_darwin.go

The code included in launchd.go is based on the darwin platform, but the build is not based on the darwin platform.

The runtime guard should be enough.

AkihiroSuda · 2025-10-09T07:33:23Z

pkg/autostart/launchd/io.lima-vm.autostart.INSTANCE.plist

 		<string>start</string>
 		<string>{{ .Instance }}</string>
 		<string>--foreground</string>
+		<string>--progress</string>


Since there is no way to arbitrarily pass the --progress option from the limactl start process that the user starts to the limactl hostagent that is started via launchctl, It is to be handed over at the time of registration.

limactl hostagent collects progress logs regardless of whether there is a process to observe progress.

Why is --progress needed here?

To pass --progress to limactl hostagent.

User -> limactl start --progress -> launchctl -> launchd -> limactl start --progress -> limactl hostagent --progress.
There is no api to passing --progress from user initiated limactl start to limactl hostagent via launchctl.

- Hide creating/deleting an autostart entry file into `Register`/`Unregister` as the implementation details. - Separate the `launchd` and `systemd`-specific code into packages. Signed-off-by: Norio Nomura <[email protected]>

…ctl` If the instance isn’t launched by `launchd`, it won’t be stopped on log out. This changes to use `launchctl` or `systemctl` to start/stop the instance if it’s registered to autostart. ## Affected sub commands: - `limactl start` - `limactl stop` - `limactl restart` - `limactl edit` - `limactl shell` ## API changes ### `pkg/autostart` - Introduced `AutoStartedIdentifier()`: - If not empty, it indicates whether the instance was started by `launchd` or `systemd`. - Added `RequestStart()`: - Delegates the operation to `launchd` or `systemd`. - Added `RequestStop()`: - Delegates the operation to `launchd` or `systemd`. ### `pkg/autostart/launchd` - Added `AutoStartedServiceName()`: - Uses the XPC_SERVICE_NAME environment variable as the service name. - Added `RequestStart()`: - Uses `launchctl enable service-target` to avoid failing `bootstrap`. - Uses `launchctl bootstrap domain-target plist-path`. - Added `RequestStop()`: - Uses `launchctl bootout service-target` if the instance is launched by `launchd`. - Added `--progress` to the `limactl` option in `io.lima-vm.autostart.INSTANCE.plist`: - Required to support `limactl start --progress`. ### `pkg/autostart/systemd` - Added `AutoStartedServiceName()`: - Uses `CurrentUnitName()` by `github.com/coreos/go-systemd/v22/util` as the service identifier. - Added `RequestStart()`: - Uses `systemctl --user start unit-name`. - Added `RequestStop()`: - Uses `systemctl --user stop unit-name` if the instance is launched by `systemd`. - Added `--progress` to the `limactl` option in `[email protected]`: - Required to support `limactl start --progress`. ### `pkg/hostagent` - Add `AutoStartedIdentifier` to `Info`. - If not empty, it indicates whether the instance was started by `launchd` or `systemd`. ### `pkg/instance` - `StartWithPaths()`: - Use `autostart.IsRegistered()` to check if the instance is registered to autostart. - If `launchHostAgentForeground` is true, ignore autostart registration. - If the instance is registered to autostart, use `autostart.RequestStart()` instead of launching HostAgent. - `StopGracefully()`: - Use `autostart.RequestStop()`. - `Restart()`, `RestartForcibly()`: - Use `autostart.IsRegistered()` to skip `networks.Reconcile()` if the instance is registered to autostart. Signed-off-by: Norio Nomura <[email protected]> bump `coreos/go-systemd` to v22.6.0 Signed-off-by: Norio Nomura <[email protected]>

…hctl bootstrap` Because instances may be stopped without unloading the plist file. e.g. `limactl stop -f` or `limactl factory-reset`. If the plist file is not unloaded, `launchctl bootstrap` will fail. Signed-off-by: Norio Nomura <[email protected]>

norio-nomura · 2025-10-09T08:57:48Z

How to test this PR?

I was researching how to test and took a detour to fix test-port-forwarding.pl. I will consider it again.

norio-nomura marked this pull request as draft October 5, 2025 08:55

norio-nomura force-pushed the improve-autostart branch 7 times, most recently from 783c0f2 to 428fcb1 Compare October 5, 2025 12:13

norio-nomura marked this pull request as ready for review October 5, 2025 12:42

AkihiroSuda linked an issue Oct 6, 2025 that may be closed by this pull request

limactl should use launchctl to start/stop instance if it's registered to start-at-login #4141

Open

norio-nomura force-pushed the improve-autostart branch 2 times, most recently from ac9db28 to 31d7007 Compare October 6, 2025 07:05

AkihiroSuda added this to the v2.0.0 milestone Oct 6, 2025

norio-nomura force-pushed the improve-autostart branch 4 times, most recently from 89c500c to 7082f48 Compare October 8, 2025 15:42

AkihiroSuda reviewed Oct 9, 2025

View reviewed changes

go.mod Outdated Show resolved Hide resolved

AkihiroSuda reviewed Oct 9, 2025

View reviewed changes

norio-nomura added 3 commits October 9, 2025 16:47

autostart: Refactor to add autoStartManager

88dfc01

- Hide creating/deleting an autostart entry file into `Register`/`Unregister` as the implementation details. - Separate the `launchd` and `systemd`-specific code into packages. Signed-off-by: Norio Nomura <[email protected]>

norio-nomura force-pushed the improve-autostart branch from 7082f48 to 994efee Compare October 9, 2025 08:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

autostart: Ensure instance is started/stopped by `launchd` or `systemctl` #4139

autostart: Ensure instance is started/stopped by `launchd` or `systemctl` #4139

norio-nomura commented Oct 5, 2025 •

edited

Loading

Uh oh!

AkihiroSuda commented Oct 6, 2025

Uh oh!

AkihiroSuda commented Oct 6, 2025

Uh oh!

norio-nomura commented Oct 6, 2025

Uh oh!

Uh oh!

AkihiroSuda Oct 9, 2025

Uh oh!

norio-nomura Oct 9, 2025

Uh oh!

AkihiroSuda Oct 9, 2025

Uh oh!

AkihiroSuda Oct 9, 2025

Uh oh!

norio-nomura Oct 9, 2025

Uh oh!

AkihiroSuda Oct 9, 2025

Uh oh!

norio-nomura Oct 9, 2025 •

edited

Loading

Uh oh!

AkihiroSuda Oct 9, 2025

Uh oh!

norio-nomura Oct 9, 2025

Uh oh!

norio-nomura Oct 9, 2025

Uh oh!

norio-nomura commented Oct 9, 2025

Uh oh!

Uh oh!

autostart: Ensure instance is started/stopped by launchd or systemctl #4139

Are you sure you want to change the base?

autostart: Ensure instance is started/stopped by launchd or systemctl #4139

Conversation

norio-nomura commented Oct 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Refactor to add autoStartManager

Use launchctl or systemctl to start/stop the instance if it’s registered to autostart.

Affected sub commands:

API changes

pkg/autostart

pkg/autostart/launchd

pkg/autostart/systemd

pkg/hostagent

pkg/instance

Uh oh!

AkihiroSuda commented Oct 6, 2025

Uh oh!

AkihiroSuda commented Oct 6, 2025

Uh oh!

norio-nomura commented Oct 6, 2025

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

norio-nomura Oct 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

norio-nomura commented Oct 9, 2025

Uh oh!

Uh oh!

autostart: Ensure instance is started/stopped by `launchd` or `systemctl` #4139

autostart: Ensure instance is started/stopped by `launchd` or `systemctl` #4139

norio-nomura commented Oct 5, 2025 •

edited

Loading

Refactor to add `autoStartManager`

Use `launchctl` or `systemctl` to start/stop the instance if it’s registered to autostart.

`pkg/autostart`

`pkg/autostart/launchd`

`pkg/autostart/systemd`

`pkg/hostagent`

`pkg/instance`

norio-nomura Oct 9, 2025 •

edited

Loading