From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM doesn't send an arp announce after live migrating a domain Date: Wed, 25 Aug 2010 14:30:01 +0300 Message-ID: <4C74FEB9.40204@redhat.com> References: <4C74CBB0.7080203@kangaroot.net> <20100825083812.GG10499@redhat.com> <4C74E091.60100@kangaroot.net> <4C74F313.6040604@redhat.com> <20100825105232.GE13337@redhat.com> <4C74F909.8020909@redhat.com> <20100825111511.GF13337@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nils Cant , Gleb Natapov , kvm@vger.kernel.org, libvir-list@redhat.com To: "Daniel P. Berrange" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:26755 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752437Ab0HYLaS (ORCPT ); Wed, 25 Aug 2010 07:30:18 -0400 In-Reply-To: <20100825111511.GF13337@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/25/2010 02:15 PM, Daniel P. Berrange wrote: > >> So it looks like the default config uses the kernel default? If libvirt >> uses an existing bridge I agree it shouldn't hack it, but if it creates >> its own can't it use a sensible default? > That is the NAT virtual network. That one *does* default to a forward > delay of 0, but since it is NAT, it is fairly useless for migration > in anycase. If you do 'virsh net-dumpxml default' you should see that > delay='0' was added > > The OP was using bridging rather than NAT though, so this XML example > doesn't apply. My comments about libvirt not overriding kenrel policy > for forward delay were WRT full bridging mode, not the NAT mode[1] Yes, of course. Can't libvirt also create a non-NAT bridge? Looks like it would prevent a lot of manual work and opportunity for misconfiguration. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.