P
PeterSteele
I'm doing some work with OpenVZ under CentOS and it's simple enough to install the OpenVZ kernel on an already installed system. In my case, I have a streamlined OS created via kickstart. The kickstart script installs the standard 6.4 kernel automatically as part of the options:
%packages --nobase
@core
To avoid installing the OpenVZ kernel after the OS install is complete (which requires an extra reboot), I want to install the OpenVZ kernel during kickstart instead of the standard CentOS kernel. There are two files that are required:
vzkernel-2.6.32-042stab090.4.x86_64.rpm
vzkernel-firmware-2.6.32-042stab090.4.noarch.rpm
These replace of course the eqivalent default kernel files. I'm not sure though how to tell kickstart to use these alternative kernel files instead of the ones that it installs by default. Is this something that can be done in kickstart? The attempts I've made so far result in the message "No kernel packages were installed on the system. Bootloader configuration will not be changed." This message is displayed just after the package install phase is complete. The install.log file shows that my kernel files were installed, but kickstart obviously didn't register them as kernel files.
So, what's the correct way to accomplish this?
Continue reading...
%packages --nobase
@core
To avoid installing the OpenVZ kernel after the OS install is complete (which requires an extra reboot), I want to install the OpenVZ kernel during kickstart instead of the standard CentOS kernel. There are two files that are required:
vzkernel-2.6.32-042stab090.4.x86_64.rpm
vzkernel-firmware-2.6.32-042stab090.4.noarch.rpm
These replace of course the eqivalent default kernel files. I'm not sure though how to tell kickstart to use these alternative kernel files instead of the ones that it installs by default. Is this something that can be done in kickstart? The attempts I've made so far result in the message "No kernel packages were installed on the system. Bootloader configuration will not be changed." This message is displayed just after the package install phase is complete. The install.log file shows that my kernel files were installed, but kickstart obviously didn't register them as kernel files.
So, what's the correct way to accomplish this?
Continue reading...
