WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] Don't attach needless options when launch pygrub

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Don't attach needless options when launch pygrub
From: Yu Zhiguo <yuzg@xxxxxxxxxxxxxx>
Date: Wed, 14 Jul 2010 15:29:25 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 14 Jul 2010 00:30:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1279090052.13417.16.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C3D55F8.9010303@xxxxxxxxxxxxxx> <1279090052.13417.16.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 3.0a1 (Windows/2008050715)
Hi Ian,

Ian Campbell wrote:
> On Wed, 2010-07-14 at 07:15 +0100, Yu Zhiguo wrote:
>> We should always run grub if bootloader is specified,
>> options 'kernel' and 'ramdisk' are needless.
> 
> Not quite. If you specify both bootloader and kernel then this instructs
> pygrub to extract the specific named file from the guest file system,
> similarly for the ramdisk.
> 

 Do you mean in this case, pygrub will use specified kernel
that lie in the filesystem of the DomU?

 I think this is good. But now pygrub's action is using the
specified kernel in Dom0, but not run grub.

> With your patch the functionality is still available using the
> bootloader_args field to add the "--kernel=FOO" yourself but I'm not
> sure it is a big enough issue to be worth changing. Is there some
> specific reason you don't like the current behaviour?

 Yes, all the bootloader_args will be attach to pygrub option......
 I think if bootloader is specified, omit kernel is simple.

> 
> In any case you seem to have forgotten to update the caller in
> tools/python/xen/xend/XendDomainInfo.py.
> 
 Oh, sorry for this mistake.

> I also have patches pending on the list from Monday which add bootloader
> functionality, including this behaviour, to libxl so if we decide to
> change it here it will need to change there as well.
> 

 OK, I'll try after patchs are applied.

Yu

> Ian.
> 
> 
>> Signed-off-by: Yu Zhiguo <yuzg@xxxxxxxxxxxxxx>
>>
>> diff -r d867eb643fe4 -r 38d9dac1de56 tools/python/xen/xend/XendBootloader.py
>> --- a/tools/python/xen/xend/XendBootloader.py        Tue Jul 13 18:17:28 
>> 2010 +0100
>> +++ b/tools/python/xen/xend/XendBootloader.py        Wed Jul 14 22:18:58 
>> 2010 +0800
>> @@ -24,8 +24,7 @@
>>  import pty, termios, fcntl
>>  from xen.lowlevel import ptsname
>>  
>> -def bootloader(blexec, disk, dom, quiet = False, blargs = '', kernel = '',
>> -               ramdisk = '', kernel_args = ''):
>> +def bootloader(blexec, disk, dom, quiet = False, blargs = '', kernel_args = 
>> ''):
>>      """Run the boot loader executable on the given disk and return a
>>      config image.
>>      @param blexec  Binary to use as the boot loader
>> @@ -96,10 +95,6 @@
>>      (child, m2) = pty.fork()
>>      if (not child):
>>          args = [ blexec ]
>> -        if kernel:
>> -            args.append("--kernel=%s" % kernel)
>> -        if ramdisk:
>> -            args.append("--ramdisk=%s" % ramdisk)
>>          if kernel_args:
>>              args.append("--args=%s" % kernel_args)
>>          if quiet:
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> 
> 
> 
> 


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