public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hermann Himmelbauer <dusty@qwer.tk>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Disk I/O stuck with KVM - no clue how to solve that
Date: Sun, 7 Nov 2010 17:07:51 +0100	[thread overview]
Message-ID: <201011071707.51508.dusty@qwer.tk> (raw)
In-Reply-To: <AANLkTi=pmdikqbLFckpUts1Jhxd=a-2wQS8v-D-Wf5rt@mail.gmail.com>

Am Samstag 06 November 2010 20:58:12 schrieb Stefan Hajnoczi:
> On Fri, Nov 5, 2010 at 5:16 PM, Hermann Himmelbauer <dusty@qwer.tk> wrote:
> > I experience strange disk I/O stucks on my Linux Host + Guest with KVM,
> > which make the system (especially the guests) almost unusable. These
> > stucks come periodically, e.g. every 2 to 10 seconds and last between 3
> > and sometimes over 120 seconds, which trigger kernel messages like this
> > (on host and/or guest):
> >
> > INFO: task postgres:2195 blocked for more than 120 seconds
>
> The fact that this happens on the host too suggests there's an issue
> with the host software/hardware and the VM is triggering it but not
> the root cause.
>
> Does dmesg display any other suspicious messages?

No, there's anything that can be seen via dmesg. I at first suspected the 
hardware, too. I can think of the following reasons:

1) Broken SATA cable / Harddisks - I changed some cables, no change, thus this 
is probably ruled out. I also can't see anything via S.M.A.R.T. Moreover, the 
problem is not bound to a specific device, instead it happens on sda - sdd, 
so I doubt it's harddisk related.

2) Broken Power Supply / Insufficient Power - I'd expect either a complete 
crash or some error messages in this case, so I'd rather rule that out.

3) Broken SATA-Controller - I cannot think of any way to check that, but I'd 
also expect some crashes or kernel messages. I flashed the board to the 
latest BIOS version, no change either.

However, it seems no one except me seems to have this problem, so I'll buy a 
new, similar but different mainboard (Intel instead of Asus), hopefully this 
solves the problem.

What do you think, any better idea?

Anyway, thanks for your reply!

Best Regards,
Hermann

-- 
hermann@qwer.tk
GPG key ID: 299893C7 (on keyservers)
FP: 0124 2584 8809 EF2A DBF9  4902 64B4 D16B 2998 93C7

  reply	other threads:[~2010-11-07 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 17:16 Disk I/O stuck with KVM - no clue how to solve that Hermann Himmelbauer
2010-11-06 19:58 ` Stefan Hajnoczi
2010-11-07 16:07   ` Hermann Himmelbauer [this message]
2010-11-08  6:32     ` Stefan Hajnoczi
2010-11-08 14:05       ` Hermann Himmelbauer

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=201011071707.51508.dusty@qwer.tk \
    --to=dusty@qwer.tk \
    --cc=kvm@vger.kernel.org \
    --cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox