Hi Shawn,

Interesting. I'll have to do more digging. Because removing map_at_zero
support is the same as keeping it at the default of 0. It's not possible
that our ASLR implementation is affecting bhyve, since our ASLR
implementation is in sys_mmap and the elf image activator. At this
stage, bhyve's vmm.ko is directly accessing vm_map_*, which we haven't

One thing you may be able to try is ktrace the bhyveload process and see which syscall is failing.



freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to