From owner-freebsd-xen@freebsd.org  Mon Dec 12 10:33:03 2016
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D21DC714B0
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon, 12 Dec 2016 10:33:03 +0000 (UTC)
 (envelope-from prvs=1477f1691=roger.pau@citrix.com)
Received: from SMTP.EU.CITRIX.COM (smtp.ctxuk.citrix.com [185.25.65.24])
 (using TLSv1.2 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "DigiCert SHA2 Secure Server CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D5CB52F7
 for <freebsd-xen@freebsd.org>; Mon, 12 Dec 2016 10:33:01 +0000 (UTC)
 (envelope-from prvs=1477f1691=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.33,335,1477958400"; d="scan'208";a="36611905"
Date: Mon, 12 Dec 2016 10:32:57 +0000
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Nathan Friess <nathan.friess@gmail.com>
CC: <freebsd-xen@freebsd.org>
Subject: Re: 11-RELEASE acting as vbd backend
Message-ID: <20161212103257.tg46q2s3j5riixp5@dhcp-3-221.uk.xensource.com>
References: <247e5b6c-2713-27cf-f8fa-61e55c9e2025@gmail.com>
 <20161206100414.pi7ep2zbkduhuol7@dhcp-3-221.uk.xensource.com>
 <39e43ae4-6388-c698-c3c2-43cbc1f7b93c@gmail.com>
 <20161209144630.dfga5mozh72veo4g@dhcp-3-221.uk.xensource.com>
 <584ADC91.8050909@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <584ADC91.8050909@gmail.com>
User-Agent: NeoMutt/20161126 (1.7.1)
X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To
 AMSPEX02CL02.citrite.net (10.69.22.126)
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Dec 2016 10:33:03 -0000

On Fri, Dec 09, 2016 at 09:32:17AM -0700, Nathan Friess wrote:
> On 16-12-09 07:46 AM, Roger Pau Monné wrote:
> > Hello,
> > 
> > Sorry for the delay, there was a huge can of worms behind this. I have a
> > solution, but it requires patching both Xen and the FreeBSD kernel. Please bear
> > with me, I will send those patches once ready.
> 
> It sounds like you might know this already, but I did some more digging and
> here is what I can see so far...
> 
> The important command is "xl devd".  Running that under truss, it is trying
> to open /dev/xen/xenbus and that was the cause of the No such file error.
> It looks like the 10.3 tools used to open /dev/xen/xenstore instead.
> 
> I can get around this by exporting XENSTORED_PATH="/dev/xen/xenstore".
> 
> Now xl devd is stuck at:
> 
> libxl: error: libxl_event.c:639:libxl__ev_xswatch_register: create watch for
> path /local/domain/7/backend: Invalid argument
> 
> So it seems like an API issue with asking the kernel or dom0 to set a watch
> for new backend devices.

Yes, the current xenstore user-space device on FreeBSD is missing the ability to 
register xenstore watches. As said, I will hopefully be able to send the patches 
soon.

Thanks, Roger.