Hi,
i'm trying to follow the steps from the Virtualization WWDC22 session. The sample app provided works ok "as is", but if I use the same APIs in my own app (i.e. a project I started from scratch), I get errors such as
Internal Virtualization error. Installation service returned an unexpected error.
when downloading the "best supported" image via VZMacOSRestoreImage.fetchLatestSupportedWithCompletionHandler, and
Internal Virtualization error. Unable to connect to installation service.
if I try and install one I downloaded myself.
I did add the
<key>com.apple.security.virtualization</key>
<true/>
entitlement to my own app and (since this is arm), it is codesigned (with -) . But could it be that there is some other application-level flag or setup needed to enable virtualization use?
Since I'm calling the exact same APIs, and neither seem to depend on much prior setup I could get wrong, it seems weird that they work in the sample app but not when called from my own app...
Ideas? thanx!
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/binaryto list the entitlements. - You can call
VZVirtualMachineConfiguration.validateon 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?
