Closed fredericblaison closed 5 years ago
I remember seeing this issue in the past. Try to reboot (to ensure no image is mounted), delete the clover ISO image (e.g. running make clean
), recreate it (make clover
) and check the log file (~/Library/Logs/runMojaveVirtualbox.log) in case it still doesn't work. Make also sure that the VM really boots from the Clover ISO image.
Thanks much Alexander but in which directory I should run make
?
created: /tmp/macOS-MojaveClover.dmg
cp: /Volumes/Clover-v2.4k-4533-X64/*: No such file or directory
cp: directory /Volumes/NO NAME/EFI/CLOVER does not exist
cp: directory /Volumes/NO NAME/EFI/CLOVER/drivers64UEFI does not exist
Let me see it.
I believe that I have an issue with xz
which is installed but not linked in /usr/local
due to macOS SIP
/Applications/RunMojaveVirtualbox.app/Contents/Resources/runMojaveVirtualbox.sh: line 213: xz: command not found
tar: Error opening archive: Failed to open 'clover.tar'
I'm trying running brew link xz
then I rebuild from scratch (step 1) after erased everything.
Fixed
Issue
On macOS SIERRA
or sup, xy
can be installed but not properly linked making Clover.tar
to fail on decompression.
Workaround Prerequis
Brew
Steps
xy
with Brew
if not installed by the script$ brew link xz
\tmp
or reboot computer/usr/local
is not protected by SIP
. I added another additional brew link xz
to the setup script. Hope this would fix the issue for others. Thanks.
Until I'm wrong, since SIERRA
, /usr/local
permissions can't no longer be modified with chown
. I believe it is due on new SIP
policies (?). It makes necessary to create a subfolder in /usr/local
prior to be able to install and set any file with appropriate permissions or links; one of the reason why Brew
can get some issues.
True, but brew
is using /usr/local/Homebrew
that is owned by you. Afaik brew
is working on 10.11-10.14 (and even on 10.5–10.10).
Just tried this today and I’m getting the same issue
Ps: xz already linked
Can you provide the output of the log file?
I removed clover from the setup. So might be fixed now.
To Reproduce Steps to reproduce the behavior:
Expected behavior Start macOS in the Clover boot menu
Additional context Tried fs1: and fs0: where I enter \EFI\Boot\Bootx64.efi No luck.