public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: thomas@fjellstrom.ca
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: kvm linux guest hanging for minutes at a time
Date: Tue, 09 Aug 2011 17:37:09 +0300	[thread overview]
Message-ID: <4E414615.8030201@redhat.com> (raw)
In-Reply-To: <201108090831.48423.thomas@fjellstrom.ca>

On 08/09/2011 05:31 PM, Thomas Fjellstrom wrote:
> On August 9, 2011, Avi Kivity wrote:
> >  On 08/09/2011 03:03 PM, Thomas Fjellstrom wrote:
> >  >  >   Your guest isn't using kvmclock for some reason.  Is it compiled in
> >  >  >   the guest kernel?  What are the contents of
> >  >  >   /sys/devices/system/clocksource/clocksource0/available_clocksource and
> >  >  >   /sys/devices/system/clocksource/clocksource0/current_clocksource (in
> >  >  >   the guest filesystem)?
> >  >
> >  >  Hi, it seems it is using kvm-clock:
> >  >
> >  >  $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> >  >  kvm-clock hpet acpi_pm
> >  >  $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
> >  >  kvm-clock
> >
> >  Yikes.  Please trace such a hang according to
> >  http://www.linux-kvm.org/page/Tracing.
>
> Does it matter that I have several vms running? Is there a way to limit it to
> tracing the single kvm process that's been locking up?
>

You can use "trace-cmd record -F ... qemu ..." but that misses out on 
events the run from workqueues.

Best to stop those other guests.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-08-09 14:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 14:06 kvm linux guest hanging for minutes at a time Thomas Fjellstrom
2011-08-09  9:16 ` Avi Kivity
2011-08-09 12:03   ` Thomas Fjellstrom
2011-08-09 12:36     ` Avi Kivity
2011-08-09 14:31       ` Thomas Fjellstrom
2011-08-09 14:37         ` Avi Kivity [this message]
2011-08-09 14:46           ` Thomas Fjellstrom
2011-08-09 14:49             ` Avi Kivity
2011-08-09 14:54               ` Thomas Fjellstrom
2011-08-09 15:01               ` Thomas Fjellstrom
2011-08-10 15:03             ` Philipp Hahn
2011-08-09 15:33           ` Nick
2011-08-11  6:38             ` Avi Kivity
2011-08-11 16:37               ` Thomas Fjellstrom

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=4E414615.8030201@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=thomas@fjellstrom.ca \
    /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