Red Hat Bugzilla – Bug 473137
virtio PXE rom too large - Too many option ROMS
Last modified: 2013-09-02 02:29:55 EDT
Cloned from bug#472236 to address not being able to boot a guest with multiple boot targets. For example:
# virsh dumpxml vguest1 | grep "<boot"
# virsh start vguest1
libvir: QEMU error : internal error QEMU quit during monitor startup
error: Failed to start domain vguest1
# cat /var/log/libvirt/qemu/vguest1.log
/usr/bin/qemu-kvm -S -M pc -m 1024 -smp 2 -name vguest1 -monitor pty -boot nc
-drive file=/dev/VolGroup00/vguest1,if=ide,index=0,boot=on -drive
tap,fd=14,script=,vlan=0,ifname=vnet2 -serial pty -parallel none -usb -vnc
127.0.0.1:3 -k en-us
char device redirected to /dev/pts/8
char device redirected to /dev/pts/9
Too many option ROMS
The problem has been best described by gcosta below ...
--- Additional comment from firstname.lastname@example.org on 2008-11-26 12:57:58 EDT ---
I believe the problem itself is very simple (although I don't really know a good solution without thinking a little bit...)
there's only 64k of memory available for option roms, and the virtio rom that ships with our packages is... 64k in size!. So after loading the virtio PXE option rom, we're unable to keep loading option roms, in particular, the extboot option rom we need to kick out virtio boots. ;-(
James said he could boot with an older rom I handled to him, which is 32k in size,
and the problem os "Too many option ROMS" went away.
However, he was still unable to boot from the local target, despite of the fact that he could do a local boot by pressing "q"
So we really have two problems in here:
The first one is that we cannot boot from our current virtio ROM, because it is too large. We can try to quick fix it by building smaller images. This should be a new BZ agains the etherboot package.
And the other, the fact that roms do not honor the local target. For that, I believe we can keep using this BZ.
etherboot-5.4.4-5.fc10 has been submitted as an update for Fedora 10.
etherboot-5.4.4-5.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update etherboot'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2008-10657
Update to etherboot-roms-kvm-5.4.4-5.fc10.i386 resolved problem for me. See bug#491515 comment #4 and #5
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.