All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Minoru Usui <usui@mxm.nes.nec.co.jp>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Boot order problem
Date: Mon, 25 Jul 2011 12:09:31 +0300	[thread overview]
Message-ID: <20110725090931.GV3044@redhat.com> (raw)
In-Reply-To: <20110725164458.267a8197.usui@mxm.nes.nec.co.jp>

On Mon, Jul 25, 2011 at 04:44:58PM +0900, Minoru Usui wrote:
> On Sun, 24 Jul 2011 09:30:49 +0300
> Gleb Natapov <gleb@redhat.com> wrote:
> 
[skip]

> I tested another one about <boot order> case on RHEL6.1, and I also faced another problem.
> 
> VM has two virtio HDD. HDD1 is installed RHEL6.1, HDD2 is empty.
> I specified boot order to HDD1:1, HDD2:2, VM booted up from HDD1,
> but boot order HDD1:2, HDD2:1 case, VM couldn't boot up from HDD2.
> (It searched CD-ROM, NIC(gPXE), and finally stopped booting.)
> 
That's BIOS specification limitation. BIOS can't fall back from one HDD
to another, so only HDD with lowest priority among all HDDs will be tried.
 
> It seems seabios searches only 1 device per device list(HDD, CD-ROM, NET, FLOPPY).
> Is it true?
No, it searches only one HDD. Other devices do not have this limitation
IIRC.

> 
> <boot order> can specify per device, so shouldn't seabios search all device,
> even if it specifies multiple device per device list?
> 
> -- 
> Minoru Usui <usui@mxm.nes.nec.co.jp>

--
			Gleb.

  reply	other threads:[~2011-07-25  9:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22  0:51 [Qemu-devel] Boot order problem Minoru Usui
2011-07-24  6:30 ` Gleb Natapov
2011-07-25  7:07   ` Minoru Usui
2011-07-25  9:06     ` Gleb Natapov
2011-07-26  1:07       ` Minoru Usui
2011-07-25  7:44   ` Minoru Usui
2011-07-25  9:09     ` Gleb Natapov [this message]
2011-07-26  1:00       ` Minoru Usui

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=20110725090931.GV3044@redhat.com \
    --to=gleb@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=usui@mxm.nes.nec.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.