From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM Test result, kernel 5ed4995.., userspace e44dce6..
Date: Mon, 07 Jan 2008 12:18:57 +0200 [thread overview]
Message-ID: <4781FC91.40309@qumranet.com> (raw)
In-Reply-To: <200801071812.05892.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Yang, Sheng wrote:
> On Monday 07 January 2008 17:51:36 Avi Kivity wrote:
>
>> Farkas Levente wrote:
>>
>>> Zhao, Yunfeng wrote:
>>>
>>>> Hi, all,
>>>>
>>>> This is today's KVM test result against kvm.git
>>>> 5ed49953ef3749de1198bc07cdf11339d8f74432 and kvm-userspace.git
>>>> e44dce6b8c8c8cf155223ba0e036bb4ace5071b1.
>>>>
>>>> 4. Cannot boot 32bit smp RHEL5.1 guest with nic on 64bit host
>>>> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1812043&gro
>>>> up_id=180599
>>>>
>>> is there any progress with this?
>>>
>> It's a toughie. We know which guest kernel change caused the hang, but
>> we are still some way off from understanding it and fixing it.
>>
>
> I am beginning to look into this recently, but not many clues... Seems like
> interrupt problem. The guest was executing "mov 0xffffd0b0, 0"(set EOI) all
> the time after it hung.
>
>
For reference, the trouble ends at commit
95492e4646e5de8b43d9a7908d6177fb737b61f0. Guest kernels before that
commit will hang; guest kernels at the commit or later are fine.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-07 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 9:24 KVM Test result, kernel 5ed4995.., userspace e44dce6 Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A029B5DA4-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-07 9:48 ` Farkas Levente
[not found] ` <4781F586.5060700-lWVWdrzSO4GHXe+LvDLADg@public.gmane.org>
2008-01-07 9:51 ` Avi Kivity
[not found] ` <4781F628.9040107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-07 10:12 ` Yang, Sheng
[not found] ` <200801071812.05892.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2008-01-07 10:18 ` Avi Kivity [this message]
2008-01-07 9:54 ` Izik Eidus
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=4781FC91.40309@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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.