VirtualBox

Opened 10 years ago

Closed 10 years ago

#12762 closed defect (duplicate)

Linux guest kernel panic, Windows host, VirtualBox 4.3.8 [FIXED in SVN]

Reported by: Rob Brown Owned by:
Component: other Version: VirtualBox 4.3.8
Keywords: Cc:
Guest type: other Host type: other

Description

When booting my Linux VMs I get a kernel panic:

0000000000000000 ffffffff81089458 0000000000000000 0000000000000004
Call Trace:
 [<ffffffff8101b417>] ? uncore_cpu_starting+0x97/0x1e0
 [<ffffffff81780df3>] ? intel_pmu_init+0x8d8/0x8d8
 [<ffffffff81089458>] ? on_each_cpu+0x28/0x60
 [<ffffffff81781355>] ? intel_uncore_init+0x282/0x366
 [<ffffffff817810d3>] ? uncore_pmu_register+0xbf/0xbf
 [<ffffffff810002ea>] ? do_one_initcall+0xea/0x130
 [<ffffffff8105a752>] ? parse_args+0x1f2/0x320
 [<ffffffff8177ae0e>] ? kernel_init_freeable+0x106/0x188
 [<ffffffff8177a7c5>] ? do_early_param+0x81/0x81
 [<ffffffff81529db0>] ? rest_init+0x80/0x80
 [<ffffffff81529db5>] ? kernel_init+0x5/0x110
 [<ffffffff8153543c>] ? ret_from_fork+0x7c/0xb0
 [<ffffffff81529db0>] ? rest_init+0x80/0x80
Code: 01 00 00 31 d2 31 c0 0f 30 c3 66 90 48 8b 87 08 01 00 00 44 8b 88 d0 00 00
 00 45 85 c9 75 0e 31 d2 b8 0f 00 00 20 b9 91 03 00 00 <0f> 30 f3 c3 66 66 66 66
 2e 0f 1f 84 00 00 00 00 00 31 d2 31 c0
RIP [<ffffffff8101acdf>] snb_uncore_msr_init_box+0x1f/0x30
 RSP <ffff8800?d045e10>
———[ end trace eec7c4ed8ee80114 ]———
note: Swapper/0[1] exited with preempt_count 1
Kernel panic — not syncing: attempted to kill init! exitcode=0x0000000b

This happens on both 64-bit and 32-bit VMs, with a variety of 3.12/3.13 kernels. I've tried with and without the extension pack, and also tried changing the chipset from PIIX3 to ICH9.

VirtualBox 4.3.6 works fine, with 4.3.6 or 4.3.8 extensions.

The log file from a 64-bit boot, without the extension pack, is attached. Note that it boots quickly to the kernel panic, and then 55 minutes later I closed the VM.

The extra VDI files that are connected to the VM, are just random data that I have around. I have tried removing the extra VDIs with no effect on the kernel panic. The VMs were closed down before I upgraded from 4.3.6 to 4.3.8.

OSX Mountain Lion also crashes in the kernel if I try to boot it (although it hasn't worked properly for several versions of VirtualBox now, and I'm not worried if it works or not).

Attachments (2)

Gentoo64-2014-03-01-14-56-45.zip (18.8 KB ) - added by Rob Brown 10 years ago.
Log file - kernel panic
VBoxGentoo.txt (95.8 KB ) - added by ManBla 10 years ago.

Download all attachments as: .zip

Change History (4)

by Rob Brown, 10 years ago

Log file - kernel panic

comment:1 by Rob Brown, 10 years ago

The Host is Windows 8.1, 64-bit.

by ManBla, 10 years ago

Attachment: VBoxGentoo.txt added

comment:2 by bird, 10 years ago

Resolution: duplicate
Status: newclosed
Summary: Linux guest kernel panic, Windows host, VirtualBox 4.3.8Linux guest kernel panic, Windows host, VirtualBox 4.3.8 [FIXED in SVN]

Duplicate of #12748.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use