Mailinglist Archive: opensuse-factory (765 mails)

< Previous Next >
Re: [opensuse-factory] Kernel oops when starting a QEMU/KVM virtual machines
  • From: Martin Herkt <lachs0r@xxxxxxxxxxx>
  • Date: Sat, 25 Nov 2017 09:29:49 +0100
  • Message-id: <1831122.rpzAhbyxgx@sakuya>
On Thu, Nov 23, 2017 15:10:27 CET Giuseppe Gorgoglione wrote:
On Thu, Nov 23, 2017 at 2:31 PM, Jiri Slaby <jslaby@xxxxxxx> 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.
< Previous Next >