From owner-freebsd-virtualization@freebsd.org Mon Apr 25 20:51:00 2016 Return-Path: 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 267E9B1C853 for ; Mon, 25 Apr 2016 20:51:00 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 94AD317C4 for ; Mon, 25 Apr 2016 20:50:59 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u3PKos7W076631 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 25 Apr 2016 20:50:54 GMT (envelope-from saper@saper.info) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=saper.info; s=Sep2014; t=1461617454; bh=2ZnXC2MZ22m0kp5uxOSMMuwa4kDctGLu7MgQtczCuTY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=MQc9wZ1a0J7j2sNKWNJn8U7HVCV/e3y2lxAzg1DP2mfvANzkQMD6PSb7av+1A4M/z Zf9aGO0STfgRw1YdPJgRVEBySZpDhWcSc2qeRFnIfkkOF7bKaTsC60/SCFuAaS47zZ 8AxkXPnQBMe9AAUCfNbmPqOULzVRRHs7gzOogbjs= Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u3PKorGj076628; Mon, 25 Apr 2016 20:50:54 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Mon, 25 Apr 2016 20:50:53 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-virtualization@freebsd.org Subject: Re: Booting r298488 as Xen Dom0 may break ZFS pool? In-Reply-To: Message-ID: References: <20160425084714.64ejioyqgquwu4gw@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-15 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2016 20:51:00 -0000 On Mon, 25 Apr 2016, Marcin Cieslak wrote: > On Mon, 25 Apr 2016, Marcin Cieslak wrote: > > > On Mon, 25 Apr 2016, Roger Pau Monné wrote: > > > TBH, I have no idea. Can you also paste the log of the system (Xen + > > > FreeBSD) when it fails to boot? If that's not possible, can you at least > > > paste the output of `xl dmesg` when booted correctly under Xen? > > I managed to boot it again... > > root@o:~ # xl dmesg > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > xc: error: Could not bounce buffer for version hypercall (35 = Resource temporarily unavailabl): Internal error > 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 Marcin