All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nick <oinksocket@letterboxes.org>
Cc: thomas@fjellstrom.ca, "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: kvm linux guest hanging for minutes at a time
Date: Thu, 11 Aug 2011 09:38:57 +0300	[thread overview]
Message-ID: <4E437901.9070207@redhat.com> (raw)
In-Reply-To: <4E41534F.1010502@letterboxes.org>

On 08/09/2011 06:33 PM, Nick wrote:
> Hi,
>
> Just joined this list, looking for leads to solve a similar-sounding problem
> (guest processes hanging for seconds or minutes when host IO load is high).
> I'll say more in a separate email, but I caught the end of this thread and
> wanted to ask about kvm-clock.
>
> Naively I'd have thought that using the wrong clock would not actually *cause*
> hangs like this. Or is that what you're implying?
>
>

Using the wrong clock easily causes hangs.  The system schedules a 
wakeup in 3 ms, wrong clock causes it to wakeup in 3 years, you get a 
hang for (3 years - 3 ms).

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2011-08-11  6:39 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
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 [this message]
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=4E437901.9070207@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=oinksocket@letterboxes.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 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.