On (Wed) 11 Jun 2014 [10:50:04], Jason Wang wrote:
> On 06/10/2014 06:10 PM, Michael S. Tsirkin wrote:
> > On Tue, Jun 10, 2014 at 11:50:33AM +0530, Amit Shah wrote:
> >> On (Tue) 20 May 2014 [14:01:44], Jason Wang wrote:
> >>> It's hard to track all mac addresses and their configurations (e.g
> >>
On 06/10/2014 06:10 PM, Michael S. Tsirkin wrote:
> On Tue, Jun 10, 2014 at 11:50:33AM +0530, Amit Shah wrote:
>> On (Tue) 20 May 2014 [14:01:44], Jason Wang wrote:
>>> It's hard to track all mac addresses and their configurations (e.g
>>> vlan or ipv6) in qemu. Without this information, it's impos
On Tue, Jun 10, 2014 at 11:50:33AM +0530, Amit Shah wrote:
> On (Tue) 20 May 2014 [14:01:44], Jason Wang wrote:
> > It's hard to track all mac addresses and their configurations (e.g
> > vlan or ipv6) in qemu. Without this information, it's impossible to
> > build proper garp packet after migration
On (Tue) 20 May 2014 [14:01:44], Jason Wang wrote:
> It's hard to track all mac addresses and their configurations (e.g
> vlan or ipv6) in qemu. Without this information, it's impossible to
> build proper garp packet after migration. The only possible solution
> to this is let guest (who knows all
It's hard to track all mac addresses and their configurations (e.g
vlan or ipv6) in qemu. Without this information, it's impossible to
build proper garp packet after migration. The only possible solution
to this is let guest (who knows all configurations) to do this.
So, this patch introduces a ne
