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.
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to