This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Error expanding grant table frames

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Error expanding grant table frames
From: "Phil Winterfield (winterfi)" <winterfi@xxxxxxxxx>
Date: Thu, 26 Aug 2010 17:07:02 -0700
Authentication-results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
Delivery-date: Thu, 26 Aug 2010 17:07:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: low
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Priority: Non-Urgent
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActFe8bMRHHGEv7ITXOLQPWI8jEDDA==
Thread-topic: Error expanding grant table frames

When I start up a 32-bit PV guest with a pair of passthrough NIC ports, I am seeing the following error:


(XEN) grant_table.c:1121:d1 Expanding dom (1) grant table from (4) to (16) frames.

(XEN) mm.c:883:d1 Error getting mfn 212ef (pfn 1d210) from L1 entry 00000000212ef023 for l1e_owner=1, pg_owner=1

(XEN) grant_table.c:266:d0 Bad flags (0) or dom (0). (expected dom 0)


I am running the 64-bit linux- pvops kernel for dom0 along with xen-unstable c/s 22068.  This problem has been around for quite a long time and was fixed in the OpenSuse11.1 release which had the linux-2.6.27 kernel for dom0 paired with xen-3.4.  In all of the subsequent releases that I have tried, the problem has returned.  A few searches have shown that the problem has been observed by others, usually when running 32-bit guests with passthrough NICs.  In some instances the error was observed when dom0 was mapping shared RX ring buffers.


Any ideas as to where something like this might be originating?


Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>