On Wed, 19 Jul 2023 at 12:35, Hanna Czenczek wrote:
>
> On 18.07.23 17:57, Stefan Hajnoczi wrote:
> > On Wed, Jul 12, 2023 at 01:16:59PM +0200, Hanna Czenczek wrote:
> >> For vhost-user devices, qemu can migrate the virtio state, but not the
> >> back-end's internal state. To do so, we need to be
On 18.07.23 18:12, Stefan Hajnoczi wrote:
On Wed, Jul 12, 2023 at 01:16:59PM +0200, Hanna Czenczek wrote:
@@ -1471,6 +1511,53 @@ Front-end message types
before. The back-end must again begin processing rings that are not
stopped, and it may resume background operations.
+``VHOST_USER
On 18.07.23 17:57, Stefan Hajnoczi wrote:
On Wed, Jul 12, 2023 at 01:16:59PM +0200, Hanna Czenczek wrote:
For vhost-user devices, qemu can migrate the virtio state, but not the
back-end's internal state. To do so, we need to be able to transfer
this internal state between front-end (qemu) and b
On Wed, Jul 12, 2023 at 01:16:59PM +0200, Hanna Czenczek wrote:
> @@ -1471,6 +1511,53 @@ Front-end message types
>before. The back-end must again begin processing rings that are not
>stopped, and it may resume background operations.
>
> +``VHOST_USER_SET_DEVICE_STATE_FD``
> + :id: 43
>
On Wed, Jul 12, 2023 at 01:16:59PM +0200, Hanna Czenczek wrote:
> For vhost-user devices, qemu can migrate the virtio state, but not the
> back-end's internal state. To do so, we need to be able to transfer
> this internal state between front-end (qemu) and back-end.
>
> At this point, this new f
For vhost-user devices, qemu can migrate the virtio state, but not the
back-end's internal state. To do so, we need to be able to transfer
this internal state between front-end (qemu) and back-end.
At this point, this new feature is added for the purpose of virtio-fs
migration. Because virtiofsd
