Error with Ubuntu 20

Confirmed M1/ARM, Same issue with Ubuntu 20.04 LTS ... kernels 5.4.0-90 and 5.4.0-100 are OK, but 5.4.0-104 breaks with EFI_RNG_PROTOCOL
Note that the same EFI_RNG_PROTOCOL message appeared in the previous kernels, but 5.4.0.104 doesn't gracefully continue. Boot switches avoiding EFI fail.
 
Confirmed M1/ARM, Same issue with Ubuntu 20.04 LTS ... kernels 5.4.0-90 and 5.4.0-100 are OK, but 5.4.0-104 breaks with EFI_RNG_PROTOCOL

Both on Ubuntu 20.04.2 Server and Desktop.
 
Hello everyone, we have released a Parallels Desktop hotfix version 17.1.2. The Ubuntu virtual machine boot-up issue got fixed in that. Please visit this KB article to know more.
 
Hello, it is an ongoing issue. The cases have been escalated to developers, and they're researching the ways how to address them. As a temporary workaround please create a new Linux Ubuntu VM from appliance and do not update it. Alternatively, feel free to downgrade the kernel to 5.13.0-25.
I just got the new update for parallels desktop. I am wondering whether it resolves the issue or not. How can I know which release addresses the issue. Thanks
 
I can also confirm that the latest update (Version 17.1.2 build:51548) resolves the issue of stuck on boot with the latest kernel.
 
Hello!
First, thank you a lot for reporting the issue to us.
We've reproduced the issue locally and involved our colleagues from the R & D department to look at the issue and try fixing it.
We'll let you know once we have any updates!
Hi, i still get the same error even after changing the kernel. What am i supposed to do? I am sadly on the verge of canceling my Parallels Desktop subscription.
 
@LeandrinL , thank you for letting us know.

As we can see, there is a recently submitted support ticket where our Tier-1 team has suggested the steps.

We've taken the ticket in the second line in case these steps don't help, and we could take a closer look at the case.

Thanks!
 
Is the problem back?
I tried upgrading to 22.04.1LTS from 20.04LTS and when it boots it says `EFI stub: Exiting boot services` but without the `and installing virtual address nap` part.
This is happening with kernel 5.15.0-46. (The workaround to boot with kernel 5.13.0-40-generic works.)
 
Back
Top