From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 195813] intel gvt/kvmgt: BUG: unable to handle kernel NULL
 pointer dereference at (null)
Date: Fri, 19 May 2017 16:01:43 +0000
Message-ID: <bug-195813-28872-P66uz3xu7Y@https.bugzilla.kernel.org/>
References: <bug-195813-28872@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
To: kvm@kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:34460 "EHLO
        mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1755867AbdESQBp (ORCPT
        <rfc822;kvm@vger.kernel.org>); Fri, 19 May 2017 12:01:45 -0400
Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1])
        by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 8BA5228927
        for <kvm@vger.kernel.org>; Fri, 19 May 2017 16:01:44 +0000 (UTC)
In-Reply-To: <bug-195813-28872@https.bugzilla.kernel.org/>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

https://bugzilla.kernel.org/show_bug.cgi?id=195813

Alex Williamson (alex.williamson@redhat.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alex.williamson@redhat.com

--- Comment #1 from Alex Williamson (alex.williamson@redhat.com) ---
While I agree that this should not result in a host oops (a bug remains in the
intel kvmgt driver), it is necessary to allow the vfio user sufficient locked
memory limits.  libvirt would do this for you if you used it, otherwise you
should configure the user running the VM with a locked memory limit at least
equal to the VM memory size (4G, the default is 64k).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.