Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Anton Kuchin
/* resend with fixed to: and cc: */ On 16/02/2023 18:22, Juan Quintela wrote: "Michael S. Tsirkin" wrote: On Thu, Feb 16, 2023 at 11:11:22AM -0500, Michael S. Tsirkin wrote: On Thu, Feb 16, 2023 at 03:14:05PM +0100, Juan Quintela wrote: Anton Kuchin wrote: Now any vhost-user-fs device make

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Anton Kuchin
On 16/02/2023 18:22, Juan Quintela wrote: "Michael S. Tsirkin" wrote: On Thu, Feb 16, 2023 at 11:11:22AM -0500, Michael S. Tsirkin wrote: On Thu, Feb 16, 2023 at 03:14:05PM +0100, Juan Quintela wrote: Anton Kuchin wrote: Now any vhost-user-fs device makes VM unmigratable, that also prevents

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Anton Kuchin
On 16/02/2023 23:09, Stefan Hajnoczi wrote: On Thu, Feb 16, 2023 at 04:00:03PM +0200, Anton Kuchin wrote: Now any vhost-user-fs device makes VM unmigratable, that also prevents qemu update without stopping the VM. In most cases that makes sense because qemu has no way to transfer FUSE session st

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Stefan Hajnoczi
On Thu, Feb 16, 2023 at 04:00:03PM +0200, Anton Kuchin wrote: > Now any vhost-user-fs device makes VM unmigratable, that also prevents > qemu update without stopping the VM. In most cases that makes sense > because qemu has no way to transfer FUSE session state. > > But it is good to have an optio

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Juan Quintela
"Michael S. Tsirkin" wrote: > On Thu, Feb 16, 2023 at 11:11:22AM -0500, Michael S. Tsirkin wrote: >> On Thu, Feb 16, 2023 at 03:14:05PM +0100, Juan Quintela wrote: >> > Anton Kuchin wrote: >> > > Now any vhost-user-fs device makes VM unmigratable, that also prevents >> > > qemu update without sto

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Juan Quintela
"Michael S. Tsirkin" wrote: > On Thu, Feb 16, 2023 at 03:14:05PM +0100, Juan Quintela wrote: >> Anton Kuchin wrote: >> > Now any vhost-user-fs device makes VM unmigratable, that also prevents >> > qemu update without stopping the VM. In most cases that makes sense >> > because qemu has no way to

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Michael S. Tsirkin
On Thu, Feb 16, 2023 at 11:11:22AM -0500, Michael S. Tsirkin wrote: > On Thu, Feb 16, 2023 at 03:14:05PM +0100, Juan Quintela wrote: > > Anton Kuchin wrote: > > > Now any vhost-user-fs device makes VM unmigratable, that also prevents > > > qemu update without stopping the VM. In most cases that ma

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Michael S. Tsirkin
On Thu, Feb 16, 2023 at 03:14:05PM +0100, Juan Quintela wrote: > Anton Kuchin wrote: > > Now any vhost-user-fs device makes VM unmigratable, that also prevents > > qemu update without stopping the VM. In most cases that makes sense > > because qemu has no way to transfer FUSE session state. > > >

Re: [PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Juan Quintela
Anton Kuchin wrote: > Now any vhost-user-fs device makes VM unmigratable, that also prevents > qemu update without stopping the VM. In most cases that makes sense > because qemu has no way to transfer FUSE session state. > > But it is good to have an option for orchestrator to tune this according

[PATCH v2 1/1] vhost-user-fs: add property to allow migration

2023-02-16 Thread Anton Kuchin
Now any vhost-user-fs device makes VM unmigratable, that also prevents qemu update without stopping the VM. In most cases that makes sense because qemu has no way to transfer FUSE session state. But it is good to have an option for orchestrator to tune this according to backend capabilities and mi