Skip to content

[Bug]: VirtualBox 7.2.0 gives guru meditation immediately after launching freshly imported OVA #139

New issue
New issue
Closed
Closed
[Bug]: VirtualBox 7.2.0 gives guru meditation immediately after launching freshly imported OVA#139
Assignees
ramshven
Labels
bugSomething isn't workingfixed in svnCommit made to SVN repo. Will be on GitHub on next SVN sync. Issue/PR staged for close.

Description

@gebailey
gebailey
opened on Aug 15, 2025

Version

7.2.0

Host OS Type

Linux

Host OS name + version

AlmaLinux 9.6

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version

AlmaLinux 9.6 (yes, same as host)

Component

Other

What happened?

I have several OVA exports I keep on hand of various Fedora, CentOS, and AlmaLinux virtual machines. I've used these successfully with various VirtualBox 7.1 host versions (on both Linux and Windows hosts).

Immediately after powering the VM on, I received a guru meditation error.

VBox.log

How can we reproduce this?

I'm hoping it's clear from the logs I'll upload. I can try to produce a smaller/minimal OVA file if that's helpful but the one I have is ~2 GB in size.

Did you upload all of your necessary log files, screenshots, etc.?

  • Yes, I've uploaded all pertinent files to this issue.

Activity

  1. gebailey
    added
    bugSomething isn't working
    on Aug 15, 2025

  2. gebailey commented on Aug 15, 2025

    @gebailey
    gebailey
    on Aug 15, 2025
    Author

    Looks related to #141

    If I remove the kvm_intel and kvm modules, I am then able to launch virtual machines.

  3. AlexanderEichner
    marked [Bug]: VMs fail to start with critical error on Linux hosts with Kernel 6.12+ due to KVM module conflict #141 as a duplicate of this issue on Aug 18, 2025

  4. AlexanderEichner commented on Aug 18, 2025

    @AlexanderEichner
    AlexanderEichner
    on Aug 18, 2025

    Ultimately some kind of duplicate of issue #81 but the guru meditation shouldn't happen but a descriptive error should be shown, keeping it open.

  5. ramshven commented on Aug 18, 2025

    @ramshven
    ramshven
    on Aug 18, 2025
    Contributor

    I thought this should have been fixed with r159383 (db70034). At least smells like it... Will need to revisit if the fix isn't complete (or somehow only worked on Intel host).

  6. ramshven
    self-assigned this
    on Aug 20, 2025

  7. ramshven commented on Aug 26, 2025

    @ramshven
    ramshven
    on Aug 26, 2025
    Contributor

    This is fixed in SVN (i.e. more descriptive error rather than a guru meditation) and should be available in the next 7.2.x maintenance release.

  8. ramshven
    added
    fixed in svnCommit made to SVN repo. Will be on GitHub on next SVN sync. Issue/PR staged for close.
    on Aug 26, 2025
  9. ramshven
    closed this as completedon Aug 26, 2025
  10. ramshven
    marked [Bug]: Linux host Windows 11 guest stop working properly after Vbox 7.2.0 (kernel 6.16.1) #163 as a duplicate of this issue on Aug 26, 2025
  11. ramshven
    unmarked [Bug]: Linux host Windows 11 guest stop working properly after Vbox 7.2.0 (kernel 6.16.1) #163 as a duplicate of this issue on Aug 26, 2025

  12. galitsyn-oracle commented on Sep 11, 2025

    @galitsyn-oracle
    galitsyn-oracle
    on Sep 11, 2025
    Contributor

    Hello,

    Thank you for reporting the issue. We just released VirtualBox 7.2.2. This issue should be fixed in this version. Could please give it a try? Packages are available at https://www.virtualbox.org/wiki/Downloads.

  13. galitsyn-oracle
    reopened this on Sep 11, 2025

  14. gebailey commented on Sep 11, 2025

    @gebailey
    gebailey
    on Sep 11, 2025
    Author

    Tested in version 7.2.2. I now get a more descriptive error saying that the KVM module is in use. Thank you for the fix!

  15. galitsyn-oracle
    closed this as completedon Sep 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingfixed in svnCommit made to SVN repo. Will be on GitHub on next SVN sync. Issue/PR staged for close.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions