* namespaced vsock @ 2024-06-05 14:57 Jakub Kicinski 2024-06-05 16:00 ` Stefano Garzarella 0 siblings, 1 reply; 4+ messages in thread From: Jakub Kicinski @ 2024-06-05 14:57 UTC (permalink / raw) To: Stefano Garzarella; +Cc: Stefan Hajnoczi, netdev@vger.kernel.org Hi Stefano! I found you patches from 2020 adding netns support to vsock. I got an internal ping from someone trying to run VMMs inside containers. Any plans on pushing that work forward? Is there a reason you stopped, or just EBUSY? ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: namespaced vsock 2024-06-05 14:57 namespaced vsock Jakub Kicinski @ 2024-06-05 16:00 ` Stefano Garzarella 2024-06-05 21:22 ` Jakub Kicinski 0 siblings, 1 reply; 4+ messages in thread From: Stefano Garzarella @ 2024-06-05 16:00 UTC (permalink / raw) To: Jakub Kicinski; +Cc: Stefan Hajnoczi, netdev@vger.kernel.org Hi Jakub, On Wed, Jun 05, 2024 at 07:57:44AM GMT, Jakub Kicinski wrote: >Hi Stefano! > >I found you patches from 2020 adding netns support to vsock. >I got an internal ping from someone trying to run VMMs inside >containers. Any plans on pushing that work forward? Is there >a reason you stopped, or just EBUSY? > IIRC nothing too difficult to solve, but as you guessed more EBUSY ;-) Maybe the more laborious one is somehow exporting a netdev interface into the guest to assign the device to a netns. But I hadn't tried to see if that was feasible yet. I have some notes here: https://gitlab.com/vsock/vsock/-/issues/2 I've been planning to take it up several times but haven't found time for now, if there's anyone interested I'm happy to share information and help with review and feedback. Otherwise I try to allocate some time, but I can't promise anything in the short term. Do you have time or anyone interested in continuing the work? Thanks, Stefano ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: namespaced vsock 2024-06-05 16:00 ` Stefano Garzarella @ 2024-06-05 21:22 ` Jakub Kicinski 2024-06-06 14:05 ` Stefano Garzarella 0 siblings, 1 reply; 4+ messages in thread From: Jakub Kicinski @ 2024-06-05 21:22 UTC (permalink / raw) To: Stefano Garzarella; +Cc: Stefan Hajnoczi, netdev@vger.kernel.org On Wed, 5 Jun 2024 18:00:25 +0200 Stefano Garzarella wrote: > On Wed, Jun 05, 2024 at 07:57:44AM GMT, Jakub Kicinski wrote: >> I found you patches from 2020 adding netns support to vsock. >> I got an internal ping from someone trying to run VMMs inside >> containers. Any plans on pushing that work forward? Is there >> a reason you stopped, or just EBUSY? > > IIRC nothing too difficult to solve, but as you guessed more EBUSY ;-) > > Maybe the more laborious one is somehow exporting a netdev interface > into the guest to assign the device to a netns. But I hadn't tried to > see if that was feasible yet. I have some notes here: > https://gitlab.com/vsock/vsock/-/issues/2 > > I've been planning to take it up several times but haven't found time > for now, if there's anyone interested I'm happy to share information and > help with review and feedback. Otherwise I try to allocate some time, > but I can't promise anything in the short term. Makes sense, thanks for the info! > Do you have time or anyone interested in continuing the work? Depending on the priority compared to other work, as usual :( There was a small chance you'd say "I'm planning to do it next month" and I wouldn't have to worry at all, so I thought I'd ask ;) ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: namespaced vsock 2024-06-05 21:22 ` Jakub Kicinski @ 2024-06-06 14:05 ` Stefano Garzarella 0 siblings, 0 replies; 4+ messages in thread From: Stefano Garzarella @ 2024-06-06 14:05 UTC (permalink / raw) To: Jakub Kicinski; +Cc: Stefan Hajnoczi, netdev@vger.kernel.org On Wed, Jun 05, 2024 at 02:22:52PM GMT, Jakub Kicinski wrote: >On Wed, 5 Jun 2024 18:00:25 +0200 Stefano Garzarella wrote: >> On Wed, Jun 05, 2024 at 07:57:44AM GMT, Jakub Kicinski wrote: >>> I found you patches from 2020 adding netns support to vsock. >>> I got an internal ping from someone trying to run VMMs inside >>> containers. Any plans on pushing that work forward? Is there >>> a reason you stopped, or just EBUSY? >> >> IIRC nothing too difficult to solve, but as you guessed more EBUSY ;-) >> >> Maybe the more laborious one is somehow exporting a netdev interface >> into the guest to assign the device to a netns. But I hadn't tried to >> see if that was feasible yet. I have some notes here: >> https://gitlab.com/vsock/vsock/-/issues/2 >> >> I've been planning to take it up several times but haven't found time >> for now, if there's anyone interested I'm happy to share information and >> help with review and feedback. Otherwise I try to allocate some time, >> but I can't promise anything in the short term. > >Makes sense, thanks for the info! > >> Do you have time or anyone interested in continuing the work? > >Depending on the priority compared to other work, as usual :( > >There was a small chance you'd say "I'm planning to do it next month" >and I wouldn't have to worry at all, so I thought I'd ask ;) > Yeah, I know :-) Let's keep updated if plans change! Stefano ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-06-06 14:05 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2024-06-05 14:57 namespaced vsock Jakub Kicinski 2024-06-05 16:00 ` Stefano Garzarella 2024-06-05 21:22 ` Jakub Kicinski 2024-06-06 14:05 ` Stefano Garzarella
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).