From owner-freebsd-virtualization@freebsd.org  Tue Apr 26 07:44:14 2016
Return-Path: <owner-freebsd-virtualization@freebsd.org>
Delivered-To: freebsd-virtualization@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 A9425B1CB5C
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Tue, 26 Apr 2016 07:44:14 +0000 (UTC)
 (envelope-from prvs=917dd492e=roger.pau@citrix.com)
Received: from SMTP.CITRIX.COM (smtp.citrix.com [66.165.176.89])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (Client CN "mail.citrix.com",
 Issuer "Verizon Public SureServer CA G14-SHA2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 69E06184C
 for <freebsd-virtualization@freebsd.org>; Tue, 26 Apr 2016 07:44:13 +0000 (UTC)
 (envelope-from prvs=917dd492e=roger.pau@citrix.com)
X-IronPort-AV: E=Sophos;i="5.24,536,1454976000"; d="scan'208";a="349777681"
Date: Tue, 26 Apr 2016 09:43:02 +0200
From: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
To: Marcin Cieslak <saper@saper.info>
CC: <freebsd-virtualization@freebsd.org>
Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool?
Message-ID: <20160426074302.4i3rv7wd5ogg7ful@mac>
References: <alpine.BSF.2.11.1604232216330.1768@z.fncre.vasb>
 <20160425084714.64ejioyqgquwu4gw@mac>
 <alpine.BSF.2.11.1604251906400.1768@z.fncre.vasb>
 <alpine.BSF.2.11.1604252000401.1768@z.fncre.vasb>
 <alpine.BSF.2.11.1604252048220.1768@z.fncre.vasb>
 <20160426071151.ctzdaehgfhzij6q3@mac>
 <alpine.BSF.2.11.1604260715130.1768@z.fncre.vasb>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <alpine.BSF.2.11.1604260715130.1768@z.fncre.vasb>
User-Agent: Mutt/1.6.0-neo (2016-04-07)
X-DLP: MIA2
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2016 07:44:14 -0000

On Tue, Apr 26, 2016 at 07:16:25AM +0000, Marcin Cieslak wrote:
> On Tue, 26 Apr 2016, Roger Pau Monné wrote:
> 
> > > > libxl: error: libxl.c:6121:libxl_xen_console_read_line: reading console ring buffer: Cannot allocate memory
> > > 
> > > It seems that my problem was ...
> > > 
> > > vm.max_wired=1
> > > 
> > > in /boot/loader.conf
> > > 
> > > instead of
> > > 
> > > vm.max_wired=-1
> > 
> > And this also caused the ZFS corruption?
> 
> Looks like it to me... Pretty strange.

I thought the max_wired sysctl node only affected the usage of wired memory 
by userspace applications, but it may have also prevented ZFS from using 
memory.
 
> Btw. is there any way to boot UEFI Windows partition under Xen?
> (it works fine under bhyve)

You will have to boot it using OVMF, which is not compiled with Xen by 
default. I will try to add an OVMF package (like the SeaBIOS one that we 
already have), and wire it into the xen-tools package.

If you want to try it yourself, you can add "--enable-ovmf" to the xen-tools 
package configure and see what breaks ;).

Roger.