Virtualization.framework VM execution ownership and crash reclamation on Intel macOS Monterey

[jegheloo]

I'm trying to establish the actual process/lifetime ownership semantics of VZVirtualMachine on Intel macOS Monterey 12.7.x.
The specific question is:
If a process creates and owns a running VZVirtualMachine, and that process is terminated abruptly — for example via crash or SIGKILL — is the underlying VM/vCPU execution guaranteed to terminate as part of that process's reclamation?
In particular, I'm trying to understand the relationship between:

• the process that owns the VZVirtualMachine object,
• the com.apple.Virtualization.VirtualMachine / XPC backend process,
• and the actual Hypervisor-backed guest execution.
  I'm not looking for normal shutdown behavior through stop() or graceful cleanup. The security requirement is stronger: the guest must not be able to continue executing indefinitely after the execution-owning process has been destroyed.
  I've found reports where Virtualization.framework-related backend/XPC processes appear to survive certain failure paths on newer macOS versions, but I haven't found authoritative evidence for Intel Monterey specifically.
  Target environment:
• Intel x86_64
• macOS Monterey 12.7.x
• Virtualization.framework
• abrupt owner-process termination / crash reclamation
  Does anyone know whether Apple documents or guarantees this ownership/reclamation behavior, or has anyone tested it directly on Intel Monterey?
  Apple Developer Forums thread with the full context:
  https://developer.apple.com/forums/thread/848542
  Any firsthand observations, references to source-level behavior, or reproducible tests would be very helpful.

[lforte]

My friend. Forget Intel environments for container. Unless you are trying to use hackintoshes. With M4 and M5 Apple processors, why are you still trying to develop containers for old Intel processors, with less or none GPU powered processors? With no AI boostered GPUs?

See my Native Mac Docker project here: #2312

[jegheloo]

Thanks. For this investigation, Intel Monterey is intentional rather than a platform choice for a new container product.
I need to establish the lifecycle/security behavior of Virtualization.framework on an existing Intel macOS Monterey 12.7.x host — specifically whether guest/vCPU execution can survive the abrupt death of the process owning the VZVirtualMachine.
Apple Silicon and newer macOS behavior is useful context, but it does not establish the property required for this particular target environment.
If you have any observations specifically about Virtualization.framework process ownership, the com.apple.Virtualization.VirtualMachine backend, or crash/SIGKILL reclamation behavior, I’d be very interested.