Message ID | 20200515152110.202917-1-sgarzare@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | virtio: add vhost-user-vsock device | expand |
On Fri, May 15, 2020 at 05:21:07PM +0200, Stefano Garzarella wrote: > This series add vhost-user-vsock base device and its PCI version > (vhost-user-vsock-pci). > The vhost-user-vsock device can be used to implement the virtio-vsock > device emulation in user-space. > An use case might be Kata, where they prefer to emulate devices > in user-space. Looks good. My main concern is live migration. If it hasn't been tested, please remove the live migration code. Stefan
On Thu, May 21, 2020 at 03:35:59PM +0100, Stefan Hajnoczi wrote: > On Fri, May 15, 2020 at 05:21:07PM +0200, Stefano Garzarella wrote: > > This series add vhost-user-vsock base device and its PCI version > > (vhost-user-vsock-pci). > > The vhost-user-vsock device can be used to implement the virtio-vsock > > device emulation in user-space. > > An use case might be Kata, where they prefer to emulate devices > > in user-space. > > Looks good. > > My main concern is live migration. If it hasn't been tested, please > remove the live migration code. > Right, I didn't test live migration with vhost-user-vsock. I'll give it a try. If it doesn't work, I'll remove it. Thanks for the review, Stefano
On Thu, May 21, 2020 at 03:35:59PM +0100, Stefan Hajnoczi wrote: > On Fri, May 15, 2020 at 05:21:07PM +0200, Stefano Garzarella wrote: > > This series add vhost-user-vsock base device and its PCI version > > (vhost-user-vsock-pci). > > The vhost-user-vsock device can be used to implement the virtio-vsock > > device emulation in user-space. > > An use case might be Kata, where they prefer to emulate devices > > in user-space. > > Looks good. > > My main concern is live migration. If it hasn't been tested, please > remove the live migration code. > Migration is not working: QEMU 5.0.50 monitor - type 'help' for more information (qemu) migrate -d tcp:0:3333 Error: Migration disabled: vhost-user backend lacks VHOST_USER_PROTOCOL_F_LOG_SHMFD feature. Thanks for pointing that out, I'll remove it in v2. Stefano