From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>, qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Jens Freimann <jfreimann@redhat.com>
Subject: Re: [PATCH v4] failover: unregister ROM on unplug
Date: Wed, 21 Jul 2021 18:19:01 +0200 [thread overview]
Message-ID: <785aa26e-260c-fd30-de55-c2bf6ab4e5a7@redhat.com> (raw)
In-Reply-To: <20210721160905.234915-1-lvivier@redhat.com>
On 7/21/21 6:09 PM, Laurent Vivier wrote:
> The intend of failover is to allow to migrate a VM with a VFIO
> networking card without disrupting the network operation by switching
> to a virtio-net device during the migration.
>
> This simple change allows to test failover with a simulated device
> like e1000e rather than a vfio device, even if it's useless in real
> life it can help to debug failover.
>
> This is interesting to developers that want to test failover on
> a system with no vfio device. Moreover it simplifies host networking
> configuration as we can use the same bridge for virtio-net and
> the other failover networking device.
>
> Without this change the migration of a system configured with failover
> fails with:
>
> ...
> -device virtio-net-pci,id=virtionet0,failover=on,... \
> -device e1000,failover_pair_id=virtionet0,... \
> ...
>
> (qemu) migrate ...
>
> Unknown ramblock "0000:00:01.1:00.0/e1000e.rom", cannot accept migration
> error while loading state for instance 0x0 of device 'ram'
> load of migration failed: Invalid argument
>
> This happens because QEMU correctly unregisters the interface vmstate but
> not the ROM one. This patch fixes that.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
>
> Notes:
> v4:
> export and use pci_del_option_rom()
>
> v3:
> remove useless space before comma
>
> v2:
> reset has_rom to false
> update commit log message
>
> include/hw/pci/pci.h | 2 ++
> hw/net/virtio-net.c | 1 +
> hw/pci/pci.c | 3 +--
> 3 files changed, 4 insertions(+), 2 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2021-07-21 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 16:09 [PATCH v4] failover: unregister ROM on unplug Laurent Vivier
2021-07-21 16:19 ` Philippe Mathieu-Daudé [this message]
2021-07-21 16:19 ` Michael S. Tsirkin
2021-07-21 17:01 ` Laurent Vivier
2021-07-23 8:55 ` Laurent Vivier
2021-08-03 14:04 ` Michael S. Tsirkin
2021-08-03 14:49 ` Laurent Vivier
2021-08-11 6:50 ` Michael S. Tsirkin
2021-08-11 9:51 ` Laurent Vivier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=785aa26e-260c-fd30-de55-c2bf6ab4e5a7@redhat.com \
--to=philmd@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).