All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: smp guest questions
Date: Wed, 17 Jun 2009 12:15:42 +0300	[thread overview]
Message-ID: <4A38B43E.6010704@redhat.com> (raw)
In-Reply-To: <4A38ABA3.2010401@msgid.tls.msk.ru>

On 06/17/2009 11:38 AM, Michael Tokarev wrote:
> After seeing words from Avi about that smp guests
> are ok now, I descided to try.  And immediately
> got a few questions.
>
> Running on a Phenom 9750 machine (PhenomI), AMD780G
> chipset.  Host is 2.6.29 x86-64, qemu-kvm 0.10.5,
> guests are linux with kvm paravirt bits enabled, also
> dynticks (on both host and guest).
>
>
> When booting a 2-CPU guest, I see in dmesg:
>
> PM-Timer running at invalid rate: 200% of normal - aborting.
>
> and indeed, in available_clocksource there's no pmtimer.
> Should I be concerned?  It does not look healthy.
>

It's a bug, please post guest details (kernel version, bitness).

Copying Marcelo.

>
> Some time later, I see stuff like:
>
> hrtimer: interrupt too slow, forcing clock min delta to 47210997 ns
>
> Which reminds me issues I had with broken hpet (time goes
> back-n-forth with similar messages shown in dmesg, but
> about hpet not hrtimer).  Also does not look healthy.
>
>
> I haven't seen either of the two messages above on any of
> single-processor guests so far, at least with recent kernels
> and kvm userspace, only on smp (2 cpu for now).

Please also post host /proc/cpuifo.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2009-06-17  9:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-17  8:38 smp guest questions Michael Tokarev
2009-06-17  9:15 ` Avi Kivity [this message]
2009-06-17 10:46   ` Michael Tokarev
2009-06-18  9:14     ` Michael Tokarev
2009-06-18 15:17     ` Marcelo Tosatti

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=4A38B43E.6010704@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.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.