From: Ben Hutchings <ben@decadent.org.uk>
To: Eric Wheeler <kvm@lists.ewheeler.net>, kvm@vger.kernel.org
Cc: stable@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Haozhong Zhang" <haozhong.zhang@intel.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Gleb Natapov" <gleb@kernel.org>
Subject: Re: [BISECT 4.1.y] [PATCH] regression: kvm: migration hangs guest
Date: Mon, 06 Mar 2017 19:11:36 +0000 [thread overview]
Message-ID: <1488827496.2953.15.camel@decadent.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.11.1701251535220.13235@mail.ewheeler.net>
[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]
On Wed, 2017-01-25 at 15:50 -0800, Eric Wheeler wrote:
> Hello All,
>
> We discovered guests hanging when using the 4.1.y kernel after 4.1.16 with
> live migration after CentOS applied this patch to the latest version of
> qemu-kvm user space:
> https://git.centos.org/blob/rpms!!qemu-kvm.git/34b32196890e2c41b0aee042e600ba422f29db17/SOURCES!kvm-target-i386-get-put-MSR_TSC_AUX-across-reset-and-mig.patch
>
> Please also see this Bugzilla entry:
> https://bugzilla.redhat.com/show_bug.cgi?id=1408333
>
> After a bisect, We found this commit to be causing the hang:
> 8a3185c54d650a86dafc8d8bcafa124b50944315 KVM: x86: expose MSR_TSC_AUX to userspace
>
> It turns out that this is not actually the problem, but rather these
> commits need to be pulled in as well to support the 8a31 commit:
> 609e36d372a KVM: x86: pass host_initiated to functions that read MSRs
> 81b1b9ca6d5 KVM: VMX: Fix host initiated access to guest MSR_TSC_AUX
>
> Thus, we need to either:
> 1. Revert commit 8a3185c54d650a86dafc8d8bcafa124b50944315
> - or -
> 2. Merge commits 609e36d372a and 81b1b9ca6d5 into 4.1.y.
>
> If you choose the latter options, then please see below for the backport
> patch of 81b1b9ca6d5 (609e36d372a cherry-picks just fine).
>
> What do you believe would be best?
For 3.2 and 3.16, I will revert the change. Thanks for tracking this down.
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-03-06 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 23:50 [BISECT 4.1.y] [PATCH] regression: kvm: migration hangs guest Eric Wheeler
2017-01-25 23:58 ` Paolo Bonzini
2017-01-26 23:29 ` Eric Wheeler
2017-01-27 6:21 ` Philipp Hahn
2017-02-09 21:34 ` Eric Wheeler
2017-02-15 18:36 ` Eric Wheeler
2017-03-06 19:11 ` Ben Hutchings [this message]
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=1488827496.2953.15.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=gleb@kernel.org \
--cc=haozhong.zhang@intel.com \
--cc=kvm@lists.ewheeler.net \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.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 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.