Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

Bug #1928601 reported by Reijo Korhonen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When upgrading virtual machine from Ubuntu 18.04 to 20.04 it fails to boot with kernel panic to run 5-series kernel, which is default in 20.04, but can run 4-series kernel, which comes with Ubuntu 18.04. Tested with Microsoft's Hyper-V and Ubuntu's libvirt qemu. Results are identical.

More information https://askubuntu.com/questions/1338236/ubuntu-fails-to-start-by-default-after-upgrade-18-04-to-20-04/1338722#1338722

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1928601/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Reijo Korhonen (reijokor) wrote :

I think upgrade to 20.04 comes with linux-image-5.4.0-26-generic, but bug comes when latest kernel package from Ubuntu official repocity.

affects: ubuntu → linux
affects: linux → ubuntu-release-upgrader (Ubuntu)
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1928601

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: bionic
Revision history for this message
Reijo Korhonen (reijokor) wrote :

When virtual machine's kernel panics in the boot, it not possiblr run apport-collect 1928601 any more, I'm afraid.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Reijo Korhonen (reijokor) wrote :

I can run 'apport-collect 1928601' in the virtual machine, if I boot using series-4 kernel, but does it give any information why series-5 kernel panics? Please tell if helps, if I run apport-collect 1928601' in series-4 kernel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.