Virtualization error 10007 on macOS installs

[nbeadman]

Using Version 2.1 Beta 6 trying to install macOS 26 Tahoe beta on my MacBook Pro M1 Max, 32G RAM, 1TB (430G free) running macOS Sequoia 15.6 (24G84) and am receiving "Virtualization error 10007. An error occurred during installation. Installation failed." for both macOS 26 Tahoe beta 7 (25A5346a) and macOS Sequoia 15.6 (24G84).

Have successfully installed and run an Ubuntu server distribution and have Xcode 26.0 beta 6 (17A5305f) installed able to communicate with an iPhone running iOS 26.0 (23A5326a). Previously have installed Device Support for macOS 26 beta 2

Here is the console log trying to install macOS Sequoia 15.6 (24G84):

[14:32:46.046] (Info) - nw_context_dealloc Deallocating context <nw_context (null) (sensitive)>
[14:32:46.046] (Info) - nw_protocol_tcp_wake_disconnected [C5.1.1.1:3] tcp disconnected
[14:32:45.045] (Info) - nw_context_purge_endpoints Context <nw_context com.apple.CFNetwork.NSURLSession.{4D87CEDC-766C-4251-A1CE-E501410D5BDB}{(null)}{Y}{3}{0x0} (sensitive)> has more than 0 cache entries, purging 1 from 1 down to 0
[14:32:45.045] (Debug) - nw_channel_purge_idle_block_invoke Purging channel packet pool after going idle
[14:32:37.037] (Debug) - dispatch event 3 pid 923 keychain 0x16b61e568 item 0x1370eaa48
[14:32:37.037] (Debug) - New DLDbListCFPref 0x10f004bd0 for domain 0
[14:32:26.026] (Debug) - -[NWConcrete_nw_path_evaluator dealloc] 2649622C-A80A-4BA4-8422-B93B5F54224F
[14:32:25.025] (Info) - nw_association_schedule_deactivation_block_invoke <nw_association IPv4#2f00b778:443> becoming dormant
[14:32:25.025] (Info) - nw_association_schedule_deactivation_block_invoke <nw_association Hostname#1218d10c:443> becoming dormant
[14:32:16.016] (Debug) - nw_fd_wrapper_close closed <fd_wrapper 13, guarded: false>
[14:32:16.016] (Default) - DFU mode device disconnected
[14:32:15.015] (Info) - boringssl_session_handshake_incomplete(257) [C5.1.1.1:2][0x137173ed0] Handshake incomplete: waiting for data to read [2]
[14:32:15.015] (Info) - boringssl_session_handshake_incomplete(257) [C4.1.1.1:2][0x13717d3a0] Handshake incomplete: waiting for data to read [2]
[14:32:14.014] (Info) - amai: _AMAuthInstallBundleCopyOverrideBuildIdentity: Inserting RestoreKernelCache to Manifest to personalize later
[14:32:14.014] (Info) - MacOS variant present, using MacOS restore path
[14:32:13.013] (Info) - Found IPSW restore bundle path, attempting to unpack it
[14:32:13.013] (Info) - Found a device with a known device registration class: 0x80

and for macOS Tahoe 26.0b7 (25A5346a):

[16:03:59.059] (Info) - nw_context_dealloc Deallocating context <nw_context (null) (sensitive)>
[16:03:59.059] (Debug) - nw_channel_purge_idle_block_invoke Purging channel packet pool after going idle
[16:03:40.040] (Debug) - -[NWConcrete_nw_path_evaluator dealloc] 77DD25CC-C477-4DC5-B3C0-85D612791B6F
[16:03:39.039] (Info) - nw_association_schedule_deactivation_block_invoke <nw_association IPv4#7175e2a0:443> becoming dormant
[16:03:39.039] (Info) - nw_association_schedule_deactivation_block_invoke <nw_association Hostname#eaac740d:443> becoming dormant
[16:03:30.030] (Debug) - nw_fd_wrapper_close closed <fd_wrapper 13, guarded: false>
[16:03:29.029] (Default) - Task <1BFB9F97-4AFF-4C17-9363-D5266D416B9A>.<1> sent request, body S 3496
[16:03:29.029] (Info) - boringssl_session_handshake_incomplete(257) [C1.1.1.1:2][0x124f0bb40] Handshake incomplete: waiting for data to read [2]
[16:03:28.028] (Info) - amai: _AMAuthInstallBundleCopyOverrideBuildIdentity: Inserting RestoreKernelCache to Manifest to personalize later
[16:03:28.028] (Info) - MacOS variant present, using MacOS restore path
[16:03:27.027] (Info) - Setting restore bundle in options to: /var/folders/73/vlk5785d1xz85f1q2pnln8g00000gp/T/com.apple.Virtualization.Installation.5MzWmi/IpswExtract.cS1fvZ

Any ideas?

[insidegui]

@p-linnane reported a similar issue and sent me some logs in private which I haven't had the time to analyze yet, but I don't think this is a bug in VirtualBuddy, it's most likely an issue in macOS and/or the MobileDevice restore system. For anyone having this same issue, please submit a feedback report to Apple via Feedback Assistant.

[nbeadman]

Reported as FB19834168

[insidegui]

Just had the time to check logs submitted by @p-linnane (see #585)

The entries that seem related to the issue are below, all from MobileDevice running in the com.apple.Virtualization.Installation process:

usbmuxd interface explicitly disabled by client.
Client tried to subscribe for device notifications, but disabled both RemoteXPC and usbmuxd.
returned 0x0.
activating connection: mach=false listener=false peer=false name=com.apple.MDRemoteServiceSupport
failed to do a bootstrap look-up: xpc_error=[159: Unknown error: 159]
invalidated after a failed init
activating connection: mach=true listener=false peer=false name=com.apple.remoted
failed to do a bootstrap look-up: xpc_error=[159: Unknown error: 159]
invalidated after a failed init
Starting browsing: <private>
Connection invalidated
Unable to start browsing: <private>

Apparently MobileDevice is unable to find the "device" (in this case the virtual machine) because both interfaces it has for browsing for devices are being disabled somehow. This definitely seems to be a bug in the way Virtualization sets up the restore, or a state management error in some system daemon. I wonder if restarting the host Mac addresses this, assuming you haven't tried that yet?

Shortly before the Client tried to subscribe... log message, I see a check for a defaults key:

found no value for key MobileDeviceRemoteXPCEnabled in CFPrefsSearchListSource<0x1036d8550> (Domain: com.apple.Virtualization.Installation, Container: (null) Non-launch persona: 0)

I wonder if setting that defaults flag would make a difference in the outcome. If anyone having this issue wants to try, that can be done in Terminal by running:

defaults write com.apple.Virtualization.Installation MobileDeviceRemoteXPCEnabled -bool YES

That change can be reverted later with defaults delete com.apple.Virtualization.Installation MobileDeviceRemoteXPCEnabled.

[p-linnane]

I haven't been able to reproduce this on Tahoe beta 8, but will keep an eye on it.

[nbeadman]

@insidegui changing the MobileDeviceRemoteXPCEnabled setting didn't work for me, although my host OS is macOS Sequoia 15.6.1 (24G90).

Here are the commands I ran in OMZ (before deleting):

defaults write com.apple.Virtualization.Installation MobileDeviceRemoteXPCEnabled -bool YES%                                                                    defaults write com.apple.Virtualization.Installation MobileDeviceRemoteXPCEnabled -bool YES
log stream --level debug --style compact --color none --predicate 'process contains "com.apple.Virtualization.Installation" OR senderImagePath contains "MobileDevice" OR process contains "VirtualBuddy"' > ~/Desktop/InstallLogs.log
defaults read com.apple.Virtualization.Installation MobileDeviceRemoteXPCEnabled
result: 1

Fails with the same error, here is InstallLogs.log (compressed):
InstallLogs.log.zip

[insidegui]

I didn't think that was going to fix it, just thought it'd be worth a shot :(

[jankkm]

How much disk space did you give the VM? I've had this issue and it disappeared when giving a larger disk.

[nbeadman]

I tried both 64 and 128 GB

[nbeadman]

Reported as FB19834168 (Virtualization error 10007 on attempting to install macOS in a Virtual Machine). Asked if the same error occurs when using Tahoe as the host OS 🤦. Not able to run Tahoe currently but will update when that changes.

[insidegui]

Asked if the same error occurs when using Tahoe as the host OS 🤦

What's the point of having virtualization if you have to run the beta OS on your host machine anyway, right? 😂

Thanks for the update!

[p-linnane]

FWIW, I haven't been able to replicate this issue on the last few Tahoe betas.

[insidegui]

It hasn't happened for me either. Although for the past few betas I've been updating the VM OTA in System Settings.

[p-linnane]

I spoke too soon. I set up a Monterey VM, had no issues, and then tried to set up a Ventura VM, and immediately ran into the same hang. This is on Tahoe RC 😞.

[alessionossa]

Seeing error 10007 on macOS 26.0.1, trying to install a 26.0.1 VM with VirtualBuddy storage location set to an external SSD. If I change VirtualBuddy Storage location to the internal SSD of my Mac, the installation completes as expected.

[clezcoding]

Heyoo :) I had the exact same issue and this was the solution:

1. Install macOS 26 Device Support.
   1. Sign into Apple Developer portal.
   2. Find "Device Support for macOS 26" and download "Mobile Device Support".
   3. Open the .dmg and run DeviceSupport.pkg.
2. Install Xcode 26 beta.
   1. Go to Apple Developer Resources page and click "View available Xcode betas".
   2. Download "Xcode 26 Beta“ and extract it.
   3. Move Xcode-beta.app to Applications.
   4. Launch it, agree to terms, check the macOS 26 component, the Metal Toolchain Component and click "Install".

For me it helped to install the EXACT Components for the MacOS 26 Version so if you want to install MacOs 26.2 Download the Xcode 26.2 Beta.

Hope it helps!

[nbeadman]

Unfortunately, this didn't work for me. I downloaded the only Device Support for macOS I could find on the Download page which was Device Support for macOS 26 beta 2 Build 1950A4. Then I downloaded Xcode 26.2 (17C52) for Apple Silicon using Xcodes, ran it and installed the Metal Toolchain 26.2 (17C48) as the macOS 26.2 was already built in.

From within Virtual Buddy 2.1 (325) I tried to install macOS 26.2 Developer Beta 3 (25C5948a) which was the closest macOS 26.2 I could see to 26.2, same "Virtualization error 10007. An error occurred during installation. Installation failed"

[ddaddy]

I'm getting the 10007 error when trying to install macOS 13.2 running Virtual Buddy on my 15.7.4 host :(

[ddaddy]

I redownloaded the 13.2 installer and it's now working 🤷‍♂️