From owner-freebsd-xen@freebsd.org  Fri Feb  3 10:15:20 2017
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 D61F8CCCE7D
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Fri,  3 Feb 2017 10:15:20 +0000 (UTC)
 (envelope-from prvs=200bd2211=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 217C1E7A;
 Fri,  3 Feb 2017 10:15:19 +0000 (UTC)
 (envelope-from prvs=200bd2211=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.33,328,1477958400"; d="scan'208";a="40053707"
Date: Fri, 3 Feb 2017 10:14:02 +0000
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Akshay Jaggi <jaggi@freebsd.org>
CC: FreeBSD-Xen <freebsd-xen@freebsd.org>
Subject: Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for
 XENBUS, xenbusb_nop_confighook_cb)
Message-ID: <20170203101402.dto7lzj2sldvuxl5@MacBook-Pro-de-Roger.local>
References: <A80956E3-F5A1-46BC-86C7-17BBF3DA8FB4@nfvexpress.com>
 <20170124114444.xdl3qj35lwebkso7@dhcp-3-221.uk.xensource.com>
 <159d0f04b55.10bbf935114648.7927688075504705395@nfvexpress.com>
 <20170124165621.iidjypfoyp4ccysi@dhcp-3-221.uk.xensource.com>
 <CAAeUNV=j5-Sz00PQCvC6rX7QeiEpbhD9uRCFSnqKP-dUFxjB-g@mail.gmail.com>
 <159d55b6b65.dc9b3b1720453.5847395326743424395@nfvexpress.com>
 <20170125115051.sasgqxwgt47p7pwi@dhcp-3-221.uk.xensource.com>
 <159d57da8bb.e9fea5dc25161.6113276104371162720@nfvexpress.com>
 <CAAeUNVnSqftw2WapWeWLUG7p9v9cm94gA_0wt-j6Wkj77RrSMg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAAeUNVnSqftw2WapWeWLUG7p9v9cm94gA_0wt-j6Wkj77RrSMg@mail.gmail.com>
User-Agent: NeoMutt/20170128 (1.7.2)
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: Fri, 03 Feb 2017 10:15:20 -0000

On Thu, Feb 02, 2017 at 11:37:02PM +0000, Akshay Jaggi wrote:
> [-Alex]
> 
> Hi Roger,
> 
> Did this get solved with the change you submitted to Xen?

This issue is cased by a bug in the VM subsystem, kib is currently looking into
it, and patches will be committed soon hopefully. The Xen patch I've sent is
the FreeBSD handlers for the gnttab lib, with that everything is already
upstream :). I will backport the Xen patch to your Xen package once the VM
issue is solved.

Thanks, Roger.