Thank you. I read the linked disk-image guidance for macOS 27 and later. Our remaining resource is VZMacAuxiliaryStorage, rather than VZEFIVariableStore. For the same VM after a normal guest shutdown and guestDidStop(_:), with the application submitting no further mutable work, does the supported boundary also cover all outstanding framework or helper-process writes to the Mac auxiliary-storage file, so another process may read and later use the disk image and auxiliary storage as a pair? Separately, what synchronization sequence, if any, establishes a durable and mutually consistent disk-plus-auxiliary-storage checkpoint, and what runtime versions does that guidance cover? We are not proposing a forced stop as a clean-shutdown substitute.