quickemu
quickemu copied to clipboard
quickemu-project
bug: macos sonoma hang during startup
I have installed quickget cloning from github
I downloaded sonoma with quickget with the command quickget macos sonoma see the video https://youtu.be/07JLZCy5zlo
then I installed sonoma with the command quickemu --vm macos-sonoma.conf see the vidoes of the begin of installation end the end start : https://youtu.be/MpbozxjQACw end : https://youtu.be/Z5H0FT6Karo
it seem to me that almost at the end of the installation ( second startup ) the vm rebooted
so probably the installation in not complete ( you can view that in https://youtu.be/Z5H0FT6Karo )
when I try to boot i get a blank screen ( after i have chosen the disk of installation ) and after sometime it restart
see the video
https://youtu.be/MpbozxjQACw
my system is fedora 39
the log is void
what can i check ? P.S: i have tried do install also big-sur monterey ventura with the same result
only the installation of catalina is working ( but is too old for what i have to do )
thank you for any response
It will do that. There's a some stuff about it in the qqX wiki. And a link to walk through for Ventura. Pretty much the same ...
i have read and applied the suggestions of this thread
https://github.com/quickemu-project/quickemu/issues/937
but nothing changed
in this thread you talk about
"The Ventura VM that I had was built using the new, under-development, version."
is this new version already present in quickemu 4.9.3 ( i'm using that ) o is to be released in the future ?
Anyway thanks for your help
Ciao Claudio.
I have two installs of Sonoma already. You need patience to install them but my memory is that they were much the same as with Ventura.
I was running a VM of Fedora 40 last night and tried to install Sonoma on that. It threw up complaints about graphics memory, so I just put that down to it being a VM. You can normally 'telescope' VM's though. ie install machines inside other machines. It's normally not a problem.
I have just tried installing Sonoma, again, a third copy, on my main machine. I use Ubuntu Mate on that one. It didn't work as well as I had expected. Didn't get the graphics memory error though. Something to do with virtio on that one probably.
I am starting to question the Mac distro which is getting downloaded. It doesn't have the 'installer' icon like you can see in the screenshots in #937 and as mentioned in the Quickemu instructions. I initially put this down to an Apple renaming exercise, but I am not sure that this is entirely the case.
I also tried starting Sonoma from the command line, by copying quickemu out of the 'freebird' builtins to the VM folder and using ./quickemu -vm macos-sonoma.conf but got the same results. Note the dot at the front ...
At this point in time, FreeBird is identical to the current Quickemu 'master' and it runs my two previously installed Sonama distros without fault.
@lj3954 did 95% of the work on adding in Sonoma. I am wondering if he might have some ideas?
Ciao Alex , do you think that changing distro ( for example using ubuntu 22.04 ) the installation of mac os vm can work ? i have found this video on you tube https://www.youtube.com/watch?v=wykyreQxVV8 where you can see a succesfull installation of ventura using a linux mint host ( i think based on ubuntu 22.04 ) using https://github.com/kholia/OSX-KVM ( quickemu use OVMF firmware from that project ) i'm guessing to install ubuntu 22.04 on a host and try to create the mac os vm on that system what do you think about ?
Might be worth trying an install of Ventura. See what happens there. Might give us some clues.
I think this is distro. The Ventura front end has changed as well.
This how it used to look:
@lj3954 did 95% of the work on adding in Sonoma. I am wondering if he might have some ideas?
I did very little work inside quickemu. I added sonoma to a couple of switch cases and blocked macOS guests from using some core counts they just won't boot with. Ventura and Sonoma should be identical in nearly every way. Have you been able to install a macOS guest after you modified the CPU argument?
I am starting to question the Mac distro which is getting downloaded.
The image is downloaded in exactly the same way that macrecovery does it, and as far as I can tell, exactly the same way an Apple computer would. Also, the image is verified using a chunklist file which also contains Apple's EFI key. There is no doubt in my mind that the image is legitimate.
I'll check this out tonight. I haven't done much testing with macOS in quickemu since I finished my PR on it.
I'll check this out tonight. I haven't done much testing with macOS in quickemu since I finished my PR on it.
Appreciated :+1:
I can't get the (sonoma) installer to even boot with your new CPU arg, nor can I get my preexisting VM to boot. Ventura kernel panics with it. Whether it works correctly on Intel CPUs or not doesn't matter, silencing a couple of irrelevant errors in the console is not worth whatever regression this has caused.
After reverting the CPU to Haswell, the installation was painless. I just selected the 2nd option "macOS base system" on the first boot, and the 3rd option on reboots. It was quite surprising to me how painless it was.
This doesn't solve the issue, though, since macOS releases prior to Ventura will use the Penryn CPU instead. I'm currently downloading Monterey to test whether this works.
@ctamietto Please provide the output of lscpu. It appears to me that macOS guests work very differently depending on the host's CPU, more data points would be helpful.
I completed the install of macOS Monterey with no changes to the CPU. Once again, there was no issues. Different systems clearly have very different outcomes, much more data is needed to find a solution.
After reverting the CPU to Haswell, the installation was painless
I had wondered whether the Haswell line was actually correct when it added sse_4.2 ?
The original code only grepped for 4.1 and the notes in the code said 4.1.
What happens if you change the new CPU line to 4.2 on your Ryzens?
For me, on Intel, Sonoma runs faultlessly.
I tried to install ventura and sonoma en Debian Trixie. It hang or reboot and go back to the "EFI" and "macOS Base System" menu. I used to have the ventura working on this Debian with the quickemu previous version. I agree to the fact that the installation process is not the same as the startup menu is different.
No dice. That emulated broadwell CPU just doesn't work here
So, I just changed the new CPU instruction to 4.2 and it all works, for me.
And the old one. But it's plain wrong to grep for one thing and to add another.
The question now is how do fix the CPU line so that it works for everyone, Ryzen or Intel.
@lj3954 Try this hybrid line. The old one with Haswell but tidied up.
CPU="-cpu Haswell-noTSX-IBRS,kvm=on,vendor=GenuineIntel,+sse3,+sse4.2,+aes,+xsave,+avx,+xsaveopt,+xsavec,+xgetbv1,+avx2,+bmi2,+smep,+bmi1,+fma,+movbe,+invtsc"
this is the output requested
I have tried again to install big-sur monterey ventura sonoma but nothing works
something is changed , practically all the images hang on first boot ( after selecting the base system )
@ctamietto try qqX 1.8.03 that I have just posted :crossed_fingers:
From the main https://github.com/TuxVinyards/qqX/archive/refs/heads/main.zip
1.8.04
-
The new 2nd May Quickemu code :partying_face:
-
Raft of Quickemu fixes and updates plus a couple of qqX fixes to go with
https://github.com/TuxVinyards/qqX/releases/tag/1.8.04
sorry , i have updated quickemu and qqx but nothing changed I tried to install sonoma but the mouse does not worked so I tried to install Ventura At the second boot after the installation I get a blank screen After about 5 minutes it reboots
very sorry it does not work I think that is related to my hardware
I've tried to install also monterey and hang on first boot and big-sur that hang on second boot
Fixed via #1119
https://github.com/quickemu-project/quickemu/pull/1116#issuecomment-2080411849
This issue is not resolved, that PR solves a separate issue (specifically macOS guests not booting on AMD hosts). Please re-open this.
sorry , i have updated quickemu and qqx but nothing changed I tried to install sonoma but the mouse does not worked so I tried to install Ventura At the second boot after the installation I get a blank screen After about 5 minutes it reboots
very sorry it does not work I think that is related to my hardware
Try this in the .conf file:
mouse="virtio"
keyboard="usb"
This works better with Ventura and Sonoma.
Run the qqX " [tune] " option which will help advise you.
Some people have said that usb_controller="xhci" it works for them . But as this was added to the code a few weeks ago as #981 via #986 I can't see it doing anything. I did try it, to see what it did. For me, it left me completely without mouse and keyboard ....
I've tried to install also monterey and hang on first boot and big-sur that hang on second boot
@ctamietto Can you supply a few more details please.
It is normal for installs to hang for several periods of time when doing the the install. You also may find yourself having to re-boot up to 3 or 4 times too. A bit of patience is needed.
https://github.com/TuxVinyards/qqX/wiki/FAQs-and-Help#macos-hangs-when-running-the-setup
Fixed via #1119
This issue is not resolved, that PR solves a separate issue (specifically macOS guests not booting on AMD hosts). Please re-open this.
@lj3954 these changes were put out for testing for several days before merging. No one found any problems.
You tested these PR's on your Ryzens didn't you? I seem to remember you have an older Ryzen notebook amongst your computer collection as well ...
I would like to see the Quickemu conf generator doing a bit of tuning to the mouse and keyboard. There's room for improvement in that area.
i've tried to install sonoma again adding manually
mouse="virtio" keyboard="usb"
to the conf file
then i've tried also qqx tune
so I get this config file
#!/usr/bin/qqX --vm
disk_size="128G" cpu_cores="22" ram="10G"
guest_os="macos" disk_img="macos-sonoma/disk.qcow2" img="macos-sonoma/RecoveryImage.img" macos_release="sonoma" mouse="virtio" keyboard="usb"
but nothing changed , the mouse does not work
I've uploaded to you tube a short video to show what I have done
https://youtu.be/pUuZsgVnl94
I've tried also usb_controller="xhci" but nothing changed
@ctamietto This isn't your .conf. Your video shows you going to dvd player type icons. This is a problem with the CPU line.
There are a few ways to solve this but the recent changes have no major factor that I can see. You are booting off exactly the same formula that was used before. The only change is adding is here. -cpu Haswell-noTSX-IBRS with the addition of -noTSX-IBRS.
Hopefully I can ask you for a little more patience and to try a few things. There are several ways to try to solve this and one of these should work.
Your lscpu output shows you are using an Intel CPU. An i7 1280P.
We can try changing the CPU line to plain -cpu Haswell Take off the noTSX This will probably generate warning errors but at least we will have eliminated this as a factor.
The other thing is to use -cpu host which will mean using all the features that your CPU can offer.
You have tested your set up working with Linux VM's at this point, so this should be okay.
We need to edit the quickemu file, where it says -cpu Haswell-noTSX-IBRS. You can edit this in the qqX downloads folder. Use the current "FreeSpirit" folder, which is currently the same as "FreeBird". Then either run the qqX installer to do a re-install followed by selecting "FreeSpirit" from the settings. Or copy the folder and make a Custom set-up. Instructions for that are at the end of the settings folder. It's easier than it sounds ...
Have a zoom in look at this screenshot which shows Sonoma working on my series 11 intel using the -cpu host formula which I simply copied over from a bit further down, where the Windows CPU line is.
If neither of these two work, return back to the old formula and retry but removing and replacing the instruction set lines, one by one, to see which instruction is causing the problem. Comparing the CPU instruction against your lscpu flags output will shorten this task.
You could also try copying the Penryn formula, the one with *) For that you will need to add in +avx2 and to change the +sse4.1 to +sse4.2.