From: Jan Kiszka <jan.kiszka@siemens.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: KVM mailing list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: KVM-kmod upstream built on a fully updated F12 box cannot be loaded
Date: Fri, 05 Feb 2010 11:21:28 +0100 [thread overview]
Message-ID: <4B6BF128.8050104@siemens.com> (raw)
In-Reply-To: <1265365056.2407.0.camel@localhost.localdomain>
Lucas Meneghel Rodrigues wrote:
> On Fri, 2010-02-05 at 10:25 +0100, Jan Kiszka wrote:
>> Lucas Meneghel Rodrigues wrote:
>>> Hi folks:
>>>
>>> Today's upstream test couldn't go further due to a problem trying to
>>> load the module built with kvm-kmod:
>>>
>>> TestFail: Failed to load KVM modules: Command <insmod /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/kvm.ko> failed, rc=1, Command returned non-zero exit status
>>> * Command:
>>> insmod /usr/local/autotest/tests/kvm/src/kvm_kmod/x86/kvm.ko
>>> Exit status: 1
>>> Duration: 0
>>>
>>> stderr:
>>> insmod: error inserting '/usr/local/autotest/tests/kvm/src/kvm_kmod/x86/kvm.ko': -1 Unknown symbol in module
>> Having the kernel log here would be more helpful. But I bet you are
>> bitten by the issue that breaks kvm-kmod builds against 2.6.32 and older
>> since this night: http://buildbot.kiszka.org/kvm-kmod/waterfall
>
> Yes, sorry, forgot to post dmesg here:
>
> kvm: Unknown symbol getboottime
> kvm: Unknown symbol monotonic_to_bootbased
Those two are addressed in next already (with a big-fat warning to not
suspend your host if they are missing), will push this into master now.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-02-05 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1265326179.2330.4.camel@localhost.localdomain>
2010-02-05 9:25 ` KVM-kmod upstream built on a fully updated F12 box cannot be loaded Jan Kiszka
2010-02-05 10:17 ` Lucas Meneghel Rodrigues
2010-02-05 10:21 ` Jan Kiszka [this message]
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=4B6BF128.8050104@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mtosatti@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.