From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Johnson Subject: Re: ZFS version for pygrub Date: Fri, 23 Apr 2010 09:27:42 -0400 Message-ID: References: <521a4d121003191240o7f12f7b5u176a1f10a073d2f7@mail.gmail.com> <521a4d121003270437v6afaec9eg1afead31b5c64274@mail.gmail.com> <20100327114759.GZ1878@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: eXeC001er Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Apr 23, 2010 at 8:29 AM, eXeC001er wrote: > > 2010/4/23 Mark Johnson >> >> On Fri, Apr 23, 2010 at 8:18 AM, eXeC001er wrote: >> > I use latest revision of xen-unstable, kernel-2.6.32-4 from 'Debian Si= d' >> > and >> > Debian Squeeze for Dom0. >> > I tried to create Opensolaris b132 DomU: >> > my config (i use config >> > from=A0http://blogs.sun.com/mrj/entry/installing_opensolaris_on): >> >>:# cat ns.pv_i >> > bootloader =3D "/usr/bin/pygrub" >> > kernel =3D "/platform/i86xpv/kernel/amd64/unix" >> > ramdisk =3D "/boot/x86.microroot" >> > extra =3D "/platform/i86xpv/kernel/amd64/unix -B >> > console=3Dttya,livemode=3Dtext" >> > memory =3D 512 >> > name =3D "OS_PV" >> > vif =3D [ 'mac=3D00:16:3E:00:00:01', 'mac=3D00:16:3E:00:00:02' ] >> > disk =3D [ 'file:/opt/ISO/osol-dev-132-x86.iso,6:cdrom,r', >> > 'file:/opt/src/OS_PV/ns.img,0,w' ] >> > on_reboot =3D 'destroy' >> > on_crash =3D 'destroy' >> > on_poweroff =3D 'destroy' >> >> remove the kernel and ramdisk line above. e.g. >> >> =A0bootloader =3D "/usr/bin/pygrub" >> =A0extra =3D "/platform/i86xpv/kernel/amd64/unix -B >> console=3Dttya,livemode=3Dtext" >> =A0memory =3D 512 >> >> MRJ > > Using config file "./ns.pv_i". > Error: Boot loader didn't return any data! Oh, sorry about that, I was assuming that you were trying to boot of the zf= s root after completing install, not boot off the install iso.. So what I sai= d above should be correct once you've completed the install. Your trying to boot off the iso, which doesn't have anything to do with the pygrub zfs support of course. For the install iso, the location for the boot_archive has moved again... It's now @ /platform/i86pc/amd64/boot_archive I just did a py file on a Solaris dom0 for a osol134 iso. Here's what I did.. (note, our pygrub path is different and you would want to use file in place of tap:vdisk of course).. You don't need the addition arguments in extra.. Just the path to the kernel. You should use 1500M for memory for the install, then drop down after you have completed the install.. It will work with less, but I'm not sure what the cut off is... MRJ root@mckuen:~# cat install.py bootloader =3D "/usr/lib/xen/bin/pygrub" kernel =3D "/platform/i86xpv/kernel/amd64/unix" ramdisk =3D "/platform/i86pc/amd64/boot_archive" extra =3D "/platform/i86xpv/kernel/amd64/unix" memory =3D 1500 name =3D "osol134" vif =3D [''] disk =3D ['file:/xvm/isos/osol134.iso,xvdb:cdrom,r', 'tap:vdisk:/xvm/vdisks/osol134,xvda,w'] root@mckuen:~# xm create -c install.py Using config file "./install.py". Started domain osol134 (id=3D2) v3.4.2-xvm chgset 'Mon Mar 29 23:26:50 2010 -0700 19676:ea2b16b75b5c' SunOS Release 5.11 Version snv_134 64-bit Copyright 1983-2010 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.