From: Farkas Levente <lfarkas@lfarkas.org>
To: Avi Kivity <avi@qumranet.com>
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 18:59:45 +0200 [thread overview]
Message-ID: <48B2E501.6060604@lfarkas.org> (raw)
In-Reply-To: <48B2DF7F.7050107@qumranet.com>
Avi Kivity wrote:
> 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?
no it's between 71 and 72 (i'm just not used 71 since it kmod not
compiled on rhel-5.2).
the situation is more stranger (but probably another bug)
kvm-70 (and kvm-71) with kmod-kvm-73: working if and only if i start
mandrake-10 as the first guest, if i start other guest and after i start
mandrake-10 (both from command line and virt-manager) i've got this (not
too long) error:
-----------------------------------------------------
# /usr/bin/qemu-kvm -S -M pc -m 512 -smp 1 -name mandrake-10 -monitor
pty -boot c -drive
file=/dev/VolGroup00/mandrake-10,if=ide,index=0,boot=on -net
nic,macaddr=00:16:3e:03:37:eb,vlan=0 -net
tap,fd=20,script=,vlan=0,ifname=vnet3 -serial none -parallel none -usb
-vnc 127.0.0.1:0
bind() failed
-----------------------------------------------------
if i stop all other guest and start mandrake-10 again then it's work
again?! but it's another problem and seems to exist in kvm-70 too.
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2008-08-25 16:59 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
2008-08-25 16:59 ` Farkas Levente [this message]
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=48B2E501.6060604@lfarkas.org \
--to=lfarkas@lfarkas.org \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).