From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KVM on AMD ... why doesn't it just work?
Date: Wed, 2 Oct 2013 12:11:59 -0500 [thread overview]
Message-ID: <CADPrc82gCokyyjBr=dzbyxEexuZwPqf_WwJguZRT7vb7bk3SXg@mail.gmail.com> (raw)
In-Reply-To: <524C4E19.1030802@xunil.at>
On Wed, Oct 2, 2013 at 11:47 AM, Stefan G. Weichinger <lists@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
next prev parent reply other threads:[~2013-10-02 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 12:27 [gentoo-user] KVM on AMD ... why doesn't it just work? Stefan G. Weichinger
2013-10-02 12:38 ` Stefan G. Weichinger
2013-10-02 12:45 ` Stefan G. Weichinger
2013-10-02 17:26 ` Stefan G. Weichinger
2013-10-02 19:59 ` Stefan G. Weichinger
2013-10-02 13:54 ` Kerin Millar
2013-10-02 16:31 ` Stefan G. Weichinger
2013-10-02 16:47 ` Stefan G. Weichinger
2013-10-02 16:58 ` Kerin Millar
2013-10-02 17:11 ` Canek Peláez Valdés [this message]
2013-10-02 17:24 ` Stefan G. Weichinger
2013-10-02 18:51 ` Bruce Hill
2013-10-02 19:53 ` Stefan G. Weichinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADPrc82gCokyyjBr=dzbyxEexuZwPqf_WwJguZRT7vb7bk3SXg@mail.gmail.com' \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox