Date: Sat, 08 Nov 2014 09:57:12 -0800 From: Peter Grehan <grehan@freebsd.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: virtualization@freebsd.org Subject: Re: [current] bhyve under VMware borked? Message-ID: <545E5978.2010900@freebsd.org> In-Reply-To: <BA848416-08C3-4B23-8BBB-C7A293909318@xcllnt.net> References: <3054C397-B9F4-44A7-8D71-FF83CB058671@mac.com> <545D160E.7060208@freebsd.org> <BA848416-08C3-4B23-8BBB-C7A293909318@xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Marcel, >> What version of VMWare and host are you using ? > > This is VMware Fusion 6.0.5 (2209127) running on Mac OS X 10.10. Ok, looks like the problem still exists in the wild :( Fusion 7 doesn't have this issue so there's always the upgrade option :) > Ok. If we don't depend on PAT-related exits, then I definitely would > appreciate preserving the -stable behaviour. Maybe we should not check > for the PAT-related exists in the first place? I mean if we don't need > them or depend on them to be there at all... bhyve does depend on h/w save/restore of the PAT MSR, and this is the case for all bare metal that is supported. For the nested case, bhyve used to trap/emulate PAT MSR accesses and not propagate them to the host. I'll look at resurrecting that code. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?545E5978.2010900>