From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:44851)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1QlHAO-0005Hj-CH
	for qemu-devel@nongnu.org; Mon, 25 Jul 2011 05:09:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1QlHAN-0005St-3a
	for qemu-devel@nongnu.org; Mon, 25 Jul 2011 05:09:36 -0400
Received: from mx1.redhat.com ([209.132.183.28]:63895)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1QlHAM-0005Sp-RT
	for qemu-devel@nongnu.org; Mon, 25 Jul 2011 05:09:35 -0400
Date: Mon, 25 Jul 2011 12:09:31 +0300
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20110725090931.GV3044@redhat.com>
References: <20110722095116.56bf87c5.usui@mxm.nes.nec.co.jp>
	<20110724063049.GM3044@redhat.com>
	<20110725164458.267a8197.usui@mxm.nes.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110725164458.267a8197.usui@mxm.nes.nec.co.jp>
Subject: Re: [Qemu-devel] Boot order problem
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: Minoru Usui <usui@mxm.nes.nec.co.jp>
Cc: qemu-devel@nongnu.org

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.