copy from 543979#c8 IIRC. 543979 is going to fix the problem of "e1000 rom is too big to fit the current ROMs section" create a new bug for the problem of "e1000 rom does work correctly" not sure if i select a correct component (gpxe ? kvm ?) please correct me if I am wrong . Comment #8 From lihuang (lihuang) 2009-12-23 02:44:18 EDT (-) [reply] ------- Private Created an attachment (id=379983) [details] screen shot I have test with [root@t77 ~]# rpm -qa gpxe* kvm* gpxe-roms-qemu-0.9.7-8.el5 kvm-83-140.el5 kvm-tools-83-140.el5 kvm-debuginfo-83-140.el5 kvm-qemu-img-83-140.el5 can not reproduce the " Too many option ROMS" error, when using e1000 nic but the e1000 bin doesn't work. when I use cli : -net nic,model=e1000 -net tap -boot n error in the VNC windows is -- FATAL: No bootable device -- when Press F12 on the boot menu.there is no _network_ in the boot menu,(refer to attachment) also test -option-rom /usr/share/qemu-pxe-roms/e1000-82542.zrom result same using rtl8139 and virtio. boot from network is PASS. [root@t77 kvm]# ls -l /usr/share/kvm/pxe-e1000.bin lrwxrwxrwx 1 root root 33 Dec 23 11:58 /usr/share/kvm/pxe-e1000.bin -> ../qemu-pxe-roms/e1000-82542.zrom [root@t77 kvm]# rpm -qf ../qemu-pxe-roms/e1000-82542.zrom gpxe-roms-qemu-0.9.7-8.el5
It is probably a BIOS (therefore, kvm) bug. bochs bios used to not be able to checksum roms bigger than 64k. We probably lack the patch that fixes it.
Please test the following rpm, and let me know about the results: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2167920
> Please test the following rpm, and let me know about the results: > > http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2167920 Yes . gpxe boot with e1000 nic works
Cool. I'll post the patch
Tested on kvm-83-147.el5. pass. kvm version:kvm-83-147.el5 Host kernel:2.6.18-183.e15 gpxe : gpxe-roms-qemu-0.9.7-8.el5 steps: 1.boot guest visa -net nic,model=e1000 -net tap -boot n: /usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -m 2G -smp 2 -drive file=/home/RHEL4.8-32bit-network.raw,if=virtio,boot=on -drive file=/home/gpxe.iso,media=cdrom -net nic,vlan=0,macaddr=22:11:22:45:66:99,model=e1000 -net tap,vlan=0,script=/etc/qemu-ifup -uuid `uuidgen` -cpu qemu64,+sse2 -balloon none -boot n -monitor stdio -vnc :10 -notify all 2.boot guest visa -option-rom -option-rom /usr/share/qemu-pxe-roms/e1000-82542.zrom /usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -m 2G -smp 2 -drive file=/home/RHEL4.8-32bit-network.raw,if=virtio,boot=on -drive file=/home/gpxe.iso,media=cdrom -net nic,vlan=0,macaddr=22:11:22:45:66:99,model=e1000 -net tap,vlan=0,script=/etc/qemu-ifup -uuid `uuidgen` -cpu qemu64,+sse2 -balloon none -boot n -monitor stdio -vnc :10 -notify all -option-rom /usr/share/qemu-pxe-roms/e1000-82542.zrom Results: gPXE sucessfully PXE boot on e1000 virtual NIC
Reproduced on kvm-83-140.el5. fail. Tested on kvm-83-147.el5. pass. 1), Reproduced on on kvm-83-140.el5. fail. gpxe: gpxe-roms-qemu-0.9.7-8.el5 kvm : kvm-83-140.el5 #rpm -qf e1000-82542.zrom gpxe-roms-qemu-0.9.7-8.el5 steps: 1.boot guest visa -net nic,model=e1000 -net tap -boot n: /usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -m 2G -smp 2 -drive file=/home/RHEL4.8-32bit-network.raw,if=virtio,boot=on -drive file=/home/gpxe.iso,media=cdrom -net nic,vlan=0,macaddr=22:11:22:45:66:99,model=e1000 -net tap,vlan=0,script=/etc/qemu-ifup -uuid `uuidgen` -cpu qemu64,+sse2 -balloon none -boot n -monitor stdio -vnc :10 -notify all Results: error in the VNC windows is -- FATAL: No bootable device -- when Press F12 on the boot menu.there is no network in the boot menu 2),Tested on kvm-83-147.el5. pass. gpxe: gpxe-roms-qemu-0.9.7-8.el5 kvm : kvm-83-147.el5 #rpm -qf e1000-82542.zrom gpxe-roms-qemu-0.9.7-8.el5 steps: The same as above steps. Results: gPXE sucessfully PXE boot on e1000 virtual NIC
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0271.html