2

TL;DR: How to fix __CRASHING_DUE_TO_PRIVACY_VIOLATION__ error when starting Ubuntu VM, which was migrated from Windows 10 host to macOS host?


I was warking inside a guest OS Ubuntu on a host OS Windows 10, and everything was working okay.

Recently however I had to switch to macOS; so I've exported my VM following the first scenario from this answer (though the second seems to be recommended, it didn't work for me, unfortunately, — the VM just didn't appear in the list). Now, when I try to start my VM on a MacBook, a couple of seconds after I choose to boot "Ubuntu", the VM "crashes unexpectedly" with the following logs (excerpt):

Thread 4 Crashed:: Dispatch queue: com.apple.root.default-qos
0   libsystem_kernel.dylib            0x00007fff6******* _abort_with_payload + 10
1   libsystem_kernel.dylib            0x00007fff6******* abort_with_payload_wrapper_internal + 80
2   libsystem_kernel.dylib            0x00007fff6******* abort_with_payload + 9
3   com.apple.TCC                     0x00007fff6******* __CRASHING_DUE_TO_PRIVACY_VIOLATION__ + 163
4   com.apple.TCC                     0x00007fff6******* __TCCAccessRequest_block_invoke.114 + 500
5   com.apple.TCC                     0x00007fff6******* _tccd_send_message_block_invoke + 231
6   libxpc.dylib                      0x00007fff6******* _xpc_connection_reply_callout + 36
7   libxpc.dylib                      0x00007fff6******* _xpc_connection_call_reply_async + 69
8   libdispatch.dylib                 0x00007fff6******* _dispatch_client_callout3 + 8
9   libdispatch.dylib                 0x00007fff6******* _dispatch_mach_msg_async_reply_invoke + 369
10  libdispatch.dylib                 0x00007fff6******* _dispatch_kevent_worker_thread + 1316
11  libsystem_pthread.dylib           0x00007fff6******* _pthread_wqthread + 362
12  libsystem_pthread.dylib           0x00007fff6******* start_wqthread + 15

I'm not an expert in Apple, Mac, VirtualBox, or Ubuntu (I wish I was!). Can anybody help me identify the problem and fix it?

Parzh
  • 121

1 Answers1

6

The exact same error was fixed by disabling Audio in the settings of the VM for me.