xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: eXeC001er <execooler@gmail.com>
To: Mark Johnson <johnson.nh@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: ZFS version for pygrub
Date: Fri, 23 Apr 2010 16:29:03 +0400	[thread overview]
Message-ID: <v2kebc0b6391004230529q345c48ebo8fdb09cbce652c28@mail.gmail.com> (raw)
In-Reply-To: <n2v521a4d121004230526zda197c60p7c1cc467e8a97d4a@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2745 bytes --]

2010/4/23 Mark Johnson <johnson.nh@gmail.com>

> On Fri, Apr 23, 2010 at 8:18 AM, eXeC001er <execooler@gmail.com> 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!

>
> >>:# xm create ns.pv_i -c
> > Using config file "./ns.pv_i".
> > Error: Cannot find kernel "/platform/i86xpv/kernel/amd64/unix"
> > The method proposed by Boris Derzhavets works fine.
> > (
> http://bderzhavets.wordpress.com/2010/04/14/zfs-24-support-via-pygrub-fsimage-iso-patch-for-xen-4-0-dom0-pvops-2-6-32-11-on-top-of-f12/
> ).
> > p.s:
> >>:# pygrub /opt/ISO/osol-dev-132-x86.iso
> > linux (kernel /var/run/xend/boot/boot_kernel.GQYAjq)(ramdisk
> > /var/run/xend/boot/boot_ramdisk.Q_bPCY)(args
> > "/platform/i86xpv/kernel/amd64/unix")
> > Thanks.
> > 2010/4/7 eXeC001er <execooler@gmail.com>
> >>
> >> When this patch will be applied?
> >>
> >> 2010/3/27 Pasi Kärkkäinen <pasik@iki.fi>
> >>>
> >>> On Sat, Mar 27, 2010 at 07:37:03AM -0400, Mark Johnson wrote:
> >>> > On Fri, Mar 19, 2010 at 3:40 PM, Mark Johnson <johnson.nh@gmail.com>
> >>> > wrote:
> >>> > > On Fri, Mar 19, 2010 at 2:41 PM, eXeC001er <execooler@gmail.com>
> >>> > > wrote:
> >>> > >> Hi.
> >>> > >> When will be supported ZFS version more than 16 for pygrub?
> >>> > >> Current ZFS version is 22.
> >>> > >
> >>> > > I'm actively working on it  (current version is 24 now BTW).
> >>> >
> >>> > I pushed the patch to the OpenSolaris xvm-gate.
> >>> >
> >>> >
> http://src.opensolaris.org/source/xref/xen-gate/xvm-gate+xen-patches.hg/fsimage-zfs-24
> >>> >
> >>> > I'll be testing to see if it builds/works on a Linux dom0 next week.
> >>> >
> >>>
> >>> Great! This would be nice for Xen 4.0.0..
> >>>
> >>> -- Pasi
> >>>
> >>
> >
> >
>

[-- Attachment #1.2: Type: text/html, Size: 4660 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-04-23 12:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 18:41 ZFS version for pygrub eXeC001er
2010-03-19 19:40 ` Mark Johnson
2010-03-27 11:37   ` Mark Johnson
2010-03-27 11:47     ` Pasi Kärkkäinen
2010-04-07 17:16       ` eXeC001er
2010-04-23 12:18         ` eXeC001er
2010-04-23 12:26           ` Mark Johnson
2010-04-23 12:29             ` eXeC001er [this message]
2010-04-23 12:54               ` Boris Derzhavets
2010-04-23 13:27               ` Mark Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v2kebc0b6391004230529q345c48ebo8fdb09cbce652c28@mail.gmail.com \
    --to=execooler@gmail.com \
    --cc=johnson.nh@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).