From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Jens Freimann <jfreimann@redhat.com>
Cc: pkrempa@redhat.com, berrange@redhat.com, ehabkost@redhat.com,
mst@redhat.com, aadam@redhat.com, qemu-devel@nongnu.org,
alex.williamson@redhat.com, laine@redhat.com, ailan@redhat.com,
parav@mellanox.com
Subject: Re: [PATCH v5 06/11] qapi: add failover negotiated event
Date: Thu, 24 Oct 2019 18:32:45 +0100 [thread overview]
Message-ID: <20191024173245.GP2877@work-vm> (raw)
In-Reply-To: <20191023082711.16694-7-jfreimann@redhat.com>
* Jens Freimann (jfreimann@redhat.com) wrote:
> This event is sent to let libvirt know that VIRTIO_NET_F_STANDBY
> feature was not negotiated during virtio feature negotiation. If this
> event is received it means any primary devices hotplugged before
> this were were never really added to QEMU devices.
>
> Signed-off-by: Jens Freimann <jfreimann@redhat.com>
Can I just understand a bit more about what the meaning of this is.
Say my VM boots:
a) BIOS
b) Boot loader
c) Linux
d) Reboots
(possibly a',b', different c')
When would I get that event?
When can libvirt know it can use it?
Dave
> ---
> qapi/net.json | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/qapi/net.json b/qapi/net.json
> index 728990f4fb..8c5f3f1fb2 100644
> --- a/qapi/net.json
> +++ b/qapi/net.json
> @@ -737,3 +737,19 @@
> ##
> { 'command': 'announce-self', 'boxed': true,
> 'data' : 'AnnounceParameters'}
> +
> +##
> +# @FAILOVER_NEGOTIATED:
> +#
> +# Emitted when VIRTIO_NET_F_STANDBY was negotiated during feature negotiation
> +#
> +# Since: 4.2
> +#
> +# Example:
> +#
> +# <- { "event": "FAILOVER_NEGOTIATED",
> +# "data": {} }
> +#
> +##
> +{ 'event': 'FAILOVER_NEGOTIATED',
> + 'data': {} }
> --
> 2.21.0
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-10-24 18:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 8:27 [PATCH v5 0/11] add failover feature for assigned network devices Jens Freimann
2019-10-23 8:27 ` [PATCH v5 01/11] qdev/qbus: add hidden device support Jens Freimann
2019-10-23 8:27 ` [PATCH v5 02/11] pci: add option for net failover Jens Freimann
2019-10-23 18:06 ` Alex Williamson
2019-10-23 19:30 ` Jens Freimann
2019-10-23 20:02 ` Alex Williamson
2019-10-23 20:31 ` Jens Freimann
2019-10-23 21:15 ` Alex Williamson
2019-10-24 17:57 ` Laine Stump
2019-10-25 10:52 ` Jens Freimann
2019-10-25 14:56 ` Alex Williamson
2019-10-24 5:03 ` Parav Pandit
2019-10-24 9:37 ` Jens Freimann
2019-10-24 16:34 ` Parav Pandit
2019-10-24 17:06 ` Alex Williamson
2019-10-24 16:52 ` Alex Williamson
2019-10-24 20:08 ` Jens Freimann
2019-10-24 17:22 ` Dr. David Alan Gilbert
2019-10-24 19:56 ` Jens Freimann
2019-10-23 8:27 ` [PATCH v5 03/11] pci: mark devices partially unplugged Jens Freimann
2019-10-23 8:27 ` [PATCH v5 04/11] pci: mark device having guest unplug request pending Jens Freimann
2019-10-23 8:27 ` [PATCH v5 05/11] qapi: add unplug primary event Jens Freimann
2019-10-23 11:32 ` Eric Blake
2019-10-23 8:27 ` [PATCH v5 06/11] qapi: add failover negotiated event Jens Freimann
2019-10-24 17:32 ` Dr. David Alan Gilbert [this message]
2019-10-24 20:03 ` Jens Freimann
2019-10-25 5:35 ` Markus Armbruster
2019-10-25 7:51 ` Jens Freimann
2019-10-23 8:27 ` [PATCH v5 07/11] migration: allow unplug during migration for failover devices Jens Freimann
2019-10-23 8:27 ` [PATCH v5 08/11] migration: add new migration state wait-unplug Jens Freimann
2019-10-23 8:27 ` [PATCH v5 09/11] libqos: tolerate wait-unplug migration state Jens Freimann
2019-10-23 8:27 ` [PATCH v5 10/11] net/virtio: add failover support Jens Freimann
2019-10-23 8:27 ` [PATCH v5 11/11] vfio: unplug failover primary device before migration Jens Freimann
2019-10-23 18:28 ` Alex Williamson
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=20191024173245.GP2877@work-vm \
--to=dgilbert@redhat.com \
--cc=aadam@redhat.com \
--cc=ailan@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jfreimann@redhat.com \
--cc=laine@redhat.com \
--cc=mst@redhat.com \
--cc=parav@mellanox.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).