Open undrthegraveyard opened 1 year ago
You should probably run Kali Linux in Apple Virtualization instead of QEMU. I've had lots of issues with Kali in QEMU unfortunately.
No idea what you're doing wrong, though. Let's go through the process step by step.
Report back if that does not work. If it does, you can try QEMU, which may or may not work for you.
To what purpose are you attempting to run Kali Linux? It may or may not do what you need inside a virtual machine on Apple Silicon.
Hey, I really appreciate your response. I tried downloading Kali Linux installer image from the link you mentioned above, but for some reason it wasn't working. Then I downloaded the Installer image file from https://www.kali.org/get-kali/#kali-installer-images in .iso format. Followed the same steps you mentioned but an error message popped up which I have attached as a screenshot. It is a disk image error which I really can't wrap my head around. The purpose for me to run kali linux is to just perform some basic penetration testing as part of my course. But now it has become more of a ego thing.
Insufficient data.
You MUST download the "Apple Silicon (ARM64)" installer iso which at the time of this writing is kali-linux-2023.1-installer-arm64.iso. Even if it's not from my link, please confirm that is the case. Or explain what "isn't working" when you tried my link.
You can try verifying the checksum of the iso if you think it's correct. There's no reason why the image format shouldn't be recognized. Please also provide the config.plist of the virtual machine so it can be checked (view the help for how to do that, I can't walk you through it).
More screenshots, video recording, anything - there's nothing for anyone to troubleshoot in that screenshot except an error that doesn't make sense.
Hi, have you have fixed the issue yet? I just encountered this issue today and I need help :)
@cyberRat86 this isn't something to be fixed in UTM as it currently stands. Kali boots fine in UTM in both AVD and QEMU modes. Generally this is going to be a config or disk image issue.
Provide steps to reproduce, exact error messages, troubleshooting steps, etc.
So UTM is useless to me now ??
So UTM is useless to me now ??
I think that depends entirely on your usecase. It sounds like all you're using UTM for is running Kali, and if that's not working, yes, it could be useless.
More broadly, showing up wondering if something is fixed without providing any additional context isn't helpful, or likely to get support for troubleshooting your issue.
If you're having trouble running Kali in UTM, tell us more. What kind of virtualization? What ISO image? What options did you set? What error message did you receive? Be specific. Be precise. Have you gone through the steps I documented above? What was the result?
okay I fixed it lol The way you do not get the UEIF thing is, when setting up Kali on the UTM, there is a part that says BOOT ISO IMAGE, it comes out directly after clicking virtualize. When you put browse next to "boot iso image, put your desktop, whatever that is named. My desktop is called desktop. And then you do the rest of the settings and bam, now it works !!!
okay I fixed it lol The way you do not get the UEIF thing is, when setting up Kali on the UTM, there is a part that says BOOT ISO IMAGE, it comes out directly after clicking virtualize. When you put browse next to "boot iso image, put your desktop, whatever that is named. My desktop is called desktop. And then you do the rest of the settings and bam, now it works !!!
I didn’t understand can you please explain
I faced the same issue. I have been using Kali Linux for two years on UTM. Then next day, it just shows shell exact as shown in the images. I am trying to figure out why UTM is showing shell instead of start booting up. It is strange because I didn't reconfigure or anything on UTM. I guess I have to delete and reinstall. I would like to know if I am able to reconfigure and get it to boot up instead of starting all over again.
I had the same behavior. After a long search I found the solution. My guess is that you created a VM with the "Virtualize" option in the Startup section and probably saw the following warning with the message: "_The selected boot image contains the word 'arm64' but the guest architecture is 'x8664'. Please make sure you have selected an image that is compatible with 'amd64'.", but ignored it:
... as a result, you have a stopped terminal, as shown above.
I recommend the next steps:
I know this may not work. Therefore, I have another link https://youtu.be/WJt99yl01W0?si=QOIGJ9Z5ly2C9XHR, where you can follow full instructions with downloaded amd64 (not Apple Silicon)
https://www.youtube.com/watch?v=U09soewiu18 See this vdo if you're still having trouble installing kali linux on mac. I'm having Apple m1 and it worked for me but remember set cpu core as 1.
Hey, I tried running Kali Linux Apple Silicon(ARM64) on UTM VM on my Macbook M1 Pro. The process I followed was pretty straightforward. Installed UTM and then installed image installer of Kali Linux in .iso format. After I ran UTM, chose 'Virtualize' -> Other -> selected the relevant boot iso image file -> set the memory at 2047 MB and selected 2 CPU cores -> 34 GB of drive size -> gave Downloads as my shared directory path -> then I double clicked on the VM in the sidebar -> clicked edit -> added a new 'serial' under Devices -> increased the font size to 20 -> saved! Then I tried to run the VM, and as soon as the two windows pops up, both shows a UEFI Interactive Shell v2.2. Now, I tried researching quite a lot on this issue. Sadly, I couldn't able to wrap my head around all the fancy terminologies. There was this one solution, where typing EXIT on the shell will take you to this window where you can try to boot from the file through 'Boot Maintenance Manager'. Did that also, but didn't work. Another solution. which I remember, I tried changing the order of the boot which is shown in 'Boot Manager'. That too didn't work out. Now at last I decided to get help from the GitHub community. I am still an amateur at this, so kindly excuse me. I have attached some screenshots if that could be of any help in any way :)