Hello everyone, Lets get this problem solved.
Now, doing a major version update to virtualbox in Jammy from 6.1.50-dfsg-1~ubuntu1.20.04.1 to 7.0.20 is against Ubuntu SRU policy, and would also come with the consequence that it would break all existing VMs that use guest additions, as guest additions would have to be removed from VMs, virtualbox upgraded, and then guest additions installed again. So no, doing a major upgrade to virtualbox is the wrong approach. We have two options: 1) Locate the change in the kernel, then either revert it, or find a fix for it. 2) Locate the fix in virtualbox 7.0.20 and backport if possible to 6.1.50. For the moment, let's just investigate 1). I read AaronMa's comment with the upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=219107 Now, only the first commit got backported to the jammy 5.15 kernel: commit 507882a9d37affee0903c0ebb3d1544f4bfba024 ubuntu-jammy Author: Kees Cook <keesc...@chromium.org> Date: Sat Mar 9 12:24:48 2024 -0800 Subject: randomize_kstack: Improve entropy diffusion Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=507882a9d37affee0903c0ebb3d1544f4bfba024 This landed in: $ git describe --contains 507882a9d37affee0903c0ebb3d1544f4bfba024 Ubuntu-5.15.0-115.125~210 which is when we started seeing the issues. I have reverted this commit, and built test kernels for the more technically inclined people to try: https://launchpad.net/~mruffell/+archive/ubuntu/lp2073267-test I just uploaded them. Please wait three hours from this message for them to have finished building. There are both focal HWE and jammy kernels in this ppa. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. Instructions to Install (On a focal or jammy system): 1) sudo add-apt-repository ppa:mruffell/lp2073267-test 2) sudo apt update 3) sudo apt install linux-image-unsigned-5.15.0-117-generic linux-modules-5.15.0-117-generic linux-modules-extra-5.15.0-117-generic linux-headers-5.15.0-117-generic 4) sudo reboot 5) uname -rv Look for +TEST2073267v20240731b1 If you are asked to abort removal of the currently running kernel, say no. Does it fix virtualbox 6.1.50? Please let me know. In the meantime, I will try and look through the virtualbox subversion repository to find where virtualbox fixed this to see if backporting a fix for virtualbox would be a better route to take. https://www.virtualbox.org/browser/vbox/trunk Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073267 Title: Virtualbox Guru meditation on VM start caused by kernel commit in v6.9-rc4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
