[Bug 1069955] New: Apparmor profile for QEMU/KVM needs to be updated
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955 Bug ID: 1069955 Summary: Apparmor profile for QEMU/KVM needs to be updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs@forge.provo.novell.com Reporter: gorgoglione@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- This report comes as a consequence of bug 1069562. After the kernel update to version 4.14 which came with snapshot 20171120, it is not possible anymore to start a QEMU/KVM virtual machine when the apparmor service is running. Starting a virtual machine I get either the kernel oops or the Virtual Machine Manager error described in ticket 1069562. As a temporary workaround, stopping the apparmor service fixes the issue. The problem is still present with kernel 4.14.1 delivered by snapshot 20171125. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955#c1
Tony Su
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955#c2
James Fehlig
The problem is still present with kernel 4.14.1 delivered by snapshot 20171125.
Does that kernel contain the fix for bug#1069562? If so, please provide output of /var/log/audit/audit.log when attempting to start a VM. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955#c3
--- Comment #3 from Giuseppe Gorgoglione
Does that kernel contain the fix for bug#1069562? If so, please provide output of /var/log/audit/audit.log when attempting to start a VM. Thanks.
I don't think so: the kernel 4.14.1 is still oopsing. I opened this bug as a consequence of Jiri Slabi's suggestion in comment 5 of bug 1069562: "the original bug is now fixed. You should create a new one for the apparmor update", but actually now it's not clear to me if he was referring to the kernel 4.14.1 which was released short after or to some other version which is currently in staging. By the way, I'm sending you in attachment the audit.log after the oops. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955#c4
--- Comment #4 from Giuseppe Gorgoglione
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955
http://bugzilla.opensuse.org/show_bug.cgi?id=1069955#c5
--- Comment #5 from James Fehlig
(In reply to James Fehlig from comment #2)
Does that kernel contain the fix for bug#1069562? If so, please provide output of /var/log/audit/audit.log when attempting to start a VM. Thanks.
I don't think so: the kernel 4.14.1 is still oopsing.
I just checked kernel-default-4.14.1-1.4 and indeed it does not mention bug#1069562 nor the upstream patch "apparmor: fix oops in audit_signal_cb hook".
I opened this bug as a consequence of Jiri Slabi's suggestion in comment 5 of bug 1069562: "the original bug is now fixed. You should create a new one for the apparmor update", but actually now it's not clear to me if he was referring to the kernel 4.14.1 which was released short after or to some other version which is currently in staging.
IMO, before proceeding here, you'll need a kernel containing the fix for bug#1069562. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com