From: Yu Zhiguo <yuzg@cn.fujitsu.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] Don't attach needless options when launch pygrub
Date: Wed, 14 Jul 2010 17:36:20 +0800 [thread overview]
Message-ID: <4C3D8514.6040901@cn.fujitsu.com> (raw)
In-Reply-To: <1279095028.24714.186.camel@zakaz.uk.xensource.com>
Ian Campbell wrote:
>
> As far as I can see the --kernel and --ramdisk options end up in the
> incfg map which only used in a handful of places, most of which just
> extract incfg["args"]. The only places which do not do this are the
> calls to sniff_solaris and sniff_netware both of which appear to make
> use of incfg["kernel"] (but not incfg["ramdisk"]).
>
> So it looks like specifying the kernel option in addition to bootloader
> is infact useful if you are booting a Solaris or Netware domU but is
> harmless/ignored otherwise. I think we need to continue to support this
It seems that incfg will be returned directly if DomU is not Solaris,
def sniff_solaris(fs, cfg):
if not fs.file_exists("/platform/i86xpv/kernel/unix"):
return cfg
chosencfg = sniff_solaris(fs, incfg)
So, incfg change to chosencfg and then will be used.
Should we fix sniff_solaris let it don't modify chosencfg if DomU
is not Solaris at least?
> use case and I don't see any particular reason to force those users to
> change their configuration file syntax for this issue (if it's even an
> issue, I still don't really see the problem).
>
> Perhaps it would be better to update pygrub so that --kernel actually
> does something consistent in the non-{Solaris,Netware} case, such as
> perhaps selecting the configuration entry with the match kernel path
> instead of defaulting to entry 0? (e.g. make "-q --kernel=/boot/FOO"
> select the entry with kernel /boot/FOO)
>
What about copy the specified 'kernel' from DomU to a temp file.
If there are 'bootloader' but no 'kernel', pygrub will copy and create temp file.
We can do the same things.
Yu
> It looks like --ramdisk (and the associated plumbing through xend) may
> in fact be useless at this time. I'd say it is harmless to plumb it
> through for consistency though -- perhaps in the future pygrub (or
> another bootloader) might want to use it.
>
> Ian.
>
>
>
>
--
Regards
Yu Zhiguo
--------------------------------------------------
Yu Zhiguo
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
8/F., Civil Defense Building, No.189 Guangzhou Road,
Nanjing, 210029, China
TEL: +86+25-86630566-853
COINS: 79955-853
FAX: +86+25-83317685
MAIL: yuzg@cn.fujitsu.com
--------------------------------------------------
This communication is for use by the intended recipient(s) only and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not an intended recipient of this communication, you are hereby notified that any dissemination, distribution or copying hereof is strictly prohibited. If you have received this communication in error, please notify me by reply e-mail, permanently delete this communication from your system, and destroy any hard copies you may have printed.
next prev parent reply other threads:[~2010-07-14 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 6:15 [PATCH] Don't attach needless options when launch pygrub Yu Zhiguo
2010-07-14 6:47 ` Ian Campbell
2010-07-14 7:29 ` Yu Zhiguo
2010-07-14 8:10 ` Ian Campbell
2010-07-14 9:36 ` Yu Zhiguo [this message]
2010-07-14 9:46 ` Ian Campbell
2010-07-14 10:07 ` Yu Zhiguo
2010-07-14 10:21 ` Yu Zhiguo
2010-07-14 10:22 ` Ian Campbell
2010-07-14 11:01 ` Yu Zhiguo
2010-07-14 11:10 ` Ian Campbell
2010-07-14 11:21 ` Yu Zhiguo
2010-07-14 12:33 ` Ian Campbell
2010-07-15 2:37 ` [PATCH] xm: needless to check 'kernel/ramdisk' is existent or not Yu Zhiguo
2010-07-15 7:42 ` Ian Campbell
2010-07-15 7:56 ` Ian Campbell
2010-07-15 3:44 ` [PATCH] Don't attach needless options when launch pygrub Zhigang Wang
2010-07-15 5:03 ` Yu Zhiguo
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=4C3D8514.6040901@cn.fujitsu.com \
--to=yuzg@cn.fujitsu.com \
--cc=Ian.Campbell@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.