From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:48736) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Riikd-0004WR-KQ for qemu-devel@nongnu.org; Thu, 05 Jan 2012 03:32:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Riikc-0006as-Dy for qemu-devel@nongnu.org; Thu, 05 Jan 2012 03:32:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:6370) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Riikc-0006an-5w for qemu-devel@nongnu.org; Thu, 05 Jan 2012 03:32:42 -0500 Date: Thu, 5 Jan 2012 10:32:39 +0200 From: Gleb Natapov Message-ID: <20120105083239.GR2072@redhat.com> References: <4F055827.50202@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerhard Wiesinger Cc: Gerd Hoffmann , qemu-devel@nongnu.org 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. > >>2.) -device rtl8139,romfile=/dev/null > > > >Better use a empty string as romfile argument, that will make the ROM > >pci bar go away instead of creating one with an invalid rom. > > Thnx. Works well by specifying no romfile, that's the trick. I had > the problem than otherwise devices were created. But I'm still > getting the > following iPXE rom message: > iPXE v1.0.0-591-g7aee315 > iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+0FFCA670+0FF8A670 CA00 > > How to disable it, too? > What's this option ROM doing? Is it a general iPXE main loader? > > Thnx to all who replied. > > Ciao, > Gerhard > > -- > http://www.wiesinger.com/ -- Gleb.