public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Stuart Sheldon <stu@actusa.net>
To: Jim Paris <jim@jtan.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, kvm@vger.kernel.org
Subject: Re: PXE Boot Timeout Issue...
Date: Fri, 23 Apr 2010 10:29:45 -0700	[thread overview]
Message-ID: <4BD1D909.7030409@actusa.net> (raw)
In-Reply-To: <20100423172252.GA18243@psychosis.jim.sh>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Jim Paris wrote:
> Stuart Sheldon wrote:
>> Stefan Hajnoczi wrote:
>>> On Fri, Apr 23, 2010 at 1:45 AM, Stuart Sheldon <stu@actusa.net> wrote:
>>>> Just upgraded to 12.3 user space tools from 11.0, and now when I attempt
>>>> to netboot a guest, it appears that the pxe rom is timing out on dhcp
>>>> before the bridge has enough time to come up.
> ....
>> 3) after about 15 seconds, tap device enters promiscuous mode on host,
>> and at same time, gPXE reports "No bootable device." on guest
> ...
>>  forward delay		  15.00			bridge forward delay	  15.00
> 
> I've run into this issue as well and lowering the forwarding delay
> with "brctl setfd br0 5" fixes it.
> 
> -jim
> 

Thanks Jim! I think that has it...

Stu


- --
Hey nineteen Thats retha franklin, She dont remember The queen of soul,
Its hard times befallen The sole survivors, She thinks Im crazy,
But Im just growing old
               -- Steely Dan - "Hey 19 - Lyrics"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJL0dkFAAoJEFKVLITDJSGSwJAQAIBL16jFmTavFWX0dU50syP+
VtK3EqQcv02bJdpAXdbfKuO1QDdjmucG2zEbNK4lMXKEwBsGcKtxDhUOVaNS07fK
OdfvsO+/wX9mC8JmqCah6r8Pwppd3F07nzP3HkPnswV/rgtDVrSWB2JInDy+d3R7
sd0DisPOeaHoXSQqJ8REGElVR2adzsdmRWUKpFmtu9tJCz48wsbkDLpcr5iMt7jA
sAPtTm1ENUEF3X3l6mlGB4kuYsLum93hPpgrxWmMvGO3uokVzRJYm3x2Yf5J++3v
yc8reMPPsQe1tI9r+ZtCKXE2XLqI/X4Pdap0IIjtid2245dBOMKys+aIXYZ1d7jL
YwngcgFDdse6B3Gt9/Tk5RhqqYQeYLsZckMOhy89DN2bftYxsX70xIWKKVxPEkNg
GniSN8pCg/Rx4ZOFkygwXRUayOx5Hi5nR6hetKyBqRM6mWYZvfvzRYH3O05JAOIz
3qKRObyuKHYFGkdWZ1LaTBoQoOdq+iWyuPK53kvpHFbdks6mZZg3YO70M6+ziqyT
zy9UvuumjzquuFwRu91R0qi02SZlNifvTQZ9aUpsPvRAhijroidqIzsH/5CoDuDe
AyQEKJgq64/ViA2QrYgpo/IFLAUbhCpMRIr7Tt5Te2TT+s43Lefyg6aY2XA2UwY0
6LwIWdBWwITjvP7XUU5B
=hwfS
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-04-23 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23  0:45 PXE Boot Timeout Issue Stuart Sheldon
2010-04-23  8:27 ` Stefan Hajnoczi
2010-04-23 16:14   ` Stuart Sheldon
2010-04-23 17:22     ` Jim Paris
2010-04-23 17:29       ` Stuart Sheldon [this message]
2010-04-23 19:23         ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BD1D909.7030409@actusa.net \
    --to=stu@actusa.net \
    --cc=jim@jtan.com \
    --cc=kvm@vger.kernel.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox