From: Avi Kivity <avi@qumranet.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: "kvm-devel@lists.sourceforge.net" <kvm@vger.kernel.org>
Subject: Re: mandrake-10 not able to boot on kvm-71-73
Date: Mon, 25 Aug 2008 19:36:15 +0300 [thread overview]
Message-ID: <48B2DF7F.7050107@qumranet.com> (raw)
In-Reply-To: <48B2DC6C.4000504@lfarkas.org>
Farkas Levente wrote:
> Avi Kivity wrote:
>
>> Farkas Levente wrote:
>>
>>> hi,
>>> mandrake-10 are not able to boot on kvm 71-73 while it's working on
>>> kvm-70. we noew try to install a minimal mandrake-10 from it's install
>>> cd and after the first boot it has the same error:
>>> lilo can't find keytable (or something like that).
>>> booting from a rescue cd we still able to rerun lilo and it seems to
>>> working, but not able to boot.
>>> after we downgrade to kvm-70 the system boot without any problem.
>>>
>>>
>>>
>> Can you mix and match to see whether it is a userspace problem or kernel
>> problem?
>>
>> e.g. kvm-71 userspace with kvm-70 modules, kvm-70 userspace with kvm-71
>> modules.
>>
>
> yes.
> kvm-73 with kmod-kvm-70: not working
> kvm-70 with kmod-kvm-73: working
>
So it's userspace breakage.
Can you check with kvm-71 userspace to be certain that the breakage
occured in kvm-71?
> is it totally safe to use higher kernel module then usersapce? i can i
> leave it here as it now?:
> kmod-kvm-2.6.18-92.1.10.el5-73-1
> kmod-kvm-73-1
> kvm-70-1
>
Yes. Of course mixed versions are not tested by many people, but they
are supported.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-25 16:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 14:43 mandrake-10 not able to boot on kvm-71-73 Farkas Levente
2008-08-25 16:02 ` Avi Kivity
2008-08-25 16:23 ` Farkas Levente
2008-08-25 16:36 ` Avi Kivity [this message]
2008-08-25 16:59 ` Farkas Levente
2008-08-26 7:06 ` Henrik Holst
2008-09-01 9:20 ` Farkas Levente
2008-09-01 9:28 ` Avi Kivity
2008-09-01 10:44 ` Farkas Levente
2008-09-10 17:13 ` Farkas Levente
2008-09-13 9:54 ` Avi Kivity
2008-09-13 12:57 ` Farkas Levente
2008-09-13 14:42 ` Avi Kivity
2008-09-15 15:12 ` Farkas Levente
2008-09-16 22:36 ` Avi Kivity
[not found] ` <48DBA59C.7090907@lfarkas.org>
[not found] ` <48E4B27D.10706@lfarkas.org>
2008-10-02 11:46 ` Avi Kivity
2008-10-02 14:08 ` Farkas Levente
2008-10-02 14:27 ` Avi Kivity
2008-10-02 17:06 ` Farkas Levente
[not found] ` <48E4FC9A.4060701@lfarkas.org>
2008-10-05 10:16 ` Farkas Levente
2008-10-05 10:36 ` Avi Kivity
2008-10-05 11:04 ` Farkas Levente
2008-10-05 11:06 ` Avi Kivity
2008-10-07 15:22 ` Farkas Levente
2008-10-15 12:19 ` Farkas Levente
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=48B2DF7F.7050107@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=lfarkas@lfarkas.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 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.