From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] cpu.fail / MDS fixes
Date: Wed, 15 May 2019 18:54:31 +0100 [thread overview]
Message-ID: <20190515175431.GM4751@redhat.com> (raw)
In-Reply-To: <7c80a63c-a7ce-1e83-650b-0b8343563127@profihost.ag>
On Wed, May 15, 2019 at 07:13:56PM +0200, Stefan Priebe - Profihost AG wrote:
> Hello list,
>
> i've updated my host to kernel 4.19.43 and applied the following patch
> to my qemu 2.12.1:
> https://bugzilla.suse.com/attachment.cgi?id=798722
>
> But my guest running 4.19.43 still says:
> Vulnerable: Clear CPU buffers attempted, no microcode; SMT Host state
> unknown
>
> while the host says:
> Vulnerable: Clear CPU buffers attempted, SMT Host state unknown
That suggests your host OS hasn't got the new microcode installed
or has not loaded it.
You want the host to report that it is Mitigated, and for the
host's /proc/cpuinfo to report "md-clear" exists.
> I expected the guest can use the new microcode.
You've not said what CPU model you've given to the guest.
You need either "-cpu host", or if using a named CPU model
you need to explicitly turn on the "md-clear" feature
(and all previous fixes)
eg "-cpu Haswell,+spec-ctrl,+ssbd,+md-clear"
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-15 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 17:13 [Qemu-devel] cpu.fail / MDS fixes Stefan Priebe - Profihost AG
2019-05-15 17:54 ` Daniel P. Berrangé [this message]
2019-05-15 19:24 ` Stefan Priebe - Profihost AG
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=20190515175431.GM4751@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
/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.