Results 1 to 10 of 10

Thread: VirtualBox crash (guru meditation) with new kernel 5.13.0

  1. #1

    Default VirtualBox crash (guru meditation) with new kernel 5.13.0

    Hi,

    in a previous post I was able to run kernel 5.12.13 with VirtualBox 6.1.22 almost fine (everything worked except for one app that refuses to start only on this laptop). The repository updated the kernel to 5.13.0 and now VirtualBox will not start, it crashes on startup.

    I made a big mistake yesterday and reinstalled the system as I want to have secure boot enabled (it was off before) and now I can't find kernel 5.12.13 anywhere. Does anyone know where I might find it as a repository?

    Thank you!

  2. #2
    Join Date
    Jul 2018
    Location
    Loma Linda, Mo
    Posts
    618

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Works fine when secure boot is disabled in the BIOS. Signing is not right with VirtualBox.
    OpenSUSE 15.3 with VirtualBox VM's (XP, 10, 11, Ubuntu MATE 20.04, OpenSUSE 15.3, Tumbleweed)
    Pi4 with OpenSUSE 15.3
    Unix since 1974 (pdp-11, Interdata, AT&T, Tandy, Convergent, Sun, IBM, NCR, and HP)
    Linux since 1995 (Mandrake, Fedora, CentOS, OpenSUSE)

  3. #3
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,395

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Quote Originally Posted by ReverantGR View Post
    I want to have secure boot enabled (it was off before)
    Yes, there's an issue with the UEFI MOKs with Leap 15.3 – I'm also have to turn off Secure Boot on this old Lenovo G505s laptop – the openSUSE certificates refuse to enroll into the EFI environment and therefore the Virtual Box kernel driver refuses to load if Secure Boot is enabled …
    • Maybe I'll raise a Bug Report but, not today …

  4. #4

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Quote Originally Posted by larryr View Post
    Works fine when secure boot is disabled in the BIOS. Signing is not right with VirtualBox.
    Unfortunately not. I still get a crash with Secure Boot disabled. In fact, in another thread, I had accidentally used the development repository of the kernel and installed a RC version of the 5.13.0 kernel and I would get the crash, with secure boot disabled. Reverting to the release kernel (5.12.x) would allow VirtualBox to run fine.

  5. #5
    Join Date
    Jul 2018
    Location
    Loma Linda, Mo
    Posts
    618

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    What VirtualBox did you install - mine is from the system packages - not from the Oracle VirtualBox downloads.

    I'll show you what my system looks like with VirtualBox running in 15.3.

    What does zypper show where you installed?

    Code:
    LLR1:~ # zypper se -si virtual
    Loading repository data...
    Reading installed packages...
    
    S  | Name                   | Type    | Version                       | Arch   | Repository
    ---+------------------------+---------+-------------------------------+--------+------------------
    i+ | virtualbox             | package | 6.1.22-602.1                  | x86_64 | (System Packages)
    i  | virtualbox-kmp-default | package | 6.1.22_k5.3.18_57-lp153.600.1 | x86_64 | (System Packages)
    i  | virtualbox-qt          | package | 6.1.22-602.1                  | x86_64 | (System Packages)
    LLR1:~ # uname -a
    Linux LLR1 5.3.18-59.10-default #1 SMP Fri Jun 25 12:36:56 UTC 2021 (6856d31) x86_64 x86_64 x86_64 GNU/Linux
    LLR1:~ # ps -ef | grep virtualbox
    llrainey  6888     1  0 Jun29 ?        00:09:09 /usr/lib/virtualbox/VBoxXPCOMIPCD
    llrainey  6894     1  0 Jun29 ?        00:25:17 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
    llrainey  6916  6866  0 Jun29 ?        00:03:26 /usr/lib/virtualbox/VirtualBox6
    llrainey 26358  6894 12 Jun30 ?        03:56:47 /usr/lib/virtualbox/VirtualBoxVM --comment VM7 --startvm 5116931e-7a5f-4a2f-b9ad-fa585a18826c --no-startvm-errormsgbox
    llrainey 26431  6894  7 Jun30 ?        02:25:48 /usr/lib/virtualbox/VirtualBoxVM --comment VM8 --startvm 4c211192-83b6-4387-a7e2-a387dd9d3f2d --no-startvm-errormsgbox
    llrainey 26594  6894  6 Jun30 ?        02:14:03 /usr/lib/virtualbox/VirtualBoxVM --comment VM11 --startvm 84bfc7c8-ca88-4bec-b6b7-cd17cb5deeea --no-startvm-errormsgbox
    llrainey 26701  6894 10 Jun30 ?        03:15:25 /usr/lib/virtualbox/VirtualBoxVM --comment VM2 --startvm eadecd16-7156-46b4-8d63-9634910a7d94 --no-startvm-errormsgbox
    llrainey 26780  6894 41 Jun30 ?        13:17:07 /usr/lib/virtualbox/VirtualBoxVM --comment VM1 --startvm e0e0dcb9-5839-4cb2-9c54-c778ae141076 --no-startvm-errormsgbox
    root     28956 28288  0 17:40 pts/15   00:00:00 grep --color=auto virtualbox
    LLR1:~ #
    OpenSUSE 15.3 with VirtualBox VM's (XP, 10, 11, Ubuntu MATE 20.04, OpenSUSE 15.3, Tumbleweed)
    Pi4 with OpenSUSE 15.3
    Unix since 1974 (pdp-11, Interdata, AT&T, Tandy, Convergent, Sun, IBM, NCR, and HP)
    Linux since 1995 (Mandrake, Fedora, CentOS, OpenSUSE)

  6. #6

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    It would appear that VirtualBox 6.1.22 is incompatible with the 5.13 kernel - please see this thread: https://forums.opensuse.org/showthread.php/556642-Virtualbox-stopped-working-after-a-windows-update?highlight=virtualbox
    I am having the same issue, only on Tumbleweed. Our best hope would seem to be to wait for the next VBox version. A thing like this can hardly stay unfixed for long.

  7. #7

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Workaround:
    I found this on the VirtualBox Bug Tracker: https://www.virtualbox.org/ticket/20452
    So I added
    Code:
    randomize_kstack_offset=off
    to my kernel boot parameters, and my VMs are now back in working order.

    This fix obviously disables some new feature in the kernel, which could lead to other disadvantages - so I suppose I should try removing it when a new VBox version becomes available, to see if I still need it.

  8. #8
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,395

    Question Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Quote Originally Posted by ReverantGR View Post
    in a previous post I was able to run kernel 5.12.13 with VirtualBox 6.1.22 almost fine (everything worked except for one app that refuses to start only on this laptop). The repository updated the kernel to 5.13.0 and now VirtualBox will not start, it crashes on startup.
    Wait a minute, the default Kernel used by Leap 15.3 is the Linux Kernel version 5.3 – backported from Linux Kernel version 5.9.
    • Are you using a Linux Kernel which is not the standard Leap 15.3 Kernel?

  9. #9
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,470

    Default AW: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Are you using a Linux Kernel which is not the standard Leap 15.3 Kernel?
    I think so......

    See the headline of this thread and the first post.
    Never talked about kernel 5.3.
    And the solution (if it is one) by adding randomize_kstack_offset=off to grub does also work here (kernel:stable:backport).

    So I think the kernel:stable or similar Repo is enabled.

    So post:
    Code:
    zypper lr -d

  10. #10
    Join Date
    Jan 2016
    Location
    UK
    Posts
    768

    Default Re: VirtualBox crash (guru meditation) with new kernel 5.13.0

    Quote Originally Posted by JGoll View Post
    Workaround:
    I found this on the VirtualBox Bug Tracker: https://www.virtualbox.org/ticket/20452
    So I added
    Code:
    randomize_kstack_offset=off
    to my kernel boot parameters, and my VMs are now back in working order.

    This fix obviously disables some new feature in the kernel, which could lead to other disadvantages - so I suppose I should try removing it when a new VBox version becomes available, to see if I still need it.
    I can confirm that this worked for me as well. I will remove it when a new virtualbox arrives.

    Stuart

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •