From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:36845)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lists@wiesinger.com>) id 1RijLX-0002J1-Nz
	for qemu-devel@nongnu.org; Thu, 05 Jan 2012 04:10:57 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lists@wiesinger.com>) id 1RijLS-0004h1-2B
	for qemu-devel@nongnu.org; Thu, 05 Jan 2012 04:10:51 -0500
Received: from chello084112167138.7.11.vie.surfer.at ([84.112.167.138]:54994
	helo=wiesinger.com) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lists@wiesinger.com>) id 1RijLR-0004gS-Jo
	for qemu-devel@nongnu.org; Thu, 05 Jan 2012 04:10:45 -0500
Date: Thu, 5 Jan 2012 10:09:44 +0100 (CET)
From: Gerhard Wiesinger <lists@wiesinger.com>
In-Reply-To: <20120105083239.GR2072@redhat.com>
Message-ID: <alpine.LFD.2.02.1201051008000.22639@bbs.intern>
References: <alpine.LFD.2.02.1201041749370.16793@bbs.intern>
	<4F055827.50202@redhat.com>
	<alpine.LFD.2.02.1201050917070.7992@bbs.intern>
	<20120105083239.GR2072@redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE
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: Gleb Natapov <gleb@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org

On Thu, 5 Jan 2012, Gleb Natapov wrote:

> On Thu, Jan 05, 2012 at 09:23:02AM +0100, Gerhard Wiesinger wrote:
>> On Thu, 5 Jan 2012, Gerd Hoffmann wrote:
>>
>>> On 01/04/12 19:02, Gerhard Wiesinger wrote:
>>>> Hello,
>>>>
>>>> I'm having the following boot order problem using an SCSI option ROM:
>>>>
>>>
>>>> Still boots the cdrom instead of harddisk. So it is impossible to have a
>>>> bootable CDROM in the VM without booting from it.
>>>
>>> -option-rom romfile=/root/roms/8xx_64.rom,bootindex=1
>>
>> Ok, works well, but I think than "-boot order=c" is buggy, right?
>>
> Wrong. "-boot order=c" tells seabios to boot from a HD, but for that
> Seabios needs to actually know what is HD and what is not. Since Seabios
> does not support scsi controller natively it only sees pci device and
> has no idea that you have scsi disk there. It uses pci option rom to
> boot from this unknown device.

But as far as I remember therefore the option ROM registers through BIOS 
for INT 19h booting. So Seabios should know it that this is a harddisk.
I think this usecase is currently not supported.

Ciao,
Gerhard

--
http://www.wiesinger.com/