From owner-freebsd-xen@freebsd.org  Mon Feb 27 15:35:42 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 93848CF0C44
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Mon, 27 Feb 2017 15:35:42 +0000 (UTC)
 (envelope-from prvs=224a17244=roger.pau@citrix.com)
Received: from SMTP.EU.CITRIX.COM (smtp.eu.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 DE92A1EB;
 Mon, 27 Feb 2017 15:35:41 +0000 (UTC)
 (envelope-from prvs=224a17244=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.35,215,1484006400"; d="scan'208";a="41503490"
Date: Mon, 27 Feb 2017 15:34:50 +0000
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Alexander Nusov <alexander.nusov@nfvexpress.com>
CC: <jaggi@freebsd.org>, <freebsd-xen@freebsd.org>
Subject: Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for
 XENBUS, xenbusb_nop_confighook_cb)
Message-ID: <20170227153450.m6x5tjaaek4axrdt@dhcp-3-221.uk.xensource.com>
References: <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>
 <20170203101402.dto7lzj2sldvuxl5@MacBook-Pro-de-Roger.local>
 <15a37e9d6eb.11239b0492614.5094818896052410185@nfvexpress.com>
 <15a80318042.b57369e466511.8378002830472905142@nfvexpress.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <15a80318042.b57369e466511.8378002830472905142@nfvexpress.com>
User-Agent: NeoMutt/20170206 (1.7.2)
X-ClientProxiedBy: AMSPEX02CAS01.citrite.net (10.69.22.112) 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, 27 Feb 2017 15:35:42 -0000

On Mon, Feb 27, 2017 at 06:30:12PM +0300, Alexander Nusov wrote:
> Hi, 
> Sorry for top posting.
> 
> Any update on the issue?
> Please let me know if I need open a bug in Bugzilla.

Sadly it seems like there are still some loose ends on the VM subsystem. I hope
those will be fixed soon. Have you tried with HEAD recently?

Roger.