[CentOS-virt] Automate running grub-bootxen.sh for kernel installs in Xen4CentOS
rgritzo
rgritzo at gmail.com
Fri Oct 3 15:33:11 UTC 2014
although i am very new to the xen project, this approach makes good sense to me.
consistent with the use of files within /etc/sysconfig and very predictable and sensible behavior.
also seems like it is a good base to build from when adding future features.
is it ready yet :}
r.
> We need a way to do two things to /usr/bin/grub-bootxen.sh in Xen4CentOS.
>
> 1. Automate running it if xen (the package) and the xen kernel are
> installed. But only if the user WANTS to run it.
>
> 2. Allow users to automatically modify the variables passed into the
> xen.gz line (that is, more or less memory, add console settings, etc.)
> If you look at the current script, "--mbargs=dom0_mem=1024M,max:1024M
> loglvl=all guest_loglvl=all" is hard coded in as the only option for the
> xen.gz line.
>
> While doing that we also still want to preserve the ability to run that
> kernel in other places than just for xen dom0 setups.
>
> Here is how I propose we do that.
>
> Currently the /usr/bin/grub-bootxen.sh file is in centos-release-xen ...
> that is a good place as it allows us to use a different file in
> different major versions of CentOS (so the file in 7 can be different
> than the file in 6, but still use the same auxiliary files, etc).
>
> So, what we can do is setup a file in /etc/sysconfig/ (probably from the
> xen package) that we call xen-boot or xen-kernel, etc. In this file we
> put some variables like these:
--
/*************************************************************************/
Russ Gritzo email: rgritzo at gmail.com
/usr/games/gfortune:
I know engineers. They love to change things.
- Dr. McCoy
/**************************************************************************/
More information about the CentOS-virt
mailing list