From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Help debugging a regression in KVM Module
Date: Fri, 14 Aug 2015 09:01:13 -0400 (EDT) [thread overview]
Message-ID: <1104465571.12477184.1439557273772.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <55CDCCE6.90102@kamp.de>
----- Original Message -----
> From: "Peter Lieven" <pl@kamp.de>
> To: qemu-devel@nongnu.org, kvm@vger.kernel.org
> Cc: "Paolo Bonzini" <pbonzini@redhat.com>
> Sent: Friday, August 14, 2015 1:11:34 PM
> Subject: Help debugging a regression in KVM Module
>
> Hi,
>
> some time a go I stumbled across a regression in the KVM Module that has been
> introduced somewhere
> between 3.17 and 3.19.
>
> I have a rather old openSUSE guest with an XFS filesystem which realiably
> crashes after some live migrations.
> I originally believed that the issue might be related to my setup with a 3.12
> host kernel and kvm-kmod 3.19,
> but I now found that it is also still present with a 3.19 host kernel with
> included 3.19 kvm module.
>
> My idea was to continue testing on a 3.12 host kernel and then bisect all
> commits to the kvm related parts.
>
> Now my question is how to best bisect only kvm related changes (those that go
> into kvm-kmod)?
I haven't forgotten this. Sorry. :(
Unfortunately I'll be away for three weeks, but I'll make it a priority
when I'm back.
Paolo
next prev parent reply other threads:[~2015-08-14 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 11:11 [Qemu-devel] Help debugging a regression in KVM Module Peter Lieven
2015-08-14 13:01 ` Paolo Bonzini [this message]
2015-08-14 19:36 ` Peter Lieven
2015-08-14 20:01 ` Alex Bennée
2015-08-17 12:33 ` Peter Lieven
2015-08-18 14:54 ` Peter Lieven
2015-08-18 15:25 ` Radim Krčmář
2015-08-18 15:37 ` Peter Lieven
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=1104465571.12477184.1439557273772.JavaMail.zimbra@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).