From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:42790)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1SCFAR-0000st-4s
	for qemu-devel@nongnu.org; Mon, 26 Mar 2012 15:01:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1SCFAO-00084Q-4B
	for qemu-devel@nongnu.org; Mon, 26 Mar 2012 15:01:22 -0400
Received: from isrv.corpit.ru ([86.62.121.231]:39957)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mjt@tls.msk.ru>) id 1SCFAN-00082r-T9
	for qemu-devel@nongnu.org; Mon, 26 Mar 2012 15:01:20 -0400
Message-ID: <4F70BCF5.2030901@msgid.tls.msk.ru>
Date: Mon, 26 Mar 2012 23:01:09 +0400
From: Michael Tokarev <mjt@tls.msk.ru>
MIME-Version: 1.0
References: <20100602141509.9453.12384.malonedeb@soybean.canonical.com>
	<20120326151845.22107.56060.malone@soybean.canonical.com>
In-Reply-To: <20120326151845.22107.56060.malone@soybean.canonical.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [Bug 588731] Re: PXE boot not working
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Bug 588731 <588731@bugs.launchpad.net>
Cc: Michal Suchanek <hramrach@gmail.com>, qemu-devel@nongnu.org

On 26.03.2012 19:18, Michal Suchanek wrote:
> There seems to be an issue with kvm virtual network interface being
> connected to a in-kernel bridge implementation.
> 
> When you configure networking that way the bridge port comes up when the
> kvm instance is started.
> 
> As the time from the kvm start to entering the netboot rom is minimal
> and the timeout before the bridge starts forwarding on new ports is long
> this may cause the machine never getting an address.
> 
> If you are using a bridge try setting the forwarding delay to a small
> value like:
> 
> iface vmbridge inet static
>  bridge_ports <probably should put some network interface name here - undocumented>
>  address 10.10.10.1
>  netmask 255.255.255.0
>  post-up brctl setfd vmbridge 3

Use
  bridge_fd 0

here instead of these post-up things.

/mjt