Kernel Crash when running on nested environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
When running an Ubuntu 17.10 or 18.04 VM and then running a Kata-Container (which creates a new VM), sometimes I get a kernel Panic in the First VM launched.
I don't know what is the Host distro, since this is a cloud environment.
Using this script, it is easily reproducible:
https:/
This is the kernel panic got from Ubuntu 17.10:
[ 7893.642642] general protection fault: 0000 [#1] SMP PTI
[ 7893.644919] Modules linked in: vhost_net vhost macvtap macvlan tap veth kvm_intel kvm irqbypass ipt_MASQUERADE nf_nat_
[ 7893.666649] [last unloaded: irqbypass]
[ 7893.667910] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-45-generic #50-Ubuntu
[ 7893.670283] Hardware name: RDO OpenStack Compute, BIOS 1.11.0-2.el7 04/01/2014
[ 7893.672483] task: ffffffffb0412480 task.stack: ffffffffb0400000
[ 7893.674218] RIP: 0010:native_
[ 7893.675549] RSP: 0018:ffff8b08bf
[ 7893.677138] RAX: 00000000000626f0 RBX: 0000000000000000 RCX: ffff8b08bfc23cd0
[ 7893.679254] RDX: ffff8b08bfc14020 RSI: ffff8b08bfc23cd0 RDI: 00000000000606f0
[ 7893.681478] RBP: ffff8b08bfc03f50 R08: 00000a6d223ad8ee R09: ffff8b08ac931800
[ 7893.683695] R10: 00000001001cf7c1 R11: 0000000000000061 R12: 0000000000023cd0
[ 7893.685895] R13: 0000000000000001 R14: ffff8b08bff4a800 R15: 000000000008a000
[ 7893.688171] FS: 000000000000000
[ 7893.690855] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 7893.692658] CR2: 00007fb2f8fdc020 CR3: 000000035b80a003 CR4: 00000000000626f0
[ 7893.694909] Call Trace:
[ 7893.695837] <IRQ>
[ 7893.696664] hardware_
[ 7893.698380] kvm_arch_
[ 7893.700043] hardware_
[ 7893.701712] flush_smp_
[ 7893.703335] generic_
[ 7893.705321] smp_call_
[ 7893.706883] call_function_
[ 7893.708529] </IRQ>
[ 7893.709361] RIP: 0010:native_
[ 7893.710878] RSP: 0018:ffffffffb0
[ 7893.713311] RAX: ffffffffafb1be10 RBX: ffffffffb0660720 RCX: 0000000000000000
[ 7893.715635] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 7893.717890] RBP: ffffffffb0403df8 R08: 0000000000000002 R09: ffff8b08ac931800
[ 7893.720044] R10: 00000001001cf7c1 R11: 0000000000000061 R12: 0000000000000000
[ 7893.722234] R13: 0000000000000000 R14: ffff8b08bff4a800 R15: 000000000008a000
[ 7893.724426] ? __cpuidle_
[ 7893.725828] default_
[ 7893.727209] arch_cpu_
[ 7893.728450] default_
[ 7893.729613] do_idle+0x16f/0x1e0
[ 7893.730643] cpu_startup_
[ 7893.731825] rest_init+0xbc/0xc0
[ 7893.732840] start_kernel+
[ 7893.733974] ? early_idt_
[ 7893.735306] x86_64_
[ 7893.736607] x86_64_
[ 7893.737887] secondary_
[ 7893.739139] Code: 0f 1f 80 00 00 00 00 55 48 89 e5 0f 20 d8 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 0f 22 df 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 <0f> 22 e7 5d c3 0f 1f 80 00 00 00 00 55 48 89 e5 44 0f 20 c0 5d
[ 7893.744104] RIP: native_
[ 7893.745775] ---[ end trace fccf997ea9a59d36 ]---
[ 7893.747097] Kernel panic - not syncing: Fatal exception in interrupt
[ 7893.749271] Kernel Offset: 0x2e200000 from 0xffffffff81000000 (relocation range: 0xffffffff80000
[ 7893.752179] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1784393
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.