From: Yu Zhiguo <yuzg@cn.fujitsu.com>
To: Zhigang Wang <zhigang.x.wang@oracle.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] Don't attach needless options when launch pygrub
Date: Thu, 15 Jul 2010 13:03:19 +0800 [thread overview]
Message-ID: <4C3E9697.7070409@cn.fujitsu.com> (raw)
In-Reply-To: <4C3E843A.9070008@oracle.com>
Hi,
Zhigang Wang wrote:
>>
>> 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.
>>
>
> Yes. Please don't remove --kernel/--ramdisk: pygrub is not the only pv guest
> bootloader.
>
> Here is a pv guest boot loader we are using which grab vmlinuz/initrd from
> network. It uses --kernle/--ramdisk parameters.
>
I made a mistake here, sorry for that.
I committed another patch and just ignore the kernel path check of Dom0
in 'xm create' when use bootloader, it works well.
--
Regards
Yu Zhiguo
> Thanks,
>
> Zhigang
prev parent reply other threads:[~2010-07-15 5:03 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
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 [this message]
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=4C3E9697.7070409@cn.fujitsu.com \
--to=yuzg@cn.fujitsu.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhigang.x.wang@oracle.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.