kitkat kernel panic on virtualbox with Intel® Xeon® E5-2699 v3

[Vincent Li]

Hi,
I encountered this kernel panic problem when running kitkat on virtualbox with Intel® Xeon® E5-2699 v3.
The kitkat image was downloaded directly from android x86 official site.

I also noticed the latest kitkat release came with linux kernel 3.18.8.
And lollipop came with kernel 3.10, which was workable on the same virtualbox.
So I tried to build from source with kernel replaced with 3.10 and this time found it worked well on the same virtualbox.

My first thought is that it may be due to a virtualbox bug so I did a search on Google with similar keywords, only to find nothing similar.

Right now the machine is not at hand, therefore I will attach vbox log and kernel log tomorrow.

[Vincent Li]

Hi,

please have a look at the log.
Hope this helps.


Vincent Li於 2015年3月18日星期三 UTC+8下午9時47分28秒寫道：

[pstglia]

Have you tried an older VirtualBox release?

It's a similar behavior like this (https://www.csz-online.net/wordpress/?p=229) 

"

VirtualBox 4.3.8 Linux ‘kernel panic’ Bug

A few days ago Oracle published its virtualization solution VirtualBox in version 4.3.8 and yesterday I also updated my installation to this version. Some really strange problems have occurred after this update: All guest Linux 3.12/3.13 kernel distributions did not boot up anymore because of a kernel panic in a very early stage of booting.

Tested guest OS: Lunar Linux (3.12.5), Fedora 20. Tested host OS: Oracle Solaris 11.1, Windows 7. All 64bit systems.

Here is the kernel panic:

0000000000000000 ffffffff81089458 0000000000000000 0000000000000004
Call Trace:
[] ? uncore_cpu_starting+0x97/0x1e0
[] ? intel_pmu_init+0x8d8/0x8d8
[] ? on_each_cpu+0x28/0x60
[] ? intel_uncore_init+0x282/0x366
[] ? uncore_pmu_register+0xbf/0xbf
[] ? do_one_initcall+0xea/0x130
[] ? parse_args+0x1f2/0x320
[] ? kernel_init_freeable+0x106/0x188
[] ? do_early_param+0x81/0x81
[] ? rest_init+0x80/0x80
[] ? kernel_init+0x5/0x110
[] ? ret_from_fork+0x7c/0xb0
[] ? 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 30 f3 c3 66 66 66 66
2e 0f 1f 84 00 00 00 00 00 31 d2 31 c0
RIP [] 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

The problem is that the kernel tries to write to a MSR, which is not allowed by Oracle VirtualBox. Some more information on this bug can be found here:

• https://www.virtualbox.org/ticket/12748

Solution:

This bug is already fixed by Oracle in the SVN version, which can be self-compiled. Otherwise installing the version 4.3.6 might also fix the problem until the next release version has been published (4.3.10).