Greg,
OSv cannot run natively in Nitro instances (see
https://github.com/cloudius-systems/osv/issues/924).
I am not sure I understand enclaves well but can they be used across i3
(other "bare metal") instances and help communicate between OSv instances
running under Firecracker on those? Woul
With the introduction of Enclave instances which communicate via vsock and
the security benefits of OSv/unikernel approach maybe this issue will
warrant more attention as the two seem made for one another (OSv and
Enclaves). Any ideas? This is on Nitro instances, I forget if OSv
supports Nitro ye
On Mon, Oct 26, 2020 at 4:50 AM David Smith wrote:
> Waldek,
>
> many thanks for your detailed reply and I certainly understand the
> bandwidth issues. Unfortunately, I also have no bandwidth, plus I am not
> experienced working in the Linux kernel, so the level of effort for me to
> attempt this
Waldek,
many thanks for your detailed reply and I certainly understand the
bandwidth issues. Unfortunately, I also have no bandwidth, plus I am not
experienced working in the Linux kernel, so the level of effort for me to
attempt this would be higher. To answer your question, in my particular
Base on page 26 in this slide
-
https://static.sched.com/hosted_files/kvmforum2019/50/KVMForum_2019_virtio_vsock_Andra_Paraschiv_Stefano_Garzarella_v1.3.pdf,
it looks like there is a plan to use virtio-net device a transport for
vsock. That would help us a lot, I guess.
Does anyone have any m
Hi,
Unfortunately, I do not have any bandwidth to work on it now (maybe in a
couple of months). So we are looking for volunteers to help us with it. Are
you interested?
As the mailing group conversation linked to #1069 indicates, adding vsock
support would require implementing virtio socket de
