xen discuss - Jun 2008 - What is the correct method to add Xen kernel options to grub?

Hi,
I''ve been working with an snv_89 dom0 and solved some problems by
limiting dom0
memory and pinning the dom0 CPUs.  To do that, I had to manually edit
/boot/grub/menu.lst and add the following options to the appropriate
"kernel$" line:
dom0_mem=4G dom0_max_vcpus=2 dom0_vcpus_pin=true

Today I live-upgraded dom0 to snv_90, and my options were not preserved, which
is not surprising, as it says not to edit this file.  However, bootadm does not
have the capability to edit kernel options, so what is the appropriate method to
maintain my kernel options?  If it''s just to go in and add them back
after every
boot change, that''s fine, but I wondered if there''s a better
way.

Thanks,
Eric

Eric Sproul wrote:
> Hi,
> I''ve been working with an snv_89 dom0 and solved some problems by
limiting dom0
> memory and pinning the dom0 CPUs.  To do that, I had to manually edit
> /boot/grub/menu.lst and add the following options to the appropriate
"kernel$" line:
> dom0_mem=4G dom0_max_vcpus=2 dom0_vcpus_pin=true
> 
> Today I live-upgraded dom0 to snv_90, and my options were not preserved,
which
> is not surprising, as it says not to edit this file.  However, bootadm does
not
> have the capability to edit kernel options, so what is the appropriate
method to
> maintain my kernel options?  If it''s just to go in and add them
back after every
> boot change, that''s fine, but I wondered if there''s a
better way.
As of now, there''s no better way.

I would like to blow up the handling of eeprom, bootadm, and kernel 
options to allow setting more options and clean up some other things. 
But, I''m probably not going to have time to do that soon (if ever), so 
manually editing menu.lst is the only way for now.

-Ryan
> 
> Thanks,
> Eric
> _______________________________________________
> xen-discuss mailing list
> xen-discuss@opensolaris.org

Ryan Scott wrote:
> As of now, there''s no better way.
> 
> I would like to blow up the handling of eeprom, bootadm, and kernel
> options to allow setting more options and clean up some other things.
> But, I''m probably not going to have time to do that soon (if
ever), so
> manually editing menu.lst is the only way for now.
Heh, thanks Ryan, I understand.  I appreciate the quick response.

Cheers,
Eric

On Tue, Jun 10, 2008 at 01:28:05PM -0400, Eric Sproul wrote:
> I''ve been working with an snv_89 dom0 and solved some problems by
limiting dom0
> memory and pinning the dom0 CPUs.  To do that, I had to manually edit
> /boot/grub/menu.lst and add the following options to the appropriate
"kernel$" line:
> dom0_mem=4G dom0_max_vcpus=2 dom0_vcpus_pin=true
> 
> Today I live-upgraded dom0 to snv_90, and my options were not preserved,
which
> is not surprising, as it says not to edit this file.  However, bootadm does
not
> have the capability to edit kernel options, so what is the appropriate
method to
> maintain my kernel options?  If it''s just to go in and add them
back after every
> boot change, that''s fine, but I wondered if there''s a
better way.
You can do that, or you can create separate entries not inside "ADDED BY
BOOTADM - DO NOT EDIT" markers. I think they should always be left
alone.

BTW, if this is a significant problem for you, by all means file an RFE:
same applies to kernel arguments, as rscott mentioned.

regards
john