Re: [current] bhyve under VMware borked?

2015-02-23 Thread Neel Natu
Hi Marcel, On Fri, Nov 7, 2014 at 7:21 PM, Marcel Moolenaar mar...@xcllnt.net wrote: On Nov 7, 2014, at 4:29 PM, Michael Dexter edi...@callfortesting.org wrote: On 11/7/14 12:50 PM, Marcel Moolenaar wrote: This is VMware Fusion 6.0.5 (2209127) running on Mac OS X 10.10. Just in case:

Re: [current] bhyve under VMware borked?

2014-11-08 Thread Marcel Moolenaar
On Nov 8, 2014, at 9:57 AM, Peter Grehan gre...@freebsd.org wrote: Fusion 7 doesn't have this issue so there's always the upgrade option :) Good to know. Ok. If we don't depend on PAT-related exits, then I definitely would appreciate preserving the -stable behaviour. Maybe we should not

[current] bhyve under VMware borked?

2014-11-07 Thread Marcel Moolenaar
All, With FreeBSD-current I can't load vmm.ko when running FreeBSD under VMware. I get: vmx_init: processor does not support desired exit controls module_register_init: MOD_LOAD (vmm, 0x81014130, 0) error 22 There's a distinct change between -stable and -current in this respect. -stable

Re: [current] bhyve under VMware borked?

2014-11-07 Thread Peter Grehan
Hi Marcel, What version of VMWare and host are you using ? Any reason why the fallback was removed? Do we need PAT-related exit controls to make vmm work? 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

Re: [current] bhyve under VMware borked?

2014-11-07 Thread Marcel Moolenaar
[Changing my email address...] On Nov 7, 2014, at 10:57 AM, Peter Grehan gre...@freebsd.org wrote: 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. Any reason why the fallback was removed? Do we need