Re: Xen Dom0

On 6/29/17, 5:01 AM, "Roger Pau Monné" wrote: Hello, Sorry for the delay, I don't read freebsd-virt as often as I should. There's also freebsd-xen@ for FreeBSD/Xen specific issues (although posting here is fine). On Wed, Jun 28, 2017 at

Re: Xen Dom0

Hello, Sorry for the delay, I don't read freebsd-virt as often as I should. There's also freebsd-xen@ for FreeBSD/Xen specific issues (although posting here is fine). On Wed, Jun 28, 2017 at 11:44:27PM -0500, Larry Rosenman wrote: > Any ideas? When was the last time that you updated world (or

Re: Xen Dom0

Any ideas? On 6/25/17, 8:28 AM, "Larry Rosenman" wrote: On Sun, Jun 25, 2017 at 07:50:25AM -0500, Larry Rosenman wrote: > On Sat, Jun 24, 2017 at 06:12:24PM -0400, Allan Jude wrote: > > On 2017-06-24 16:11,

Re: Xen Dom0

On Sun, Jun 25, 2017 at 07:50:25AM -0500, Larry Rosenman wrote: > On Sat, Jun 24, 2017 at 06:12:24PM -0400, Allan Jude wrote: > > On 2017-06-24 16:11, Larry Rosenman wrote: > > > I tried to play with Xen on my existing root-on-zfs system, and when it > > > tried to > > > load /boot/xen, it said

Re: Xen Dom0

On Sat, Jun 24, 2017 at 06:12:24PM -0400, Allan Jude wrote: > On 2017-06-24 16:11, Larry Rosenman wrote: > > I tried to play with Xen on my existing root-on-zfs system, and when it > > tried to > > load /boot/xen, it said it couldn't. > > > > This is on: > > > > FreeBSD borg.lerctr.org

Re: Xen Dom0

On 2017-06-24 16:11, Larry Rosenman wrote: > I tried to play with Xen on my existing root-on-zfs system, and when it tried > to > load /boot/xen, it said it couldn't. > > This is on: > > FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #33 r320190: Wed > Jun 21 10:22:24 CDT 2017

Xen Dom0

I tried to play with Xen on my existing root-on-zfs system, and when it tried to load /boot/xen, it said it couldn't. This is on: FreeBSD borg.lerctr.org 12.0-CURRENT FreeBSD 12.0-CURRENT #33 r320190: Wed Jun 21 10:22:24 CDT 2017 r...@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER amd64

Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Thu, May 05, 2016 at 10:20:51PM +, Marcin Cieslak wrote: > On Thu, 5 May 2016, Roger Pau Monné wrote: > > > On Sat, Apr 30, 2016 at 08:56:54PM +, Marcin Cieslak wrote: > > > > Certainly. I assumed that you meant it crashed the VM, not the whole > > > > host. > > > > Can you please

Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Thu, 5 May 2016, Roger Pau Monné wrote: > On Sat, Apr 30, 2016 at 08:56:54PM +, Marcin Cieslak wrote: > > > Certainly. I assumed that you meant it crashed the VM, not the whole > > > host. > > > Can you please provide the trace of the crash? > > > > Apologies, forgot to let Xen keep

Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Sat, Apr 30, 2016 at 08:56:54PM +, Marcin Cieslak wrote: > On Fri, 29 Apr 2016, Roger Pau Monné wrote: > > > On Thu, Apr 28, 2016 at 08:01:23PM +, Marcin Cieslak wrote: > > > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > > > > > On Tue, Apr 26, 2016 at 10:39:06AM +, Marcin

Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Thu, Apr 28, 2016 at 08:01:23PM +, Marcin Cieslak wrote: > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > On Tue, Apr 26, 2016 at 10:39:06AM +, Marcin Cieslak wrote: > > > By the way, I just managed to crash a whole machine by trying to > > > boot Solaris 11.3: > > > > > > #

Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Tue, 26 Apr 2016, Roger Pau Monné wrote: > On Tue, Apr 26, 2016 at 10:39:06AM +, Marcin Cieslak wrote: > > By the way, I just managed to crash a whole machine by trying to > > boot Solaris 11.3: > > > > # builder = "hvm" > > memory = 2048 > > vcpus = 1 > > name = "Solaris0" > > disk = [

Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Tue, Apr 26, 2016 at 10:39:06AM +, Marcin Cieslak wrote: > Yes, should be easy. Will try to plug a binary port in. Thanks :). > By the way, I just managed to crash a whole machine by trying to > boot Solaris 11.3: > > # builder = "hvm" > memory = 2048 > vcpus = 1 > name = "Solaris0" >

Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Tue, 26 Apr 2016, Roger Pau Monné wrote: > On Tue, Apr 26, 2016 at 09:24:30AM +, Marcin Cieslak wrote: > > I got lazy and I have downloaded > > > > https://sourceforge.net/projects/edk2/files/OVMF/OVMF-X64-r15214.zip/download > > > > recompiled xen-tools by adding to xen-tools/Makefile >

Re: Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Tue, Apr 26, 2016 at 09:24:30AM +, Marcin Cieslak wrote: > I got lazy and I have downloaded > > https://sourceforge.net/projects/edk2/files/OVMF/OVMF-X64-r15214.zip/download > > recompiled xen-tools by adding to xen-tools/Makefile > > CONFIGURE_ARGS+=--enable-ovmf >

Booting Windows/UEFI (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)

On Tue, 26 Apr 2016, Marcin Cieslak wrote: > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > 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

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

On Tue, 26 Apr 2016, Roger Pau Monné wrote: > 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

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

On Tue, Apr 26, 2016 at 07:16:25AM +, 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 ... > > > > > >

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

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 > > > >

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

On Mon, Apr 25, 2016 at 08:50:53PM +, 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 + > > >

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

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 >

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

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

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

On Mon, 25 Apr 2016, Roger Pau Monné wrote: > > I have managed to make zpool boot again by doing voodoo > > similar to this one: > > > > [root@rescue ~]# zpool import -R /mnt zroot > > [root@rescue ~]# mount -t devfs devfs /mnt/dev > > [root@rescue ~]# chroot /mnt /bin/tcsh > > > > (... Running

Re: Booting r298488 as Xen Dom0 may break ZFS pool?

On Sat, Apr 23, 2016 at 10:40:20PM +, Marcin Cieslak wrote: > On a freshly installed (via upgrade from 10.3 from source) > -CURRENT on this machine: > > FreeBSD 11.0-CURRENT #0 r298488: Sat Apr 23 11:10:01 UTC 2016 > r...@o.saper.info:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang

Booting r298488 as Xen Dom0 may break ZFS pool?

On a freshly installed (via upgrade from 10.3 from source) -CURRENT on this machine: FreeBSD 11.0-CURRENT #0 r298488: Sat Apr 23 11:10:01 UTC 2016 r...@o.saper.info:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) WARNING:

Re: HEAD UP: notice to FreeBSD/Xen Dom0 users

Hello, El 15/08/15 a les 15.36, Outback Dingo ha escrit: HEAD UP on 10.2 the instructions found at http://wiki.xen.org/wiki/FreeBSD_Dom0 git branch master * stable-4.5 no longer appear to work gmake -j8 install-tools HOSTCC=gcc48 CC=gcc48 fails with __SNIP__

Re: HEAD UP: notice to FreeBSD/Xen Dom0 users

On Fri, Jun 26, 2015 at 5:19 PM, Roger Pau Monné roy...@freebsd.org wrote: Hello, If you are running a FreeBSD/Xen Dom0 and update FreeBSD to r284870 or any later revision make sure you are using the xen-kernel-4.5.0_4 and xen-tools-4.5.0_7 packages (or any later version), or else you won't

HEAD UP: notice to FreeBSD/Xen Dom0 users

Hello, If you are running a FreeBSD/Xen Dom0 and update FreeBSD to r284870 or any later revision make sure you are using the xen-kernel-4.5.0_4 and xen-tools-4.5.0_7 packages (or any later version), or else you won't be able to boot. Sorry for the trouble this might cause. Be aware that the Xen