Re: [current] bhyve under VMware borked?
Hi Marcel, On Fri, Nov 7, 2014 at 7:21 PM, Marcel Moolenaar wrote: > >>> On Nov 7, 2014, at 4:29 PM, Michael Dexter >>> 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: Have you selected "Enable hypervisor applications in this >> virtual machine" in the Processors: Advanced options settings? >> >> Michael > > Yes. Reverting the change Peter talked about fixed it for me. > There is now a proper fix for this in r279228. https://svnweb.freebsd.org/base?view=revision&revision=279228 best Neel > -- > Marcel (mobile) > ___ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to > "freebsd-virtualization-unsubscr...@freebsd.org" ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [current] bhyve under VMware borked?
> On Nov 8, 2014, at 9:57 AM, Peter Grehan 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 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. That would be great. As I said: stable/10 works just fine, BTW: Can you review the attached patch that moves disk support from bhyveload and bhyve into a new library called libvdsk. Once there, I plan to add support for VM image formats like vmdk, vhd, qcow, etc. For now, it's just moving the barebones support into the libary. Thanks, -- Marcel Moolenaar mar...@xcllnt.net libvdsk.diff Description: Binary data ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [current] bhyve under VMware borked?
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. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [current] bhyve under VMware borked?
>> On Nov 7, 2014, at 4:29 PM, Michael Dexter 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: Have you selected "Enable hypervisor applications in this > virtual machine" in the Processors: Advanced options settings? > > Michael Yes. Reverting the change Peter talked about fixed it for me. -- Marcel (mobile) ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [current] bhyve under VMware borked?
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: Have you selected "Enable hypervisor applications in this virtual machine" in the Processors: Advanced options settings? Michael ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [current] bhyve under VMware borked?
[Changing my email address...] > On Nov 7, 2014, at 10:57 AM, Peter Grehan 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 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 that it was no > longer an issue. > > 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... -- Marcel Moolenaar mar...@xcllnt.net ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
Re: [current] bhyve under VMware borked?
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 that it was no longer an issue. It's easy to put that change back. later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
