From: Gerhard Wiesinger <lists@wiesinger.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Boot order problem and disable iPXE/gPXE
Date: Thu, 5 Jan 2012 09:23:02 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1201050917070.7992@bbs.intern> (raw)
In-Reply-To: <4F055827.50202@redhat.com>
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?
>> 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/
next prev parent reply other threads:[~2012-01-05 8:23 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 [this message]
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
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=alpine.LFD.2.02.1201050917070.7992@bbs.intern \
--to=lists@wiesinger.com \
--cc=kraxel@redhat.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 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.