All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Winkelmann <guido-kvml@thisisnotatest.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, Brian Jackson <iggy@theiggy.com>,
	kvm@vger.kernel.org
Subject: Re: I/O errors in guest OS after repeated migration
Date: Tue, 06 Nov 2012 12:07:30 +0100	[thread overview]
Message-ID: <2061347.nNjMkC6xtr@pc10> (raw)
In-Reply-To: <CAJSP0QWWVTZPWL7cPQCFMwoZOP-uPk0MU1g84NYvxGDsdcG32g@mail.gmail.com>

Am Montag, 29. Oktober 2012, 12:29:01 schrieb Stefan Hajnoczi:
> On Fri, Oct 19, 2012 at 2:55 PM, Guido Winkelmann
> <guido-kvml@thisisnotatest.de> wrote:
> > Am Donnerstag, 18. Oktober 2012, 18:05:39 schrieb Avi Kivity:
> >> On 10/18/2012 05:50 PM, Guido Winkelmann wrote:
> >> > Am Mittwoch, 17. Oktober 2012, 13:25:45 schrieb Brian Jackson:
> >> >> 
> >> >> What about newer versions of qemu/kvm? But of course if those work,
> >> >> your
> >> >> next task is going to be git bisect it or file a bug with your distro
> >> >> that
> >> >> is using an ancient version of qemu/kvm.
> >> > 
> >> > I've just upgraded both hosts to qemu-kvm 1.2.0
> >> > (qemu-1.2.0-14.fc17.x86_64,
> >> > built from spec files under
> >> > http://pkgs.fedoraproject.org/cgit/qemu.git/).
> >> > 
> >> > The bug is still there.
> >> 
> >> If you let the guest go idle (no I/O), then migrate it, then restart the
> >> I/O, do the errors show?
> > 
> > Just tested - yes, they do.
> 
> The -EIO error does not really reveal why there is a problem.  You can
> use SystemTap probes in QEMU to find out more about the nature of the
> error.
> 
> # stap -e 'probe qemu.kvm.bdrv_*, qemu.kvm.virtio_blk_*,
> qemu.kvm.paio_* { printf("%s(%s)\n", probefunc(), $$parms) }' -x
> $PID_OF_QEMU

This does not work for me. When I try running this, I'm getting many pages of 
errors like this:

======
# stap -e 'probe qemu.kvm.bdrv_*, qemu.kvm.virtio_blk_*, qemu.kvm.paio_* { 
printf("%s(%s)\n", probefunc(), $$parms) }' -x 1623
parse error: expected statement
        saw: keyword at /usr/share/systemtap/tapset/qemu-alpha.stp:1455:3
     source:   function = $arg3;
               ^
parse error: expected identifier
        saw: operator '=' at /usr/share/systemtap/tapset/qemu-
alpha.stp:1455:12
     source:   function = $arg3;
                        ^
2 parse errors.
======

Unfortunately, I don't know the first thing about systemtap, so I don't really 
know what's happening here...

	Guido

  reply	other threads:[~2012-11-06 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 16:33 I/O errors in guest OS after repeated migration Guido Winkelmann
2012-10-16 17:44 ` Brian Jackson
2012-10-17 11:54   ` Guido Winkelmann
2012-10-17 18:24     ` Brian Jackson
2012-10-17 15:45   ` Guido Winkelmann
2012-10-17 18:25     ` Brian Jackson
2012-10-18 15:50       ` Guido Winkelmann
2012-10-18 16:05         ` Avi Kivity
2012-10-19 12:55           ` Guido Winkelmann
2012-10-29 11:29             ` Stefan Hajnoczi
2012-11-06 11:07               ` Guido Winkelmann [this message]
2012-11-08  8:23                 ` Stefan Hajnoczi

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=2061347.nNjMkC6xtr@pc10 \
    --to=guido-kvml@thisisnotatest.de \
    --cc=avi@redhat.com \
    --cc=iggy@theiggy.com \
    --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 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.