From: Paolo Bonzini <pbonzini@redhat.com>
To: Bug 1661386 <1661386@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1661386] Re: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed
Date: Mon, 6 Feb 2017 22:49:35 +0100 [thread overview]
Message-ID: <b7687a46-62d5-8d03-5766-844fef8abaa8@redhat.com> (raw)
In-Reply-To: <CAJs94EbfKZKVnR97-EuVfjMmhDhG=zwxGhdHGE_OjPCjLCXj2A@mail.gmail.com>
On 06/02/2017 20:38, Matwey V. Kornilov wrote:
>> OK, so that suggests the problem is that with PMU disabled in VMWare
>> config, it's not giving the right info to the guest to know it's
>> disabled.
> How should it provide info? Can we check it?
ver should have been 0 when PMU is disabled.
Can you run "x86info -a" in the host (the VMware guest)? Maybe it's not
a VMware bug. :)
Paolo
next prev parent reply other threads:[~2017-02-06 21:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 20:45 [Qemu-devel] [Bug 1661386] [NEW] Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed Matwey V. Kornilov
2017-02-03 12:57 ` [Qemu-devel] [Bug 1661386] " Dr. David Alan Gilbert
2017-02-03 16:25 ` Matwey V. Kornilov
2017-02-03 18:34 ` Dr. David Alan Gilbert
2017-02-03 18:55 ` Matwey V. Kornilov
2017-02-03 19:51 ` Dr. David Alan Gilbert
2017-02-05 8:58 ` Matwey V. Kornilov
2017-02-06 10:02 ` Dr. David Alan Gilbert
2017-02-06 16:54 ` Matwey V. Kornilov
2017-02-06 16:51 ` Matwey V. Kornilov
2017-02-06 17:11 ` Dr. David Alan Gilbert
2017-02-06 17:45 ` Matwey V. Kornilov
2017-02-06 17:31 ` Paolo Bonzini
2017-02-06 18:05 ` Dr. David Alan Gilbert
2017-02-06 19:38 ` Matwey V. Kornilov
2017-02-06 21:49 ` Paolo Bonzini [this message]
2017-02-07 15:50 ` Matwey V. Kornilov
2017-02-08 8:49 ` Paolo Bonzini
2017-07-23 9:54 ` Matwey V. Kornilov
2017-07-23 10:24 ` Matwey V. Kornilov
2017-02-08 13:14 ` Matwey V. Kornilov
2017-02-08 13:15 ` Matwey V. Kornilov
2017-04-07 13:26 ` Matwey V. Kornilov
2020-02-11 14:42 ` Thomas Huth
2020-02-11 15:43 ` Matwey V. Kornilov
2020-02-11 16:37 ` Thomas Huth
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=b7687a46-62d5-8d03-5766-844fef8abaa8@redhat.com \
--to=pbonzini@redhat.com \
--cc=1661386@bugs.launchpad.net \
--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).