From: Chris Friesen <chris.friesen@windriver.com>
To: "Han, Huaitong" <huaitong.han@intel.com>,
"hangaohuai@huawei.com" <hangaohuai@huawei.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"fangying1@huawei.com" <fangying1@huawei.com>,
"herongguang.he@huawei.com" <herongguang.he@huawei.com>,
"xudong.hao@linux.intel.com" <xudong.hao@linux.intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"wangxinxin.wang@huawei.com" <wangxinxin.wang@huawei.com>,
"kai.huang@linux.intel.com" <kai.huang@linux.intel.com>,
"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
"guangrong.xiao@linux.intel.com" <guangrong.xiao@linux.intel.com>
Subject: Re: [Qemu-devel] kvm bug in __rmap_clear_dirty during live migration
Date: Tue, 21 Feb 2017 21:08:04 -0600 [thread overview]
Message-ID: <58AD0094.90304@windriver.com> (raw)
In-Reply-To: <1487565495.3740.27.camel@intel.com>
On 02/19/2017 10:38 PM, Han, Huaitong wrote:
> Hi, Gaohuai
>
> I tried to debug the problem, and I found the indirect cause may be that
> the rmap value is not cleared when KVM mmu page is freed. I have read
> code without the root cause. Can you stable reproduce the the issue?
> Many guesses need to be verified.
In both cases it seems to have been triggered by repeatedly live-migrating a KVM
virtual machine between two hypervisors with Broadwell CPUs running the latest
CentOS 7.
It's a race of some sort, it doesn't happen every time.
Chris
next prev parent reply other threads:[~2017-02-22 3:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:37 kvm bug in __rmap_clear_dirty during live migration Herongguang (Stephen)
2017-02-09 14:37 ` [Qemu-devel] " Herongguang (Stephen)
2017-02-10 8:50 ` Herongguang (Stephen)
2017-02-10 8:50 ` [Qemu-devel] " Herongguang (Stephen)
2017-02-10 9:11 ` Herongguang (Stephen)
2017-02-10 9:11 ` [Qemu-devel] " Herongguang (Stephen)
2017-02-10 15:28 ` Chris Friesen
2017-02-10 15:28 ` [Qemu-devel] " Chris Friesen
2017-02-10 16:14 ` Paolo Bonzini
2017-02-10 16:14 ` [Qemu-devel] " Paolo Bonzini
2017-02-13 13:19 ` hangaohuai
2017-02-13 13:19 ` hangaohuai
2017-02-20 2:17 ` hangaohuai
2017-02-20 2:17 ` [Qemu-devel] " hangaohuai
2017-02-20 4:38 ` Han, Huaitong
2017-02-22 3:08 ` Chris Friesen [this message]
2017-02-22 11:15 ` Paolo Bonzini
2017-02-22 13:31 ` Chris Friesen
2017-02-22 14:43 ` Paolo Bonzini
2017-02-24 2:23 ` Herongguang (Stephen)
2017-02-24 2:23 ` Herongguang (Stephen)
2017-02-24 9:35 ` Herongguang (Stephen)
2017-02-24 9:35 ` Herongguang (Stephen)
2017-02-24 9:59 ` Greg KH
2017-02-24 10:00 ` Paolo Bonzini
2017-02-24 10:07 ` Greg KH
2017-02-24 10:07 ` [Qemu-devel] " Greg KH
2017-02-24 15:10 ` Chris Friesen
2017-02-24 15:10 ` Chris Friesen
2017-02-24 15:14 ` Paolo Bonzini
2017-02-24 15:14 ` [Qemu-devel] " Paolo Bonzini
2017-02-25 1:44 ` Herongguang (Stephen)
2017-02-25 1:44 ` Herongguang (Stephen)
2017-02-27 7:38 ` Huang, Kai
2017-02-27 7:38 ` [Qemu-devel] " Huang, Kai
2017-03-13 14:58 ` fangying
2017-03-13 14:58 ` fangying
2017-03-13 16:57 ` Paolo Bonzini
2017-03-16 1:40 ` Huang, Kai
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=58AD0094.90304@windriver.com \
--to=chris.friesen@windriver.com \
--cc=fangying1@huawei.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=hangaohuai@huawei.com \
--cc=herongguang.he@huawei.com \
--cc=huaitong.han@intel.com \
--cc=kai.huang@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=wangxinxin.wang@huawei.com \
--cc=xudong.hao@linux.intel.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.