From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: trivial Makefile patch + problem report
Date: Wed, 29 Nov 2006 14:01:54 +0200 [thread overview]
Message-ID: <456D76B2.3040001@qumranet.com> (raw)
In-Reply-To: <aday7pvrw97.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Roland Dreier wrote:
> Hi, I've just installed kvm release 5 on systems with Intel Xeon 5160
> processors, running up-to-date git kernels (2.6.19-rc6).
>
> First, since I built my kernel with a separate object directory
> ("O=xxx"), I needed the patch below to the kernel module Kbuild file
> to get things to work (otherwise the build wouldn't find
> <linux/kvm.h>). As Documentation/kbuild/makefiles.txt says:
>
> $(src)
> $(src) is a relative path which points to the directory
> where the Makefile is located. Always use $(src) when
> referring to files located in the src tree.
>
>
Applied, thanks.
> Second, some of the time when starting a guest, I see a flood of
> messages like
>
> rtc: lost some interrupts at 1024Hz.
>
> flooding my kernel log, and almost always when that happens the system
> becomes unresponsive (although occasionally I'm able to kill the qemu
> process and restore the system).
>
> Is there any debugging information or other way I can help fix this
> issue?
>
>
You're using a Core (not 2) processor on a laptop, right?
There are two other reports about lost interrupts. One of them (hi
Christian) is a total lockup, the other is lost rtc interrupts like yours.
Does your machine like Xen?
I'll try to cook up an experimental patch to modify interrupt handling
to be more like Xen's.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-11-29 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 23:23 trivial Makefile patch + problem report Roland Dreier
[not found] ` <aday7pvrw97.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2006-11-28 23:28 ` Roland Dreier
[not found] ` <adau00jrw0g.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2006-11-29 12:03 ` Avi Kivity
2006-11-29 12:01 ` Avi Kivity [this message]
[not found] ` <456D76B2.3040001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-29 12:38 ` Avi Kivity
[not found] ` <456D7F4B.1000307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-11-29 16:06 ` Roland Dreier
2006-11-29 22:29 ` Roland Dreier
2006-11-29 22:38 ` Roland Dreier
[not found] ` <adavekxq3ou.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2006-11-30 8:29 ` Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E03216094CB09E-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2006-11-30 14:48 ` Roland Dreier
2006-11-29 15:30 ` Roland Dreier
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=456D76B2.3040001@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox