I ran "yum update" the other day on my dom0 and let it pull a new kernel. The RPM install scriptlet runs /sbin/new-kernel-pkg (part of the grubby package) to update grub.conf. It writes a new record to boot the Linux kernel instead of Xen. It would be nice if it noticed that it was running inside Xen and wrote a suitable record for that.
On 11/23/2013 12:07 PM, Kenneth Porter wrote:
I ran "yum update" the other day on my dom0 and let it pull a new kernel. The RPM install scriptlet runs /sbin/new-kernel-pkg (part of the grubby package) to update grub.conf. It writes a new record to boot the Linux kernel instead of Xen. It would be nice if it noticed that it was running inside Xen and wrote a suitable record for that.
We are aware of this issue and for now, you have to manually run /usr/bin/grub-bootxen.sh
We are also aware that the setup that grub-bootxen.sh provides is very basic and does not learn/keep custom settings.
This is something that we would love to receive community input to fix.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/24/2013 08:14 AM, Johnny Hughes wrote:
On 11/23/2013 12:07 PM, Kenneth Porter wrote:
I ran "yum update" the other day on my dom0 and let it pull a new kernel. The RPM install scriptlet runs /sbin/new-kernel-pkg (part of the grubby package) to update grub.conf. It writes a new record to boot the Linux kernel instead of Xen. It would be nice if it noticed that it was running inside Xen and wrote a suitable record for that.
We are aware of this issue and for now, you have to manually run /usr/bin/grub-bootxen.sh
We are also aware that the setup that grub-bootxen.sh provides is very basic and does not learn/keep custom settings.
This is something that we would love to receive community input to fix.
Modifying the spec file for the Xen kernel package to call an additional script in %post should be trivial, and since this kernel package doesn't come from upstream you should be free to do so.
The issue with using grubby is that grubby expects the kernel to be defined in the kernel line and the initrd in the initrd line. But with Xen boot entries both are defined in module lines instead. It shouldn't bee too difficult to eitehr write a new script that would work similar to grubby but looks at the module lines instead, or to modify grubby itself to do so.
Note that I (and I would think some others) like to have two boot entries for each new kernel. One that boots via the Xen hypervisor and a second that boots directly to the kernel itself, I would love to see such a script be able to copy both of these entries when installing a new kernel.
Peter
On 11/23/2013 03:22 PM, Peter wrote:
On 11/24/2013 08:14 AM, Johnny Hughes wrote:
On 11/23/2013 12:07 PM, Kenneth Porter wrote:
I ran "yum update" the other day on my dom0 and let it pull a new kernel. The RPM install scriptlet runs /sbin/new-kernel-pkg (part of the grubby package) to update grub.conf. It writes a new record to boot the Linux kernel instead of Xen. It would be nice if it noticed that it was running inside Xen and wrote a suitable record for that.
We are aware of this issue and for now, you have to manually run /usr/bin/grub-bootxen.sh
We are also aware that the setup that grub-bootxen.sh provides is very basic and does not learn/keep custom settings.
This is something that we would love to receive community input to fix.
Modifying the spec file for the Xen kernel package to call an additional script in %post should be trivial, and since this kernel package doesn't come from upstream you should be free to do so.
The issue with using grubby is that grubby expects the kernel to be defined in the kernel line and the initrd in the initrd line. But with Xen boot entries both are defined in module lines instead. It shouldn't bee too difficult to eitehr write a new script that would work similar to grubby but looks at the module lines instead, or to modify grubby itself to do so.
Note that I (and I would think some others) like to have two boot entries for each new kernel. One that boots via the Xen hypervisor and a second that boots directly to the kernel itself, I would love to see such a script be able to copy both of these entries when installing a new kernel.
The problem is, this kernel is not just installed on Dom0 machines ... so we need some way to know if this is or is not a Dom0 machine as well as to set the parameters.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/25/2013 02:51 AM, Johnny Hughes wrote:
The problem is, this kernel is not just installed on Dom0 machines ... so we need some way to know if this is or is not a Dom0 machine as well as to set the parameters.
Yes, I suppose it could be used in a domu, or even just as a regular bare-metal kernel by someone who wants a newer kernel but wants something a little bit more "official" than the elrepo kernel-ml (or kernel-lt). Perhaps the best approach would be to have the script available to run for the first time (as is currently the case), but for updates just check if the xen hypervisor is running, or even just check if a xen entry is in the grub.conf for the current kernel and if so put a new entry into grub.conf for xen.
Peter
-
Johnny Hughes -
Kenneth Porter -
Peter