From: Jason Wang <jasowang@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Germano Veit Michel <germano@redhat.com>,
armbru@redhat.com
Cc: qemu-devel@nongnu.org, Juan Jose Quintela Carreira <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2] migration: expose qemu_announce_self() via qmp
Date: Mon, 6 Mar 2017 12:02:52 +0800 [thread overview]
Message-ID: <bebb011d-5cf9-c33a-5920-a029cae5f558@redhat.com> (raw)
In-Reply-To: <20170303103919.GA2439@work-vm>
On 2017年03月03日 18:39, Dr. David Alan Gilbert wrote:
> * Germano Veit Michel (germano@redhat.com) wrote:
>> qemu_announce_self() is triggered by qemu at the end of migrations
>> to update the network regarding the path to the guest l2addr.
>>
>> however it is also useful when there is a network change such as
>> an active bond slave swap. Essentially, it's the same as a migration
>> from a network perspective - the guest moves to a different point
>> in the network topology.
>>
>> this exposes the function via qmp.
> Markus: Since you're asking for tests for qmp commands; how would you
> test this?
>
> Jason: Does this look OK from the networking side of things?
>
Good as a start I think. We probably want to add callbacks for each
kinds of nic. This will be useful for virtio, since some guest can
announce themselves with complex configurations (e.g vlans).
Thanks
next prev parent reply other threads:[~2017-03-06 4:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 0:16 [Qemu-devel] [PATCH V2] migration: expose qemu_announce_self() via qmp Germano Veit Michel
2017-03-03 10:39 ` Dr. David Alan Gilbert
2017-03-03 12:06 ` Markus Armbruster
2017-03-13 2:59 ` Germano Veit Michel
2017-03-13 5:24 ` Markus Armbruster
2017-03-13 8:51 ` Markus Armbruster
2017-03-27 16:31 ` Dr. David Alan Gilbert
2017-05-05 0:36 ` Germano Veit Michel
2017-05-05 6:13 ` Markus Armbruster
2017-05-05 9:26 ` Jason Wang
2017-03-06 4:02 ` Jason Wang [this message]
2017-05-11 21:37 ` Vlad Yasevich
2017-05-12 19:24 ` Dr. David Alan Gilbert
2017-05-12 21:16 ` Vlad Yasevich
2017-05-22 23:23 ` Germano Veit Michel
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=bebb011d-5cf9-c33a-5920-a029cae5f558@redhat.com \
--to=jasowang@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=germano@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).