search

relf108 / OSX-KVM-installer

An automation of the cli based installation steps for the kholia/OSX-KVM project. OSX-KVM-installer allows users to set up a fully functioning OSX VM with one command. Tested on Arch and Debian based Linux environments
Other
26 stars 3 forks source link

OSX-KVM-installer #3

Closed hiroshclan closed 3 years ago

hiroshclan commented 3 years ago

After i follow your Post Installation guide and finish all setup proces, i can't find the OSX-KVM-installer to run osx_kvm_runner in OSX-KVM-runner directory To run new macOS installation, i choose catalina number 13 in fetch list, and succesed follow all the instalation guide

relf108 commented 3 years ago

It looks like the virt machine manager setup can sometimes throw an exception if the environment is a little atypical and therefore prevent the code from reaching the runner setup. I've added a try catch block around this and the program should now continue if it fails to add the vm to the manager as this is not a big deal.

In the short term, you can download the runner directly from https://github.com/relf108/OSX-KVM-runner/releases/download/beta-2/OSX-KVM-runner

You may need to make it executable after downloading with

chmod +x OSX-KVM-runner

then run it with

./OSX-KVM-runner

Thanks so much for getting involved in the project and let me know if you encounter any more issues.

hiroshclan commented 3 years ago

me too :) but now i faced new problem this is the ss of the error Screenshot from 2021-01-14 11-56-30

relf108 commented 3 years ago

Run without sudo. Virsh networking behaves very differently depending on its permissions.

hiroshclan commented 3 years ago

it same , run without sudo Screenshot from 2021-01-14 13-39-06

relf108 commented 3 years ago

In that case re-run the installer but skip the post installation steps (close the vm when it pops up) and then run the runner again. The installer has code in it that should fix networking issues and I'll update the runner to do the same. Thanks again for bearing with me through this. It's been an enormous help in working the kinks out of the code :)

EDIT: just finished updating the runner. Try extracting this and running it without sudo again ./osx_kvm_runner. You may need to chmod +x it again osx_kvm_runner.zip

hiroshclan commented 3 years ago

thank you for your hard work, this can't be such an easier without your script, now i must dealing with this damn slow connection and quota limitation from my provider, i will let you know after this runner process done, thank you so much :)

hiroshclan commented 3 years ago

i'm sorry, but it still error on tap0 Screenshot from 2021-01-14 14-49-18

relf108 commented 3 years ago

Could you show me the output of running this command sudo ip tuntap add dev tap0 mode tap followed by running the runner again.

hiroshclan commented 3 years ago

octl(TUNSETIFF): Device or resource busy

EDIT : after rebooting i run "sudo ip tuntap add dev tap0 mode tap" again, but nothing shows up, and then run the runner, but the error is still same

relf108 commented 3 years ago

Try these commands for me and see how it goes.

cd OSX-KVM-installer/OSX-KVM
sudo ./OpenCore-Boot.sh

This behavior is really strange, the code should be dealing with the tap issue as it's quite common and well tested. I'm starting to think the installer failing initially meant the required directories were setup incorrectly. If this doesn't work show me the output and we might need to try a full re-install of the VM.

EDIT: are you using a vpn? In rare cases it can affect the installer when dealing with tap0

hiroshclan commented 3 years ago

yes, i'm so sorry, i think i messed up this time, i dont' have OSX-KVM-installer directory, when i run this command "wget https://github.com/relf108/OSX-KVM-installer/releases/download/v1.5/osx_kvm_installer" a file with a name "osx_kvm_installer" downloaded in my home directory

Screenshot from 2021-01-14 15-36-41

and then i make this file executable with chmod and run the file, after that a folder with a name OSX-KVM created with all it's file in there

Screenshot from 2021-01-14 15-43-06

i finished all mac installation process, but i never find the OSX-KVM-installer directory

relf108 commented 3 years ago

That is actually my bad, I need to update the doco on github to use the correct executable. That being said that folder missing is what would have been causing the errors. From that directory you should now be able to run sudo ./OpenCore-Boot.sh If that works, try creating the OSX-KVM-installer directory yourself and placing the OSX-KVM directory inside it and I think the runner will begin to work.

relf108 commented 3 years ago

I've just edited the release executable to use the latest version so the github documentation should be accurate now.

relf108 commented 3 years ago

Okay so after a little more digging I'm now certain the issue was that you were using an older version of the software which is entirely my fault for forgetting to update the Github release. If what I just suggested doesn't get things going a full re-install using the following command should almost certainly work. Super sorry about the oversight.

pub global activate osx_kvm_installer
osx_kvm_installer
hiroshclan commented 3 years ago

i decide to full re-install, and after instalation process, i've got new problem, the installer resaources were not found Screenshot from 2021-01-14 22-07-00

relf108 commented 3 years ago

Would you be able to send a screenshot of the MacOS DiskUtility so I can see each of your virtual drives?

hiroshclan commented 3 years ago

this is the ss Screenshot from 2021-01-15 10-25-42

relf108 commented 3 years ago

This looks a little unusual. I see you have what looks to be two root partitions. This is what I would be expecting to see. image Did you delete the OSX-KVM directory and any other directories created by the installer before starting the install process again? If not, I would suggest doing so as I think the duplicate hard drives are what is confusing the installer.

EDIT: You may be able to get away with just choosing the re-clone option when OSX-KVM-installer is running if you wanted to try save some time but my first suggestion is probably the safer option

hiroshclan commented 3 years ago

i start from begining, delete all the folder and files, then follow your updated guide in github documentation to full re-install

relf108 commented 3 years ago

Could you show me the other drive titled Mac

relf108 commented 3 years ago

I'm currently doing a full reinstall on my machine following the GitHub instructions to try and replicate your issue

EDIT: I'm going to record the post installation steps so we can ensure you're doing the same thing.

relf108 commented 3 years ago

Are these steps the same as what you did? https://user-images.githubusercontent.com/11174524/104683212-955c9080-574a-11eb-83fd-6cbbacb35231.mp4

EDIT: One thing I've noticed you've done differently is format your root drive as APFS instead of MAC OS Extended (Journaled). This could definitely be causing the problem.

hiroshclan commented 3 years ago

Could you show me the other drive titled Mac

This is the other drive Screenshot from 2021-01-15 11-40-16 Screenshot from 2021-01-15 11-40-32 Screenshot from 2021-01-15 11-40-51

hiroshclan commented 3 years ago

Are these steps the same as what you did? https://user-images.githubusercontent.com/11174524/104683212-955c9080-574a-11eb-83fd-6cbbacb35231.mp4

EDIT: One thing I've noticed you've done differently is format your root drive as APFS instead of MAC OS Extended (Journaled). This could definitely be causing the problem.

yes, what i did is same as in your video, and i leave all the format option in default state

relf108 commented 3 years ago

I'm really confused as to how we managed to get into a state where you have multiple large drives setup without some custom partitioning, I also followed the instructions that I have listed on this repo and couldn't replicate your circumstances. Beyond that, I'm not sure why the default drive formatting would be APFS but try formatting it to use MAC OS Extended (Journaled) instead. Might also be worth just running the first aid tool on each of your drives. Finally, could I get another look at your current directory structure regarding the folders the software has built. I apologize for not having a straight solution as this is getting a little out of my area of expertise so I'm just making some educated guesses. Thanks again for your patience :)

hiroshclan commented 3 years ago

it's ok :) i'm so sorry to make you confused, maybe i missed something this installer file after executing cmd "wget https://github.com/relf108/OSX-KVM-installer/releases/download/1.0.3/osx_kvm_installer" Screenshot from 2021-01-15 13-40-24

this OSX-KVM-installer Screenshot from 2021-01-15 13-40-35

inside OSX-KVM-installer's folder Screenshot from 2021-01-15 13-40-46

inside OSX-KVM's folder Screenshot from 2021-01-15 13-41-01

inside OSX-KVM-runner's folder Screenshot from 2021-01-15 13-41-28

hiroshclan commented 3 years ago

maybe i must repeat from the start and re-install it to make sure about the partition

relf108 commented 3 years ago

That sounds like a good idea. From what I can see this all looks right and you're definitely using the correct command so a re-install should be your best bet. The only thing which might be worth trying before you start again would be to just start the runner and see if it boots a successfully installed version of OSX which may be on the second root partition.

relf108 commented 3 years ago

Assuming issue resolved due to inactivity.