limactl stop kills child processes on Windows preventing shutdown sequence

[arixmkii]

Description

Some time ago I reported similar issue with CTRL-C command for containers #1284 This was fixed by decoupling long living HA into independent console host (new process group).

Then SIGINT to this process was implemented via sending CTRL-C through syscalls

lima/pkg/osutil/osutil_windows.go

Line 35 in 7ce6a7a

return windows.GenerateConsoleCtrlEvent(syscall.CTRL_BREAK_EVENT, uint32(pid))

The problem is that it has QEMU VM and potentially SSH master (this requires additional testing) attached withing the same process group and it will immediately kill QEMU.

It causes a lot of error logs, sometimes results in ERROR CODE 130 from limactl stop and with QEMU it causes data loss for virtual hdd changes not flushed.

Possible solutions:

1. start QEMU in new process group on Windows
2. use qemu-system-x86_64w.exe (w here is for Windows GUI like process, which is automatically detached from console host)

This manifests in integration tests "restart" scenario. File is lost.

I can work on implementation, when decision is made on the best option.