VirtualBox

Opened 4 years ago

Last modified 4 years ago

#19089 new defect

Kernel Panic when running Ubuntu 18.04.03 inside VirtualBox 6.0.14 on macOS 10.14.6 host

Reported by: Lars Sonchocky-Helldorf Owned by:
Component: other Version: VirtualBox 6.0.14
Keywords: Cc:
Guest type: Linux Host type: Mac OS X

Description

While the installation of Ubuntu 18.04.03 went fine, a subsequent boot of this VM resulted in a kernel panic. See attached files.

Attachments (7)

kernel-panic-crash-log.txt.zip (325.2 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
Zipped crash log of the kernel panic
Logs.zip (39.6 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
Zipped Vbox Logs of the affected VM
crash log.1.txt.zip (22.3 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
crash log of the crashed VM
crash log.2.txt.zip (23.3 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
crash log of the crashed VM
Logs.2.zip (58.8 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
VBox Logs of the crashed VM
Logs.3.zip (77.9 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
VBox Logs of the crashed VM
kernel-panic-crash-log.2.txt.zip (274.2 KB ) - added by Lars Sonchocky-Helldorf 4 years ago.
Kernel Panic Crash Log when running ReactOS VM

Download all attachments as: .zip

Change History (16)

by Lars Sonchocky-Helldorf, 4 years ago

Zipped crash log of the kernel panic

by Lars Sonchocky-Helldorf, 4 years ago

Attachment: Logs.zip added

Zipped Vbox Logs of the affected VM

comment:1 by Lars Sonchocky-Helldorf, 4 years ago

If this wasn't clear: the host panicked, not the guest!

comment:2 by Lars Sonchocky-Helldorf, 4 years ago

kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  123    3 0xffffff7f83eb3000 0xf0000    0xf0000    org.virtualbox.kext.VBoxDrv (6.0.14) 53BAF3B2-AB27-321B-9DF8-7A1395C58923 <8 6 5 3 1>
  124    0 0xffffff7f83fa3000 0x28000    0x28000    com.intel.kext.intelhaxm (7.3.2) 58DFBE80-E54A-3EFE-B38A-215C5ED8E828 <8 6 5 3 1>
  170    0 0xffffff7f847a6000 0x4000     0x4000     com.intel.driver.EnergyDriver (2.0) 8937025C-61CA-370A-A1D1-553F373E68C7 <8 6 5 3>
  183    0 0xffffff7f84912000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (6.0.14) CE24428E-4F6D-3690-89CC-1575AA093D8D <182 123 54 8 6 5 3 1>
  188    0 0xffffff7f84949000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (6.0.14) 895E2094-4B8F-349F-8951-BF361447E6C5 <123 8 6 5 3 1>
  199    0 0xffffff7f85aec000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (6.0.14) 38B6099A-ED14-3D29-87D4-DF1A3E4168CF <123 6 5 1>

comment:3 by Lars Sonchocky-Helldorf, 4 years ago

removed the intelhaxm kext, now I am getting just crashes of that VM. See attached files.

by Lars Sonchocky-Helldorf, 4 years ago

Attachment: crash log.1.txt.zip added

crash log of the crashed VM

by Lars Sonchocky-Helldorf, 4 years ago

Attachment: crash log.2.txt.zip added

crash log of the crashed VM

by Lars Sonchocky-Helldorf, 4 years ago

Attachment: Logs.2.zip added

VBox Logs of the crashed VM

by Lars Sonchocky-Helldorf, 4 years ago

Attachment: Logs.3.zip added

VBox Logs of the crashed VM

comment:5 by Lars Sonchocky-Helldorf, 4 years ago

  • Installed Android Studio 3.5.2 which in turn installed HAXM 7.5.1: no kernel panics so far
  • Still getting above crashes of the VM when inserting or removing the Guest Additions CD image

comment:6 by Lars Sonchocky-Helldorf, 4 years ago

Got a single, not reproducible kernel panic with Intel HAXM 7.5.1. installed when trying to run a ReactOS 0.4.11 VM. See attached file.

by Lars Sonchocky-Helldorf, 4 years ago

Kernel Panic Crash Log when running ReactOS VM

comment:8 by Socratis, 4 years ago

Replying to comment 5 by IOOI:

which in turn installed HAXM 7.5.1

I believe I mentioned that 7.5.4 is the current HAXM release, not 7.5.1, can you try with that?


Replying to comment 7 by IOOI:

see also https://issuetracker.google.com/issues/144584550

I can't. It wants me to login to Google. What's the summary?

Last edited 4 years ago by Socratis (previous) (diff)

in reply to:  8 comment:9 by Lars Sonchocky-Helldorf, 4 years ago

Replying to socratis:

Replying to comment 5 by IOOI:

which in turn installed HAXM 7.5.1

I believe I mentioned that 7.5.4 is the current HAXM release, not 7.5.1, can you try with that?

I don't mess with what Android Studio installs. I need this for production, whereas I need VBox only for occasional tests.


Replying to comment 7 by IOOI:

see also https://issuetracker.google.com/issues/144584550

I can't. It wants me to login to Google. What's the summary?

The summary is:

"Intel HAXM v 7.5.1 kext installed by Android Studio 3.5.2 causes Kernel Panics on macOS 10.14.6 when running VirtualBox Reviewed (L1)"

and my report says:

"IOOI SqAR <lars.sonchocky.helldorf@…> #1 Nov 17, 2019 11:47AM

Created issue. IMPORTANT: Please read https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Studio Build: Android Studio 3.5.2 Build #AI-191.8026.42.35.5977832, built on October 30, 2019 JRE: 1.8.0_202-release-1483-b49-5587405 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.14.6

Version of Gradle Plugin: Version of Gradle: Version of Java: JRE: 1.8.0_202-release-1483-b49-5587405 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o OS: macOS 10.14.6

Steps to Reproduce: All those Java and Gradle configs are irrelevant for this bug, the Intel HAXM kext installed by Android Studio causes Kernel Panics on macOS 10.14.6 when running VirtualBox. Here are my non Apple kexts:

kextstat | grep -v com.apple Index Refs Address Size Wired Name (Version) UUID <Linked Against>

124 3 0xffffff7f83eb3000 0xf0000 0xf0000 org.virtualbox.kext.VBoxDrv (6.0.14) 53BAF3B2-AB27-321B-9DF8-7A1395C58923 <8 6 5 3 1> 125 0 0xffffff7f83fa3000 0x29000 0x29000 com.intel.kext.intelhaxm (7.5.1) D0CC7B8F-1F62-33B1-BE6B-B5573D2A607B <8 6 5 3 1> 165 0 0xffffff7f846e9000 0x4000 0x4000 com.intel.driver.EnergyDriver (2.0) 8937025C-61CA-370A-A1D1-553F373E68C7 <8 6 5 3> 185 0 0xffffff7f84918000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (6.0.14) CE24428E-4F6D-3690-89CC-1575AA093D8D <184 124 54 8 6 5 3 1> 190 0 0xffffff7f84950000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (6.0.14) 895E2094-4B8F-349F-8951-BF361447E6C5 <124 8 6 5 3 1> 194 0 0xffffff7f84a24000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (6.0.14) 38B6099A-ED14-3D29-87D4-DF1A3E4168CF <124 6 5 1>

the one of interest here is com.intel.kext.intelhaxm (7.5.1). According to https://forums.virtualbox.org/viewtopic.php?f=8&t=95616&p=463219#p463219 the old version of Intel HAXM is the cause.

Please update the installed Intel HAXM to version 7.5.4 https://github.com/intel/haxm/releases"

their response so far:

"Assigned to lf...@…. Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue."

btw. I don't get why you don't want to login to Google, when you seem to have no problems to login to Oracle. If the later was any better than the former …

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use