Virtual machines fail to start on macOS Sequoia / Tahoe 26 when running GitLab Runner as launch agent on EC2 Mac hosts

[camilacodes]

Hello, I'm Camila!

I am running tart on macOS EC2 instances (Mac2.metal) AMI Sequoia latest.

On Sonoma images, everything works fine.
But on Sequoia Xcode (latest) and especially Tahoe Xcode 26, I get the following error when trying to start a VM with GitLab Runner + tart:

Error Domain=VZErrorDomain Code=1 
"The virtual machine failed to start." 
UserInfo={
  NSLocalizedFailure=Internal Virtualization error.,
  NSLocalizedFailureReason=The virtual machine failed to start.
}

It looks related to Local Network privacy permissions. When running GitLab Runner as a launch agent/daemon, macOS requires UI confirmation to allow “Local Network” access. Since these EC2 Mac hosts are headless, I cannot manually approve the popup every time I provision a new instance.

My questions:

1.	Is there a way to pre-authorize or bypass the “Local Network” prompt so that VMs created by tart can start without UI interaction?

2.	Is this a known issue with Sequoia / Tahoe 26 images? (since Sonoma still works fine)

3.	What would be the recommended approach for running tart inside a CI/CD environment (GitLab Runner) on macOS EC2, where user interaction with UI is not possible?

Thanks a lot in advance!

[edigaryev]

Closing as duplicate of #1146.