On 05/12/2014 03:22 PM, Michael S. Tsirkin wrote:
> On Fri, Apr 11, 2014 at 10:54:47AM +0800, Jason Wang wrote:
>> > It's hard to track all mac addresses and their configurations (e.g
>> > vlan or ipv6) in qemu. Without those informations, it's impossible to
>> > build proper garp packet after migr
On Fri, Apr 11, 2014 at 10:54:47AM +0800, Jason Wang wrote:
> It's hard to track all mac addresses and their configurations (e.g
> vlan or ipv6) in qemu. Without those informations, it's impossible to
> build proper garp packet after migration. The only possible solution
> to this is let guest (who
On Fri, 2014-04-11 at 22:10 +0800, 陈梁 wrote:
> Hi Jason,
> Have you ever test that adds a bridge on the virtio-net in vm and migrate the
> vm?
I tested both ipv4 and ipv6, all work well.
> The bridge may don't send garp packet(in my testing).
Several questions:
- The garp should be sent by guest
Hi Jason,
Have you ever test that adds a bridge on the virtio-net in vm and migrate the
vm?
The bridge may don't send garp packet(in my testing). BTW, how about the other
net devices like e1000 and rtl8139? Is it better that qemu notifys qemu guest
agent
to force the net devices in the vm to send
It's hard to track all mac addresses and their configurations (e.g
vlan or ipv6) in qemu. Without those informations, it's impossible to
build proper garp packet after migration. The only possible solution
to this is let guest (who knew all configurations) to do this.
So, this patch introduces a n
