Post not yet marked as solved
Hi Gavin,
Which version of macOS are you trying to install in the virtual Mac?
If it is a beta of macOS Ventura, you will need to install the latest Xcode beta on the host.
If it's not a beta of macOS Ventura, one possibility is the installation process could not reach Apple's servers.
If that's not a network issue, we will need a sysdiagnose to investigate. In that case, please use "Feedback Assistant" to file a new bug report with a sysdiagnose and you can give us the report numbers to follow up.
Post not yet marked as solved
The GUI Linux support is new in macOS Ventura. You will need to install the beta and the new Xcode to have the missing symbols.
Post not yet marked as solved
Thanks for reporting the problem. It looks like the kernel changed since we tested it.
We'll have to update the documentation with a link to an uncompressed kernel.
Post not yet marked as solved
The new VZMacOSVirtualMachineStartOptions.startUpFromMacOSRecovery is the way to go.
It looks like your VM bundle is corrupted.
When running the app the first time, it creates a directory named GUI Linux VM.bundle in the home directory. That bundle contains the VM's data, including the machine identifier.
You may try to rename or erase the GUI Linux VM.bundle directory to create a new virtual machine from scratch.
Post not yet marked as solved
You are correct in understanding that macOS VMs currently don't support signing into certain Apple services (such as iCloud, iMessage/FaceTime, etc). However, software updates (with and without the help of the Beta Access Utilities) are fully supported on virtual machines.
Post not yet marked as solved
It is not a problem with your project.
Without going into the details, virtual machine lacks the characteristics needed to connect to the services.
Post not yet marked as solved
We have been unable to reproduce with this IPSW.
One hypothesis is the hosts loses network during the restore process but that seems unlikely.
We could use more information about the host system to understand the problem.
Could you please try this?
Run the install process until failure.
When it fails, collect a sysdiagnose of the Mac (https://developer.apple.com/bug-reporting/profiles-and-logs/?name=sysdiagnose - https://developer.apple.com/services-account/download?path=/OS_X/OS_X_Logs/sysdiagnose_Logging_Instructions.pdf)
Report a bug with the Feedback Assistant App with the sysdiagnose.
Reply on this forum with the bug report number. That way we can find it easily.
Post not yet marked as solved
This is strange. We will need to investigate.
Post not yet marked as solved
Oh, right. I didn't notice that on the first point.
Yes, that is wrong. Sandbox is supported but not mandatory.
Now, to get authentication with Apple services to work. Has there been any progress on that front?
This is not supported at the moment.
Post not yet marked as solved
Which version of macOS are you trying to install?
If it is macOS Ventura, you will also need the latest beta of Xcode installed to have all the required host support.
If this is not macOS Ventura in the VM, could you share the link to the IPSW you are using?
Post not yet marked as solved
The instructions are only about the com.apple.security.virtualization entitlement.
The app sandbox is only there in the screenshot because it's a standard property in new projects.
Thanks for this feedback, this is useful.
We'll look into making the documentation better.
Post not yet marked as solved
It sounds like the macOSVirtualMachineSampleApp-Swift app is being run with App Sandbox enabled.
Could it be that you enabled App Sandbox by accident?
If not, could you please share your version of macOS and Xcode? We can try reproducing the issue.
Post not yet marked as solved
Thanks for reporting this error.
One thing that comes to mind is the disk might be full on the host system. When that happens, the guest would see I/O errors for legitimate block operations. The Linux kernel handles that smoothly but user-space apps may not expect such failures.
Could you share the panic logs from the Linux kernel?
From the description, it looks like the binary doesn't have the entitlement.
There are two ways you can verify this.
You can use codesign -d --entitlements :- /path/to/binary to list the entitlements.
You can call VZVirtualMachineConfiguration.validate on your configuration. If the app lacks the necessary entitlement, the exception/error will report that.
If the problem is the entitlement, you can check two settings in your Xcode project:
The "Code Signing Entitlements" (aka CODE_SIGN_ENTITLEMENTS) needs to point to your file.
The binary must be signed.
You also can check the build logs to verify both aspects.
If that's not the problem, can you attach your sample code?
