From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-stable@nongnu.org, Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH] target-i386: do not read/write MSR_TSC_AUX from KVM if CPUID bit is not set
Date: Thu, 31 Mar 2016 21:21:51 +0200 [thread overview]
Message-ID: <56FD78CF.4080201@kamp.de> (raw)
In-Reply-To: <56FD55BB.2010903@redhat.com>
Am 31.03.2016 um 18:52 schrieb Paolo Bonzini:
>
> On 31/03/2016 17:38, Peter Lieven wrote:
>>
>>> Am 31.03.2016 um 15:23 schrieb Paolo Bonzini <pbonzini@redhat.com>:
>>>
>>>
>>>
>>>> On 31/03/2016 15:12, Peter Lieven wrote:
>>>>>> KVM does not let you read or write this MSR if the corresponding CPUID
>>>>>> bit is not set. This in turn causes MSRs that come after MSR_TSC_AUX
>>>>>> to be ignored by KVM_SET_MRSS.
>>>> Is it possible that this causes a freeze when migrating vom qemu 2.2.0
>>>> to 2.5.1?
>>> I wouldn't exclude it if the CPU model is Westmere or earlier.
>> the Host CPU or the Emulated CPU?
> The guest.
I can confirm this seems to fix the migration for emulated Westmere CPUs. Regardless if its a 2.2.0 -> 2.5.1 or 2.5.1 -> 2.5.1
migration.
Peter
next prev parent reply other threads:[~2016-03-31 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 20:59 [Qemu-devel] [PATCH] target-i386: do not read/write MSR_TSC_AUX from KVM if CPUID bit is not set Paolo Bonzini
2016-03-31 12:56 ` Laszlo Ersek
2016-03-31 13:12 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2016-03-31 13:23 ` Paolo Bonzini
2016-03-31 15:38 ` Peter Lieven
2016-03-31 16:52 ` Paolo Bonzini
2016-03-31 19:21 ` Peter Lieven [this message]
2016-03-31 16:26 ` [Qemu-devel] " Eduardo Habkost
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=56FD78CF.4080201@kamp.de \
--to=pl@kamp.de \
--cc=ehabkost@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.