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:05:45 +0300 Message-ID: <4C74F909.8020909@redhat.com> References: <4C74CBB0.7080203@kangaroot.net> <20100825083812.GG10499@redhat.com> <4C74E091.60100@kangaroot.net> <4C74F313.6040604@redhat.com> <20100825105232.GE13337@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]:20909 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752211Ab0HYLGJ (ORCPT ); Wed, 25 Aug 2010 07:06:09 -0400 In-Reply-To: <20100825105232.GE13337@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/25/2010 01:52 PM, Daniel P. Berrange wrote: > >> I think libvirt is doing something about this, copying list for further >> info. > libvirt doesn't set a policy for this. It provides an API for > configuring host networking, but we don't override the kernel's > forward delay policy, since we don't presume that all bridges > are going to have VMs attached. In any case the API isn't available > for Debian yet, since no one has ported netcf to Debian, so I > assume the OP set bridging up manually. The '15' second default is > actually a kernel level default IIRC. > > The two main host network configs recommended for use with libvirt+KVM > (either NAT or bridging) are documented here: > > http://wiki.libvirt.org/page/Networking From that page: # virsh net-define /usr/share/libvirt/networks/default.xml From my copy of that file: default 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? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.