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


Re: 答复: RE: 答复: RE: [Xen-devel] start stubdom issue

To: James Song <jsong@xxxxxxxxxx>
Subject: Re: 答复: RE: 答复: RE: [Xen-devel] start stubdom issue
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Date: Fri, 19 Sep 2008 12:34:06 +0200
Cc: guanqun.lu@xxxxxxxxx, Bhaskar.Jayaraman@xxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 Sep 2008 03:34:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48D3F99902000020000046E7@xxxxxxxxxxxxxxxxxxxxxxx>
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>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, James Song <jsong@xxxxxxxxxx>, guanqun.lu@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Bhaskar.Jayaraman@xxxxxxx
References: <48D3F99902000020000046E7@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
James Song, le Fri 19 Sep 2008 03:12:24 -0600, a écrit :
> Path changed backend/vfs/exports/requests/10/0/frontend
> Handling connection from dom=10, for export=0
> Frontend found at: /local/domain/10/device/vfs/0 (gref=1789, evtchn=5)
> Our own dom_id=0
> ERROR Internal error: Could not open grant table interface (22 = Invalid 
> argument)
> fs-backend: fs-backend.c:239: handle_connection: Assertion `mount->gnth != 
> -1' failed.

Mmm, are you perhaps running an old version of the dom0 kernel?  Could
you strace fs-backend to know which precise syscall is failing?


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>