[current] bhyve under VMware borked?

t. -stable has a fallback that that -current doesn't have anymore. Any reason why the fallback was removed? Do we need PAT-related exit controls to make vmm work? Thanks, -- Marcel Moolenaar xcl...@mac.com ___ freebsd-virtualization@freebsd.o

Re: [current] bhyve under VMware borked?

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...@xclln

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 &

Re: [current] bhyve under VMware borked?

d 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 __

Re: bhyve: Support for QCOW2 image format

lready on the branch. Getting it hooked up with bhyve was my priority, but we’ve not crossed that hurdle yet… -- Marcel Moolenaar mar...@xcllnt.net signature.asc Description: Message signed with OpenPGP using GPGMail

Re: bhyve: Support for QCOW2 image format

> On Aug 19, 2015, at 10:55 AM, anup shendkar wrote: > > > On 18-Aug-2015 9:35 PM, "Marcel Moolenaar" <mailto:mar...@xcllnt.net>> wrote: > > > > > > > On Aug 18, 2015, at 2:51 AM, anup shendkar > > <mailto:anupshend...@gmail.com

Re: bhyve: Support for QCOW2 image format

support) and you get a kernel panic, boot the same kernel from a raw disk to see if it’s the kernel or the QCOW disk. Have fun! -- Marcel Moolenaar mar...@xcllnt.net signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [BHyVE] bhyverun.c:818:16: error: use of undeclared identifier 'VM_MEM_F_WIRED

ompile on FreeBSD-current. HTH, -- Marcel Moolenaar mar...@xcllnt.net <mailto:mar...@xcllnt.net> signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [BHyVE] bhyverun.c:818:16: error: use of undeclared identifier 'VM_MEM_F_WIRED

arget is in bsd.prog.mk or bd.lib.mk, so you should be able to run “make install” as root and things should get installed. > Thanks a lot for quick help Marcel. No problem. Have fun hacking :-) -- Marcel Moolenaar mar...@xcllnt.net <mailto:mar...@xcllnt.net> signature.asc Description: Message signed with OpenPGP using GPGMail

Re: bhyve, sparse disk image and trim support?

could be useful in general, not just raw disk images so I wanted to get off the ground with something like vmdk first... JFYI, -- Marcel Moolenaar mar...@xcllnt.net ___ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailm

[Differential] D9686: fix UEFI VM's bootup on Hyper-V (i.e. Hyper-V Generation-2 VM)

marcel added a comment. Going for the workaround I see! :-) INLINE COMMENTS > copy.c:56 > + int i, ndesc; > + unsigned long aviable_pages; > + It's spelled "available" instead of "aviable" :-) > copy.c:79-84 > + if (KERNEL_PHYSICAL_BASE < start || > + KER