-
-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vdmutil attach fails in patchEFI #49
Comments
Thanks for the feedback. Is the |
Yes, I installed it by doing: |
Maybe the Kernel Extension has not been acknowledged at the bottom of "macOS Preferences > Security & Privacy > General"? |
I had acknowledged the kernel extension, but apparently the MacBook must be restarted before the launchctl service will start. The patchEFI function worked after reinstalling paragon-vmdk-mounter (just to be safe) and restarting, and I'm in the macOS install now. Thanks for pointing me in the right direction. |
Your script runs fine until attempting to attach the vdi image in the patchEFI function, at which point it fails for me with a VDM API Error.
I ran vdmutil using the -verbose switch like so to get more details:
/usr/local/bin/vdmutil attach -verbose "/Users/aroper/VirtualBox VMs/Mojave 4GB RAM.vdi"
...and see this output:
Looking for VDM Contoller...
No service found.
Error 0x00000001 : VDM API Error.
I've googled for this vdmutil error and haven't found anything relevant. Any suggestions would be appreciated.
In case it matters, the version of Paragon VMDK Mounter that's installed is 2.4.
runMojaveVirtualbox.log
The text was updated successfully, but these errors were encountered: