[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] ZFS version for pygrub


  • To: eXeC001er <execooler@xxxxxxxxx>
  • From: Mark Johnson <johnson.nh@xxxxxxxxx>
  • Date: Fri, 23 Apr 2010 09:27:42 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 23 Apr 2010 06:28:37 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oQO6AXRvRXkGvTJ9Ndn6jc2LHaT50ztE+u5GaRfFNKp9qhVUpEAO1I410Exbb2jJY7 ac25auMc1AcwvBTOoON8KyDrEGqbc9874DFxVmNuRJjZ13F0bXkseneY+4Cgw0hZDBYs FP8hMxus5aEMnQvBi3yM8kr1aIrLASxFaALgM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Fri, Apr 23, 2010 at 8:29 AM, eXeC001er <execooler@xxxxxxxxx> wrote:
>
> 2010/4/23 Mark Johnson <johnson.nh@xxxxxxxxx>
>>
>> On Fri, Apr 23, 2010 at 8:18 AM, eXeC001er <execooler@xxxxxxxxx> wrote:
>> > I use latest revision of xen-unstable, kernel-2.6.32-4 from 'Debian Sid'
>> > and
>> > Debian Squeeze for Dom0.
>> > I tried to create Opensolaris b132 DomU:
>> > my config (i use config
>> > from http://blogs.sun.com/mrj/entry/installing_opensolaris_on):
>> >>:# cat ns.pv_i
>> > bootloader = "/usr/bin/pygrub"
>> > kernel = "/platform/i86xpv/kernel/amd64/unix"
>> > ramdisk = "/boot/x86.microroot"
>> > extra = "/platform/i86xpv/kernel/amd64/unix -B
>> > console=ttya,livemode=text"
>> > memory = 512
>> > name = "OS_PV"
>> > vif = [ 'mac=00:16:3E:00:00:01', 'mac=00:16:3E:00:00:02' ]
>> > disk = [ 'file:/opt/ISO/osol-dev-132-x86.iso,6:cdrom,r',
>> > 'file:/opt/src/OS_PV/ns.img,0,w' ]
>> > on_reboot = 'destroy'
>> > on_crash = 'destroy'
>> > on_poweroff = 'destroy'
>>
>> remove the kernel and ramdisk line above. e.g.
>>
>>  bootloader = "/usr/bin/pygrub"
>>  extra = "/platform/i86xpv/kernel/amd64/unix -B
>> console=ttya,livemode=text"
>>  memory = 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 zfs
root after completing install, not boot off the install iso.. So what I said
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 = "/usr/lib/xen/bin/pygrub"
kernel = "/platform/i86xpv/kernel/amd64/unix"
ramdisk = "/platform/i86pc/amd64/boot_archive"
extra = "/platform/i86xpv/kernel/amd64/unix"
memory = 1500
name = "osol134"
vif = ['']
disk = ['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=2)
                             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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.