** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780817
Title:
kernel panic in nested VM with latest 4.15 kernel (4.15.0-24-generic)
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780817
Title:
kernel panic in nested VM with latest 4.15 kernel
Tested with v4.19-rc4 mainline build, and the bug still exists.
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
I can confirm this, the issue showed up in 4.14. I have tried a number
kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/, and found
that somewhere between 4.13.16 and 4.14.0 this bug introduced itself.
I am running a fresh install of Bionic, not an upgrade.
--
You received this bug
those image also related to xenial.
apt-cache policy linux-image-virtual-hwe-16.04
linux-image-virtual-hwe-16.04:
Installed: 4.15.0.33.55
Candidate: 4.15.0.33.55
Version table:
*** 4.15.0.33.55 500
500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
