qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Regression due to "Fall back to network boot..."
Date: Fri, 30 Oct 2009 20:32:31 +0100	[thread overview]
Message-ID: <4AEB3F4F.4060407@web.de> (raw)
In-Reply-To: <4AEB25B1.8040709@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Anthony Liguori wrote:
> Jan Kiszka wrote:
>> [ What happened to the scm commit list, btw?]
>>   
> 
> I need to move it to qemu.org.
> 
>> Hi Anthony,
>>
>> your patch 94ca5a9859 prevents booting PCs unless some boot order of
>> less than 4 devices is explicitly specified. The reason is
>>
>> #define PC_MAX_BOOT_DEVICES 3
>>
>> and the CMOS-based interface to the BIOS. Maybe the latter can be
>> enhanced so that the former can be increased, but for now reverting this
>> commit is probably better.
>>   
> 
> Sorry about that.  I swore I tested it and it seemed like such a simple
> change.  It's now reverted.

OK, thanks. Still one complaint: gPXE comes with an annoying boot delay
even if you can boot from disk or have _explicitly_ specified this. I'm
not familiar with it, but I bet there is some magic config switch to
disable this...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-10-30 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 17:16 [Qemu-devel] Regression due to "Fall back to network boot..." Jan Kiszka
2009-10-30 17:43 ` [Qemu-devel] " Anthony Liguori
2009-10-30 19:32   ` Jan Kiszka [this message]
2009-10-30 19:42     ` Anthony Liguori
2009-10-30 20:00       ` Jan Kiszka
2009-10-30 20:11         ` Anthony Liguori
2009-10-30 20:32           ` Jan Kiszka
2009-10-30 20:51             ` Anthony Liguori
2009-10-30 21:20           ` Alexander Graf

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=4AEB3F4F.4060407@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).