Date: Tue, 26 Apr 2016 09:11:51 +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: <20160426071151.ctzdaehgfhzij6q3@mac> In-Reply-To: <alpine.BSF.2.11.1604252048220.1768@z.fncre.vasb> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 25, 2016 at 08:50:53PM +0000, Marcin Cieslak wrote: > 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 And this also caused the ZFS corruption? Roger.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160426071151.ctzdaehgfhzij6q3>