Date: Fri, 7 Nov 2014 12:50:13 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Peter Grehan <grehan@freebsd.org> Cc: virtualization@freebsd.org Subject: Re: [current] bhyve under VMware borked? Message-ID: <BA848416-08C3-4B23-8BBB-C7A293909318@xcllnt.net> In-Reply-To: <545D160E.7060208@freebsd.org> References: <3054C397-B9F4-44A7-8D71-FF83CB058671@mac.com> <545D160E.7060208@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[Changing my email address...] > On Nov 7, 2014, at 10:57 AM, Peter Grehan <grehan@freebsd.org> wrote: >=20 > Hi Marcel, >=20 > What version of VMWare and host are you using ? This is VMware Fusion 6.0.5 (2209127) running on Mac OS X 10.10. >=20 >> Any reason why the fallback was removed? Do we need PAT-related >> exit controls to make vmm work? >=20 > I saw the problem with a beta version of Fusion 5. It went away with = the release version, and we made the perhaps wrong assumption that it = was no longer an issue. >=20 > It's easy to put that change back. 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... --=20 Marcel Moolenaar marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA848416-08C3-4B23-8BBB-C7A293909318>