From: Avi Kivity <avi@qumranet.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: KVM Test result, KVM62-RC2
Date: Tue, 26 Feb 2008 11:53:58 +0200 [thread overview]
Message-ID: <47C3E1B6.5000300@qumranet.com> (raw)
In-Reply-To: <200802261744.26259.sheng.yang@intel.com>
Yang, Sheng wrote:
>> One new issue:
>> 1. qcow based smp linux guests likely hang
>> https://sourceforge.net/tracker/index.php?func=detail&aid=1901980&group_
>> id=180599&atid=893831
>> We found the issue while booting qcow based rhel5.1 smp guest. It likely
>> hangs at the first booting. If using raw disk image, the problem will
>> not happen.
>>
>>
>
> This issue(i8254 don't connected to ioapic) happened from time to time on when
> I debug IOAPIC and PIT related things. I think it caused by guest kernel
> can't receive PIT interrupt in time. And I have done a experiment with in
> kernel PIT patch, and it works well to fix this issue.
>
> I guess this may due to qcow need some more time, and the accumulate time
> causing PIT interrupt delayed?
>
I think time calibration happens before any disk access by the kernel.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-26 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 9:20 KVM Test result, KVM62-RC2 Zhao, Yunfeng
2008-02-26 9:44 ` Yang, Sheng
2008-02-26 9:53 ` Avi Kivity [this message]
2008-02-26 11:58 ` Farkas Levente
2008-02-26 12:12 ` Izik Eidus
2008-02-26 13:11 ` Farkas Levente
2008-02-26 13:38 ` Farkas Levente
2008-02-27 4:53 ` Marcelo Tosatti
2008-02-27 10:12 ` Farkas Levente
2008-02-27 14:00 ` Marcelo Tosatti
2008-02-27 14:01 ` Avi Kivity
2008-02-27 14:22 ` david ahern
2008-03-01 14:05 ` 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=47C3E1B6.5000300@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=sheng.yang@intel.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.