I install ubuntu 22.04 for ARM64 on Parallels Desktop 18 for Mac M1, it work pretty well for months, but recently i install a update of parallel tools autmatically pushed then the ubuntu end up with stucking at the booting and the information prints on screen as follows: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... What does it means and what i can do to recover my system from the error above? PS: this annoying problem takes place at least three times on my Parallels, i tried anything could found on internet and end up with reinstalling ubuntu.
I'm getting the same error after upgrading Parallels. Worse: Ubuntu 22.04 now will not let me login. Trying my password prompts the error: "Sorry, password authentication didn't work." This is true despite the fact that certain applications are loading, using that same username/password combination, and are accessible after booting without me logging in.
Had the same issue just now on Parallels Desktop 18 for Mac M1 version 18.3.2 (53621) after a parallels tools update failed to boot into anything even the recovery options didn't work... Forced to re-install. Not great!
Parallels Desktop 18.3.2 Same problem when installing Ubuntu Server 23-10 ARM Unable to boot. Is there a solution? This problem is very annoying.
same on CentOS. Multiple VM's. Went back to a centos version 5.14.0-452.el9.aarch64 using TimeMachine from couple of months ago. Works. But as soon as I upgrade this VM to newer kernel (5.14.0-460 or higher) I'm stuck at same as described above. And they did work before I upgrade to Parallels 20. But after that they 'crashed' (no longer responded, had to force reboot them, and that's where it started).
It seems not to be related to an OS / kernel version. My MacBook (M2 - Sonoma) crashes frequently, and sometimes one of my parelles vm's won't start up again. will stay in state with this "EFI stub: Exiting boot services" displayed as last bit. and that's it. All I can do now is go back a snapshot. But that throws back days of work sometimes And it happens on Rocky 9 as well.
