Martin Lucina

@adamsteen Thanks for filing that. Is there some way I can get myself added to a Cc: list on that bug?

@adamsteen Any progress on this? I've not seen any traffic from `bugs@`. Perhaps ask on `tech@` instead?

Marking this as "help wanted" in the sense that its up for grabs for someone that needs the functionality. Current goals are concentrated on targets other than _virtio_.

To summarize some discussion I've already had with @Reperator and @Kensan elsewhere: From the Solo5 point of view, ease of _portability_, _isolation_ and a clear separation of concerns are important...

@Reperator: 1. Ok, so if I read you correctly, "DMA memory" is a global system resource. Presumably with system-wide limits, and so on. Sorry if this is obvious, but I'm...

@Reperator: OK, looking at how the VFIO mapping works it's just an `ioctl` on top of an `mmap`. So, I'd suggest starting with a minimal "strawman" PoC for `hvt` where,...

> @mato OpenBSD will not allow an mprotect call with both write and execute > enabled, W^X has been enforced at OS level since September 2016. I > initially hit...

@adamsteen: Thanks. So it looks like vmm is not updating EPT to match the `prot` from `mprotect()`. You know the OpenBSD vmm folks, could you please ping them and and...

Edit: Updated description with summary of status across back-ends and more information.

@mlarkin2015: > whatever you're using in Solo5 in userland to setup and launch the VM Just FYI, we don't use vmd(8), the userland part is the "solo5-hvt" tender which @adamsteen...