* Jens Freimann (jfreim...@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 <jfreim...@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 / dgilb...@redhat.com / Manchester, UK
