Date: Fri, 18 Jan 2019 15:06:40 +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-Q3vUp5qOpF@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 Rodney W. Grimes <rgrimes@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgrimes@FreeBSD.org --- Comment #4 from Rodney W. Grimes <rgrimes@FreeBSD.org> --- (In reply to Conrad Meyer from comment #2) Your correct in that bhyve does very little to hide CPUID bits of the host = from the guest and this has caused us these types of problems. This only gets w= orse with the addition of mitigation bits. What we need is a general mechanism to deal with this that would allow both masking and setting of any of the CPUID bits, something along the lines of (HOST & mask) | force for each of the cpuid values. This would even give us the ability to change processor model and type. IIRC this is how vmware implements the "create least common denominator" CP= Uid accross a cluster of servers so that you can do live migration. --=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-Q3vUp5qOpF>