From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1837851] Re: hv-tlbflush malfunctions on Intel host CPUs with neither EPT nor VPID (qemu-kvm)
Date: Wed, 31 Jul 2019 09:25:20 -0000 [thread overview]
Message-ID: <156456512042.6843.12889194640468618584.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 156404155054.10633.9207967667458929652.malonedeb@wampee.canonical.com
** Tags added: kvm x86
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1837851
Title:
hv-tlbflush malfunctions on Intel host CPUs with neither EPT nor VPID
(qemu-kvm)
Status in QEMU:
New
Bug description:
Enabling hv-tlbflush on older hosts using Intel CPUs supporting VT-x
but neither EPT nor VPID will lead to bluescreens on the guest.
It seems KVM only checks if EPT is available, and if it isn't it
forcibly uses VPID. If that's *also* not available, it defaults to
basically a no-op hypercall, though windows is expecting the TLB to be
flushed.
hv-tlbflush is pretty useless on machines not supporting these
extensions anyway (only reasonably fix I can see would be to flush the
*entire* TLB on tlbflush hypercall in KVM (i.e. a kernel fix), but
that would remove any performance benefits), so I would suggest some
kind of preliminary check and warning/error if hv-tlbflush is
specified on such a host.
All CPUs mentioned in this thread[0] are confirmed to be affected by
the bug, and I have successfully reproduced it on an Intel Core2Duo
E8500.
[0] https://forum.proxmox.com/threads/windows-guest-bluescreen-with-
proxmox-6.56053/
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1837851/+subscriptions
next prev parent reply other threads:[~2019-07-31 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 7:59 [Qemu-devel] [Bug 1837851] [NEW] hv-tlbflush malfunctions on Intel host CPUs with neither EPT nor VPID (qemu-kvm) Stefan
2019-07-31 9:25 ` Alex Bennée [this message]
2021-04-22 7:09 ` [Bug 1837851] " Thomas Huth
2021-06-22 4:18 ` Launchpad Bug Tracker
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=156456512042.6843.12889194640468618584.launchpad@soybean.canonical.com \
--to=alex.bennee@linaro.org \
--cc=1837851@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).