qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Eduardo Habkost <ehabkost@redhat.com>, kvm <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] kvm: "warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]"
Date: Sat, 20 Feb 2016 04:00:30 -0500 (EST)	[thread overview]
Message-ID: <859622929.26459953.1455958830109.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <56C81F3C.4010006@web.de>



----- Original Message -----
> From: "Jan Kiszka" <jan.kiszka@web.de>
> To: "Eduardo Habkost" <ehabkost@redhat.com>, "Paolo Bonzini" <pbonzini@redhat.com>
> Cc: "qemu-devel" <qemu-devel@nongnu.org>, "kvm" <kvm@vger.kernel.org>
> Sent: Saturday, February 20, 2016 9:09:32 AM
> Subject: kvm: "warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]"
> 
> Hi all,
> 
> I suppose 5120901a37 introduced this: qemu with kernel_irqchip=off now
> generates these warnings, one per VCPU, during QEMU startup. Is the plan
> to live with them until we finally have x2APIC emulation in userspace
> (ie. also MSR vmexiting to there), or should we otherwise avoid it?

I think it's a bug, x2apic should be auto-suppressed with kernel_irqchip=off.

Paolo

  reply	other threads:[~2016-02-20  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  8:09 [Qemu-devel] kvm: "warning: host doesn't support requested feature: CPUID.01H:ECX.x2apic [bit 21]" Jan Kiszka
2016-02-20  9:00 ` Paolo Bonzini [this message]
2016-02-22 21:40   ` Eduardo Habkost
2016-02-25  8:33   ` Lan Tianyu
2016-02-25  8:39     ` Jan Kiszka
2016-02-25 12:31       ` Lan Tianyu

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=859622929.26459953.1455958830109.JavaMail.zimbra@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --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).