From: Gerhard Wiesinger <lists@wiesinger.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Boot order problem and disable iPXE/gPXE
Date: Wed, 4 Jan 2012 19:02:34 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1201041749370.16793@bbs.intern> (raw)
Hello,
I'm having the following boot order problem using an SCSI option ROM:
Command line:
/root/download/qemu/git/qemu-kvm/x86_64-softmmu/qemu-system-x86_64
-drive file=1.img,media=disk,if=scsi,bus=0,unit=0
-drive file=2.img,media=disk,if=scsi,bus=0,unit=1
-drive file=3.img,media=disk,if=scsi,bus=0,unit=2
-drive file=4.img,media=disk,if=scsi,bus=0,unit=3
-cdrom KNOPPIX_V6.2CD-2009-11-18-DE.iso
-boot order=c -m 256 -k de -vga vmware -vnc :0
-bios /root/download/seabios/git/seabios/out/bios.bin
-option-rom BIOS/8xx_64.rom
-net nic,model=rtl8139,macaddr=1a:46:0b:ca:bc:7c
-net tap,ifname=tap0,script=no,downscript=no
Still boots the cdrom instead of harddisk. So it is impossible to have a
bootable CDROM in the VM without booting from it.
Going into boot menu (-boot order=c,menu=on)and selecting HD works well.
Any ideas to fix it?
I also want to disable iPXE/gPXE on boot. I found several "workarounds"
specifying rom files on different command lines:
1.) -net nic,model=rtl8139,macaddr=1a:46:0b:ca:bc:7c,rom=/dev/null
(https://lists.gnu.org/archive/html/qemu-devel/2010-03/msg00546.html)
2.) -device rtl8139,romfile=/dev/null
3.) remove ROM files.
I think best way would be:
-net nic,model=rtl8139,macaddr=1a:46:0b:ca:bc:7c,rom=/dev/null
or by SEABIOS boot option.
Removing rom files isn't an option because I want it by command line
switch and need them for other VMs.
Any thoughts?
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
next reply other threads:[~2012-01-04 18:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 18:02 Gerhard Wiesinger [this message]
2012-01-05 3:03 ` [Qemu-devel] Boot order problem and disable iPXE/gPXE 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
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.1201041749370.16793@bbs.intern \
--to=lists@wiesinger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).