On Wed, Oct 2, 2013 at 11:47 AM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 02.10.2013 18:31, schrieb Stefan G. Weichinger: >> Am 02.10.2013 15:54, schrieb Kerin Millar: >> >>> Run "modinfo kvm kvm-amd" and check for discrepancies between the >>> details of the two, especially regarding the vermagic field. >> >> [...] >> >>> I would suggest "make mrproper" to clean the source tree. Ensure that >>> the .config has been backed up because it will be deleted as a result. >> >> I had no module "kvm" because one was built as module and one into the >> kernel. I now did mrproper and recompile both kvm and kvm_amd into the >> kernel. The next reboot will show ... > > Rather simple issue: > > I have a kernel in boot with the suffix -safe ... and this one got > listed first in grub.conf.
kerninst is pretty stupid. To create the list of kernels (in GRUB, not GRUB2), it simply lists the kernels in /boot, sorts them inverted by version, and then uses that order for the listing. Therefore, if you have: vmlinuz-3.9 vmlinuz-3.8 vmlinuz-3.10 vmlinuz-blah the inverted sort by version will be: vmlinuz-blah vmlinuz-3.10 vmlinuz-3.9 vmlinuz-3.8 and the kernel with an alphanumeric "version" will be always be the default. > kerninst found that one and always set that one as default so my various > recompilings never changed the kernel itself but only the modules ... > which lead to strange mismatches ... That should explain everything. As I said before, kerninst was not written to test configurations; is for when you have nailed the configuration and want to automatize the kernel update. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
