Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Jan 2019 23:35:37 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 235010] bhyve: Linux guest crash due to unhandled MSR
Message-ID:  <bug-235010-27103-ECTOW4wWDh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-235010-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-235010-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235010

--- Comment #2 from Conrad Meyer <cem@freebsd.org> ---
This seems to be a good summary:

https://lkml.org/lkml/2019/1/9/448

We might be passing through CPUID bits that we should not be to the guest, =
at
least not without adding that MSR to our emulation list.

I'm not sure how we handle spectre/meltdown representations to guests on In=
tel.

I don't think guests should be able to set these MSRs and they probably
shouldn't do software mitigation -- it's up to the host to correct mitigate=
.=20
So maybe we should set whatever bit claims immunity to spectre/meltdown in
guest cpuid.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235010-27103-ECTOW4wWDh>