[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [virtio-net] migration
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [virtio-net] migration |
Date: |
Thu, 9 Jun 2016 13:59:38 +0100 |
User-agent: |
Mutt/1.6.1 (2016-04-27) |
On Fri, May 27, 2016 at 12:59:51PM +0000, Catalin Vasile wrote:
> What is the workflow for virtio-net devices when migrating the VM it belongs
> to?
> From what I understand so far the stop() primitives in qemu are called for
> virtio_net and vhost_net which makes the virtqueue reset such that it seems
> the queues are completely empty.
> How does the guest know that the jobs he sent on the virtqueue were discarded
> so that he can retry or release resources that were used for managing those
> jobs/packets?
No, virtqueues stay as-is across migration. vring state (e.g.
last_avail_idx) is migrated so that the new QEMU can pick up where the
old one left off.
See hw/virtio/virtio.c load/save code to learn more.
Stefan
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Qemu-devel] [virtio-net] migration,
Stefan Hajnoczi <=