Kernel oops when starting a QEMU/KVM virtual machines

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Kernel oops when starting a QEMU/KVM virtual machines

Giuseppe Gorgoglione
After upgrading my Tumbleweed box to snapshot 20171120, the first one
with kernel 4.14, I get oops every time I try to start QEMU/KVM
virtual machines. More details here:
https://bugzilla.suse.com/show_bug.cgi?id=1069562

Anybody experiencing the same?

Kind regards,
Giuseppe.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel oops when starting a QEMU/KVM virtual machines

Roger Whittaker-2
On Thu, Nov 23, 2017 at 11:05:21AM +0100, Giuseppe Gorgoglione wrote:

> After upgrading my Tumbleweed box to snapshot 20171120, the first one
> with kernel 4.14, I get oops every time I try to start QEMU/KVM
> virtual machines. More details here:
> https://bugzilla.suse.com/show_bug.cgi?id=1069562
>
> Anybody experiencing the same?

Yes - I've seen this as well.

But I think it's related to

https://lists.opensuse.org/opensuse-factory/2017-11/msg00572.html

Try with apparmor disabled and see if it makes a difference: it did
for me.

So it should soon be fixed if I understood correctly.

 
--
============================
Roger Whittaker
[hidden email]
============================
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel oops when starting a QEMU/KVM virtual machines

Jiri Slaby-6
On 11/23/2017, 11:15 AM, Roger Whittaker wrote:

> On Thu, Nov 23, 2017 at 11:05:21AM +0100, Giuseppe Gorgoglione wrote:
>
>> After upgrading my Tumbleweed box to snapshot 20171120, the first one
>> with kernel 4.14, I get oops every time I try to start QEMU/KVM
>> virtual machines. More details here:
>> https://bugzilla.suse.com/show_bug.cgi?id=1069562
>>
>> Anybody experiencing the same?
>
> Yes - I've seen this as well.
>
> But I think it's related to
>
> https://lists.opensuse.org/opensuse-factory/2017-11/msg00572.html

The kernel shall not crash no matter what profile you provide.

So if the patch helps, note that in the bug.

thanks,
--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel oops when starting a QEMU/KVM virtual machines

Roger Whittaker-2
On Thu, Nov 23, 2017 at 02:31:52PM +0100, Jiri Slaby wrote:

> The kernel shall not crash no matter what profile you provide.

It's not a crash - it's this (as soon as I do "virsh list" for instance):

2017-11-23T14:01:58.172651+00:00 jabberwock kernel: [  131.303644] BUG: unable to handle kernel paging request at fffffffe29672320
2017-11-23T14:01:58.172669+00:00 jabberwock kernel: [  131.303656] IP: audit_signal_cb+0x6c/0xe0
2017-11-23T14:01:58.172671+00:00 jabberwock kernel: [  131.303658] PGD 1d3c0c067 P4D 1d3c0c067 PUD 0
2017-11-23T14:01:58.172673+00:00 jabberwock kernel: [  131.303662] Oops: 0000 [#1] PREEMPT SMP
2017-11-23T14:01:58.172683+00:00 jabberwock kernel: [  131.303664] Modules linked in: fuse ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables devlink af_packet bridge stp llc iscsi_ibft iscsi_boot_sysfs msr joydev ftdi_sio usbserial snd_hda_codec_hdmi hid_generic usbhid snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 nls_cp437 wmi_bmof vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uas kvm irqbypass crct10dif_pclmul usb_storage crc32_pclmul intel_spi_platform intel_spi spi_nor ghash_clmulni_intel mtd iTCO_wdt iTCO_vendor_support pcbc ir_rc6_decoder aesni_intel aes_x86_64 crypto_simd glue_helper cryptd rc_rc6_mce pcspkr snd_soc_rt5640 snd_soc_rl6231 snd_soc_core snd_hda_intel tpm_tis ir_lirc_codec snd_hda_codec snd_compress tpm_tis_core lirc_dev snd_pcm_dmaengine snd_hda_core tpm
2017-11-23T14:01:58.172687+00:00 jabberwock kernel: [  131.303709]  snd_hwdep nuvoton_cir battery snd_pcm rc_core elan_i2c snd_timer snd_soc_sst_acpi snd_soc_sst_match gpio_lynxpoint dw_dmac fan spi_pxa2xx_platform thermal i2c_i801 wmi snd e1000e ptp mei_me soundcore mei lpc_ich pps_core btrfs xor zstd_decompress zstd_compress xxhash raid6_pq crc32c_intel i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ehci_pci ehci_hcd usbcore drm sdhci_acpi sdhci video mmc_core i2c_hid button sg nbd dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua ecryptfs efivarfs
2017-11-23T14:01:58.172689+00:00 jabberwock kernel: [  131.303745] CPU: 3 PID: 2931 Comm: libvirtd Not tainted 4.14.0-1-default #1
2017-11-23T14:01:58.172690+00:00 jabberwock kernel: [  131.303747] Hardware name:                  /D54250WYK, BIOS WYLPT10H.86A.0045.2017.0302.2108 03/02/2017
2017-11-23T14:01:58.172693+00:00 jabberwock kernel: [  131.303750] task: ffffa08e99958080 task.stack: ffffb4bcc3e80000
2017-11-23T14:01:58.172694+00:00 jabberwock kernel: [  131.303753] RIP: 0010:audit_signal_cb+0x6c/0xe0
2017-11-23T14:01:58.172696+00:00 jabberwock kernel: [  131.303755] RSP: 0018:ffffb4bcc3e83c08 EFLAGS: 00010292
2017-11-23T14:01:58.172697+00:00 jabberwock kernel: [  131.303758] RAX: ffffb4bcc3e83d68 RBX: ffffa08ef3638ac8 RCX: 0000000000000000
2017-11-23T14:01:58.172699+00:00 jabberwock kernel: [  131.303760] RDX: ffffffffcfdc3a90 RSI: 0000000000000006 RDI: ffffa08e999fa200
2017-11-23T14:01:58.172701+00:00 jabberwock kernel: [  131.303762] RBP: ffffb4bcc3e83d48 R08: 0000000000000043 R09: ffffb4bcc3e83c48
2017-11-23T14:01:58.172703+00:00 jabberwock kernel: [  131.303764] R10: ffffb4bcc3e83cc0 R11: ffffa0904c7ed075 R12: ffffa08ef3638ac8
2017-11-23T14:01:58.172704+00:00 jabberwock kernel: [  131.303766] R13: ffffffffaa3830e0 R14: ffffa08e99958080 R15: 0000000000000001
2017-11-23T14:01:58.172706+00:00 jabberwock kernel: [  131.303769] FS:  00007f77526ff700(0000) GS:ffffa0905fb80000(0000) knlGS:0000000000000000
2017-11-23T14:01:58.172708+00:00 jabberwock kernel: [  131.303771] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2017-11-23T14:01:58.172710+00:00 jabberwock kernel: [  131.303773] CR2: fffffffe29672320 CR3: 00000002cac1c005 CR4: 00000000001606e0
2017-11-23T14:01:58.172711+00:00 jabberwock kernel: [  131.303776] Call Trace:
2017-11-23T14:01:58.172713+00:00 jabberwock kernel: [  131.303782]  common_lsm_audit+0x1d3/0x750
2017-11-23T14:01:58.172714+00:00 jabberwock kernel: [  131.303815]  ? btrfs_get_token_32+0x5b/0x120 [btrfs]
2017-11-23T14:01:58.172717+00:00 jabberwock kernel: [  131.303819]  ? aa_check_perms+0xe4/0x100
2017-11-23T14:01:58.172718+00:00 jabberwock kernel: [  131.303830]  aa_check_perms+0xe4/0x100
2017-11-23T14:01:58.172720+00:00 jabberwock kernel: [  131.303833]  profile_signal_perm.part.2+0x90/0xa0
2017-11-23T14:01:58.172721+00:00 jabberwock kernel: [  131.303836]  aa_may_signal+0x18e/0x1d0
2017-11-23T14:01:58.172723+00:00 jabberwock kernel: [  131.303839]  apparmor_task_kill+0x52/0x120
2017-11-23T14:01:58.172725+00:00 jabberwock kernel: [  131.303842]  security_task_kill+0x44/0x60
2017-11-23T14:01:58.172727+00:00 jabberwock kernel: [  131.303846]  group_send_sig_info+0x25/0x60
2017-11-23T14:01:58.172729+00:00 jabberwock kernel: [  131.303848]  kill_pid_info+0x38/0x70
2017-11-23T14:01:58.172731+00:00 jabberwock kernel: [  131.303851]  ? __task_pid_nr_ns+0xbf/0xd0
2017-11-23T14:01:58.172733+00:00 jabberwock kernel: [  131.303853]  SYSC_kill+0xce/0x180
2017-11-23T14:01:58.172734+00:00 jabberwock kernel: [  131.303856]  ? __do_page_fault+0x26b/0x500
2017-11-23T14:01:58.172736+00:00 jabberwock kernel: [  131.303859]  entry_SYSCALL_64_fastpath+0x1e/0xa9
2017-11-23T14:01:58.172737+00:00 jabberwock kernel: [  131.303861] RIP: 0033:0x7f7798bca3b7
2017-11-23T14:01:58.172739+00:00 jabberwock kernel: [  131.303863] RSP: 002b:00007f77526fe498 EFLAGS: 00000202 ORIG_RAX: 000000000000003e
2017-11-23T14:01:58.172741+00:00 jabberwock kernel: [  131.303865] RAX: ffffffffffffffda RBX: 00007f77380ae440 RCX: 00007f7798bca3b7
2017-11-23T14:01:58.172742+00:00 jabberwock kernel: [  131.303867] RDX: 0000000000000b7b RSI: 0000000000000009 RDI: 0000000000000b7b
2017-11-23T14:01:58.172744+00:00 jabberwock kernel: [  131.303869] RBP: 00000000ffffffff R08: 00007f7755146500 R09: 0000000000000000
2017-11-23T14:01:58.172745+00:00 jabberwock kernel: [  131.303871] R10: 00007f77551438ad R11: 0000000000000202 R12: 00000000ffffffff
2017-11-23T14:01:58.172747+00:00 jabberwock kernel: [  131.303872] R13: 00007f77380ae440 R14: 00007f7755144022 R15: 0000000000000000
2017-11-23T14:01:58.172749+00:00 jabberwock kernel: [  131.303875] Code: 48 8b 55 18 48 89 df 41 b8 20 00 08 01 5b 5d 48 8b 42 10 48 8b 52 30 48 63 48 4c 48 8b 44 c8 48 31 c9 48 8b 70 38 e9 e4 fc 00 00 <48> 8b 14 d5 a0 4e 85 aa 48 c7 c6 04 a3 a7 aa 48 89 df e8 3d 7f
2017-11-23T14:01:58.172751+00:00 jabberwock kernel: [  131.303899] RIP: audit_signal_cb+0x6c/0xe0 RSP: ffffb4bcc3e83c08
2017-11-23T14:01:58.172753+00:00 jabberwock kernel: [  131.303900] CR2: fffffffe29672320
2017-11-23T14:01:58.172755+00:00 jabberwock kernel: [  131.303903] ---[ end trace 3d6dc382c87a2129 ]---
2017-11-23T14:01:58.172757+00:00 jabberwock kernel: [  131.303919] ------------[ cut here ]------------
2017-11-23T14:01:58.172758+00:00 jabberwock kernel: [  131.303923] WARNING: CPU: 3 PID: 2931 at ../kernel/rcu/tree_plugin.h:329 rcu_note_context_switch+0x5e/0x4f0
2017-11-23T14:01:58.172760+00:00 jabberwock kernel: [  131.303925] Modules linked in: fuse ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables devlink af_packet bridge stp llc iscsi_ibft iscsi_boot_sysfs msr joydev ftdi_sio usbserial snd_hda_codec_hdmi hid_generic usbhid snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 nls_cp437 wmi_bmof vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel uas kvm irqbypass crct10dif_pclmul usb_storage crc32_pclmul intel_spi_platform intel_spi spi_nor ghash_clmulni_intel mtd iTCO_wdt iTCO_vendor_support pcbc ir_rc6_decoder aesni_intel aes_x86_64 crypto_simd glue_helper cryptd rc_rc6_mce pcspkr snd_soc_rt5640 snd_soc_rl6231 snd_soc_core snd_hda_intel tpm_tis ir_lirc_codec snd_hda_codec snd_compress tpm_tis_core lirc_dev snd_pcm_dmaengine snd_hda_core tpm
2017-11-23T14:01:58.172763+00:00 jabberwock kernel: [  131.303954]  snd_hwdep nuvoton_cir battery snd_pcm rc_core elan_i2c snd_timer snd_soc_sst_acpi snd_soc_sst_match gpio_lynxpoint dw_dmac fan spi_pxa2xx_platform thermal i2c_i801 wmi snd e1000e ptp mei_me soundcore mei lpc_ich pps_core btrfs xor zstd_decompress zstd_compress xxhash raid6_pq crc32c_intel i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ehci_pci ehci_hcd usbcore drm sdhci_acpi sdhci video mmc_core i2c_hid button sg nbd dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua ecryptfs efivarfs
2017-11-23T14:01:58.172765+00:00 jabberwock kernel: [  131.303980] CPU: 3 PID: 2931 Comm: libvirtd Tainted: G      D         4.14.0-1-default #1
2017-11-23T14:01:58.172767+00:00 jabberwock kernel: [  131.303982] Hardware name:                  /D54250WYK, BIOS WYLPT10H.86A.0045.2017.0302.2108 03/02/2017
2017-11-23T14:01:58.172768+00:00 jabberwock kernel: [  131.303985] task: ffffa08e99958080 task.stack: ffffb4bcc3e80000
2017-11-23T14:01:58.172770+00:00 jabberwock kernel: [  131.303988] RIP: 0010:rcu_note_context_switch+0x5e/0x4f0
2017-11-23T14:01:58.172772+00:00 jabberwock kernel: [  131.303991] RSP: 0018:ffffb4bcc3e83e28 EFLAGS: 00010006
2017-11-23T14:01:58.172773+00:00 jabberwock kernel: [  131.303994] RAX: 0000000000000003 RBX: ffffa08e99958080 RCX: ffffa08e99958480
2017-11-23T14:01:58.172775+00:00 jabberwock kernel: [  131.303996] RDX: 0000000000000001 RSI: ffffffffaa0ac72d RDI: 0000000000000000
2017-11-23T14:01:58.172777+00:00 jabberwock kernel: [  131.303999] RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000007f
2017-11-23T14:01:58.172778+00:00 jabberwock kernel: [  131.304001] R10: 0000000000000000 R11: 0000000000000068 R12: 0000000000000000
2017-11-23T14:01:58.172780+00:00 jabberwock kernel: [  131.304004] R13: ffffa08e99958080 R14: ffffa08e999586f8 R15: ffffa08f7cf50238
2017-11-23T14:01:58.172782+00:00 jabberwock kernel: [  131.304007] FS:  0000000000000000(0000) GS:ffffa0905fb80000(0000) knlGS:0000000000000000
2017-11-23T14:01:58.172784+00:00 jabberwock kernel: [  131.304010] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2017-11-23T14:01:58.172785+00:00 jabberwock kernel: [  131.304012] CR2: fffffffe29672320 CR3: 00000001d3c09001 CR4: 00000000001606e0
2017-11-23T14:01:58.172787+00:00 jabberwock kernel: [  131.304015] Call Trace:
2017-11-23T14:01:58.172789+00:00 jabberwock kernel: [  131.304019]  __schedule+0x94/0x870
2017-11-23T14:01:58.172791+00:00 jabberwock kernel: [  131.304023]  ? release_task+0x363/0x4a0
2017-11-23T14:01:58.172792+00:00 jabberwock kernel: [  131.304028]  do_task_dead+0x3d/0x40
2017-11-23T14:01:58.172793+00:00 jabberwock kernel: [  131.304031]  do_exit+0x704/0xb40
2017-11-23T14:01:58.172795+00:00 jabberwock kernel: [  131.304035]  rewind_stack_do_exit+0x17/0x20
2017-11-23T14:01:58.172797+00:00 jabberwock kernel: [  131.304038] Code: de f2 55 84 c0 0f 85 75 02 00 00 65 48 8b 1c 25 c0 d3 00 00 40 84 ed 8b 83 f8 03 00 00 0f 85 05 01 00 00 85 c0 0f 8e 05 01 00 00 <0f> ff 80 bb fc 03 00 00 00 0f 84 79 01 00 00 65 66 8b 05 e3 da
2017-11-23T14:01:58.172798+00:00 jabberwock kernel: [  131.304061] ---[ end trace 3d6dc382c87a212a ]---
2017-11-23T14:02:58.176748+00:00 jabberwock kernel: [  191.310007] INFO: rcu_preempt detected stalls on CPUs/tasks:
2017-11-23T14:02:58.176785+00:00 jabberwock kernel: [  191.310052] Tasks blocked on level-0 rcu_node (CPUs 0-3): P2931
2017-11-23T14:02:58.176797+00:00 jabberwock kernel: [  191.310072] (detected by 3, t=15002 jiffies, g=4568, c=4567, q=3870)



--
============================
Roger Whittaker
[hidden email]
https://notes.smuvelious.org
============================
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel oops when starting a QEMU/KVM virtual machines

Giuseppe Gorgoglione
In reply to this post by Jiri Slaby-6
On Thu, Nov 23, 2017 at 2:31 PM, Jiri Slaby <[hidden email]> wrote:

> On 11/23/2017, 11:15 AM, Roger Whittaker wrote:
>> On Thu, Nov 23, 2017 at 11:05:21AM +0100, Giuseppe Gorgoglione wrote:
>>
>>> After upgrading my Tumbleweed box to snapshot 20171120, the first one
>>> with kernel 4.14, I get oops every time I try to start QEMU/KVM
>>> virtual machines. More details here:
>>> https://bugzilla.suse.com/show_bug.cgi?id=1069562
>>>
>>> Anybody experiencing the same?
>>
>> Yes - I've seen this as well.
>>
>> But I think it's related to
>>
>> https://lists.opensuse.org/opensuse-factory/2017-11/msg00572.html
>
> The kernel shall not crash no matter what profile you provide.


Indeed, the kernel 4.14 alone, as provided by snapshot 20171120 was
oopsing for me. The libvirt update delivered by snapshot 20171121
fixed the oops and now starting virtual machines just fails because of
the apparmor profile which needs to be updated.

Kind regards,
Giuseppe.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel oops when starting a QEMU/KVM virtual machines

Jiri Slaby-6
In reply to this post by Roger Whittaker-2
On 11/23/2017, 03:05 PM, Roger Whittaker wrote:
> On Thu, Nov 23, 2017 at 02:31:52PM +0100, Jiri Slaby wrote:
>
>> The kernel shall not crash no matter what profile you provide.
>
> It's not a crash - it's this (as soon as I do "virsh list" for instance):
>
> 2017-11-23T14:01:58.172651+00:00 jabberwock kernel: [  131.303644] BUG: unable to handle kernel paging request at fffffffe29672320

And what this is if not crash :D?

--
js
suse labs
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Kernel oops when starting a QEMU/KVM virtual machines

Martin Herkt
In reply to this post by Giuseppe Gorgoglione
On Thu, Nov 23, 2017 15:10:27 CET Giuseppe Gorgoglione wrote:

> On Thu, Nov 23, 2017 at 2:31 PM, Jiri Slaby <[hidden email]> wrote:
> > On 11/23/2017, 11:15 AM, Roger Whittaker wrote:
> >> On Thu, Nov 23, 2017 at 11:05:21AM +0100, Giuseppe Gorgoglione wrote:
> >>> After upgrading my Tumbleweed box to snapshot 20171120, the first one
> >>> with kernel 4.14, I get oops every time I try to start QEMU/KVM
> >>> virtual machines. More details here:
> >>> https://bugzilla.suse.com/show_bug.cgi?id=1069562
> >>>
> >>> Anybody experiencing the same?
> >>
> >> Yes - I've seen this as well.
> >>
> >> But I think it's related to
> >>
> >> https://lists.opensuse.org/opensuse-factory/2017-11/msg00572.html
> >
> > The kernel shall not crash no matter what profile you provide.
>
> Indeed, the kernel 4.14 alone, as provided by snapshot 20171120 was
> oopsing for me. The libvirt update delivered by snapshot 20171121
> fixed the oops and now starting virtual machines just fails because of
> the apparmor profile which needs to be updated.
This is still causing issues here. No AppArmor problems, but I’m seeing kernel
oopses and the machine will destabilize soon after that, with fork() syscalls
failing and whatnot. Very nasty. Can’t even ssh into it or do a clean reboot
when that happens. It damn nearly broke the bootloader, as it happened while I
was running a zypper dup with kernel package triggers…

No issues with older kernels.

signature.asc (235 bytes) Download Attachment