From: Roland Dreier <rdreier@cisco.com>
To: "David Brown" <dmlb2000@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: KVM and rtc missing interupts 2.6.21-rc3
Date: Thu, 08 Mar 2007 13:57:21 -0800 [thread overview]
Message-ID: <adatzwvxuta.fsf@cisco.com> (raw)
In-Reply-To: <9c21eeae0703081348i713c996bked9ebe2af76bc2db@mail.gmail.com> (David Brown's message of "Thu, 8 Mar 2007 13:48:43 -0800")
> When ever I try and start a guest OS with kvm I get a lot of these rtc
> missing interupt messages from the kernel
>
> [ 468.510878] rtc: lost some interrupts at 1024Hz.
I started to debug this a little while ago but I never got too far.
However it doesn't seem connected with kvm -- it is something to do
with tun/tap or bridging holding a lock too long I think.
Try running your guest with -no-kvm (and even with the kvm module not
loaded, just to be sure). In my case I still saw the messages.
However, removing the "-net tap" line from my command line did get rid
of the messages.
- R.
next prev parent reply other threads:[~2007-03-08 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 21:48 KVM and rtc missing interupts 2.6.21-rc3 David Brown
2007-03-08 21:57 ` Roland Dreier [this message]
2007-03-09 0:47 ` David Brown
2007-03-09 3:19 ` Roland Dreier
2007-03-09 1:21 ` Lee Revell
2007-03-09 3:19 ` 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=adatzwvxuta.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=dmlb2000@gmail.com \
--cc=linux-kernel@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