qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Gerhard Wiesinger <lists@wiesinger.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE
Date: Thu, 05 Jan 2012 10:42:35 +0100	[thread overview]
Message-ID: <4F05708B.5040401@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1201051025070.31348@bbs.intern>

  Hi,

> But to get rid of this problem typical BIOSes have an option whether
> they prefer to BOOT from SCSI (with an option ROM) or
> from the other devices. Then the option ROM typically boots from the
> first registered device.

qemu+seabios have bootindex to address that issue.  It was created
exactly because "boot from hard disk" isn't good enougth with multiple
disks in the system ...

cheers,
  gerd

  parent reply	other threads:[~2012-01-05  9:42 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 18:02 [Qemu-devel] Boot order problem and disable iPXE/gPXE Gerhard Wiesinger
2012-01-05  3:03 ` Kevin O'Connor
2012-01-05  7:39   ` Gerhard Wiesinger
2012-01-06  1:42     ` Kevin O'Connor
2012-01-06  8:20       ` Gerhard Wiesinger
2012-01-06  8:59         ` Gerd Hoffmann
2012-01-05  7:50 ` Gleb Natapov
2012-01-05  7:58 ` Gerd Hoffmann
2012-01-05  8:23   ` Gerhard Wiesinger
2012-01-05  8:32     ` Gleb Natapov
2012-01-05  9:09       ` Gerhard Wiesinger
2012-01-05  9:20         ` Gleb Natapov
2012-01-05  9:27           ` Gerhard Wiesinger
2012-01-05  9:29             ` Gleb Natapov
2012-01-05  9:36               ` Gerhard Wiesinger
2012-01-05  9:42                 ` Gleb Natapov
2012-01-05  9:56                   ` Gerhard Wiesinger
2012-01-05 10:00                     ` Gleb Natapov
2012-01-05  9:42             ` Gerd Hoffmann [this message]
2012-01-06  2:05           ` Kevin O'Connor
2012-01-06  5:27             ` Gleb Natapov
2012-01-07  1:53               ` Kevin O'Connor
2012-01-07  9:00                 ` Gerhard Wiesinger
2012-01-07 16:28                   ` Kevin O'Connor
2012-01-07 22:47                     ` Gerhard Wiesinger
2012-01-07 22:53                       ` Kevin O'Connor
2012-01-08  8:31                     ` Gleb Natapov
2012-01-08 14:58                       ` Kevin O'Connor
2012-01-08 15:17                         ` Gleb Natapov
2012-01-08 15:47                           ` Kevin O'Connor
2012-01-25 20:30                             ` Gerhard Wiesinger
2012-01-09  9:10                 ` Gerd Hoffmann
2012-01-07  8:35             ` Gerhard Wiesinger
2012-01-07 16:20               ` Kevin O'Connor
2012-01-07 22:46                 ` Gerhard Wiesinger
2012-01-07 22:59                   ` Gerhard Wiesinger
2012-01-08 11:59                     ` Gerhard Wiesinger
2012-01-05  8:57     ` Gerd Hoffmann
2012-01-05  9:24       ` Gerhard Wiesinger
2012-01-05  9:53         ` Gerd Hoffmann
2012-01-05 10:08           ` Gerhard Wiesinger
2012-01-05 10:13             ` Gerd Hoffmann
2012-01-05 11:13               ` Gerhard Wiesinger
2012-01-05 11:16                 ` Gleb Natapov

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=4F05708B.5040401@redhat.com \
    --to=kraxel@redhat.com \
    --cc=gleb@redhat.com \
    --cc=lists@wiesinger.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).