How to Request com.apple.vm.* Entitlements?

Is the process to gain the com.apple.vm.networking entitlement outlined above still the process … ?

Yes.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Indeed. I encourage you to prototype your product using that feature.

VZVirtualMachineConfiguration.validate will fail without com.apple.vm.networking entitlement when attempting to setup a VZBridgedNetworkDeviceAttachment for a guest OS even when running as root. It does not seem possible to prototype without the entitlement.

It does not seem possible to prototype without the entitlement.

Yes and no.

This breaks down by entitlement. Let’s start with com.apple.vm.networking. It applies in two cases:

• vmnet framework

• Virtualization framework’s bridged networking support

The former is amenable to the prototype-as-root approach. The latter is not. I strongly recommend against trying to use Virtualization framework from a root context, and your experience suggests it doesn’t help anyway.

Note The original post on this thread specifically mentioned vmnet, and hence my comment.

With regards com.apple.vm.hypervisor, that’s largely irrelevant these days.

For com.apple.vm.device-access, its doesn’t apply to Virtualization framework and thus the prototype-as-root approach works there too.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

So is it possible to prototype with bridged networking with the virtualization frame work at all? Or is the entitlement required? Even code signing with the entitlement locally just immediately results in a killed process, root or otherwise.

It doesn't seem possible to even request the entitlement without paying to enroll in the developer program, sometimes you just want to test if something is possible locally....

So is it possible to prototype with bridged networking with the virtualization frame work at all?

No [1].

Even code signing with the entitlement locally just immediately results in a killed process, root or otherwise.

Correct. This is a restricted entitlement, which means it must be authorised by a provisioning profile. See TN3125 Inside Code Signing: Provisioning Profiles.

It doesn't seem possible to even request the entitlement without paying to enroll in the developer program

Correct.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Well, if you disable SIP you can then disable all entitlement checking on your Mac. See here.

The are three significant problems with that approach:

• Disabling SIP is dangerous. See the IMPORTANT call on the above-mentioned post.

• Disabling SIP significantly changes the behaviour of your Mac. If you get something working with SIP disabled, you can’t be guaranteed it’ll work with SIP enabled.

• This, but even more so, once you start messing with boot arguments.

Honestly, if you want to used bridged networking in the context of Virtualization framework, you might as well just apply for the entitlement.

https://developer.apple.com/contact/request/user-assigned-device-name/ Just req this website

Just an update, the accepted answer is no longer the process. I just logged a DTS TSI and got back this "To request this entitlement, contact your Apple representative. For more information please review the following resource: https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_vm_networking".