Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 549315

Summary:	pxe boot failed: No valid PXE rom found for network device
Product:	Red Hat Enterprise Linux 5	Reporter:	Cao, Chen <kcao>
Component:	kvm	Assignee:	Eduardo Habkost <ehabkost>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.5	CC:	lihuang, tburke, virt-maint, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-29 10:23:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Cao, Chen 2009-12-21 10:09:10 UTC

Description of problem:
start vm with command:
# qemu-kvm -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=/kvm/images/win2003-32.qcow2,if=ide,snapshot=on,boot=on -net nic,vlan=0,model=e1000,macaddr=00:9B:FF:B5:A5:00 -net tap,vlan=0,ifname=e1000_0_6001,script=/kvm/scripts/qemu-ifup-switch,downscript=no -m 4096 -smp 2 -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -boot n -vnc :0

we got "No valid PXE rom found for network device" and command failed.
NOTE: gpxe is not installed at this point.


Version-Release number of selected component (if applicable):
83-139.el5


How reproducible:
100%


Steps to Reproduce:
1. type command:
--
qemu-kvm -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=/kvm/images/win2003-32.qcow2,if=ide,snapshot=on,boot=on -net nic,vlan=0,model=e1000,macaddr=00:9B:FF:B5:A5:00 -net tap,vlan=0,ifname=e1000_0_6001,script=/kvm/scripts/qemu-ifup-switch,downscript=no -m 4096 -smp 2 -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -boot n -vnc :0
--
into terminal.
2.
3.
  
Actual results:
qemu-kvm command failed with:
"No valid PXE rom found for network device"


Expected results:
VM can boot from network (using pxe server).


Additional info:
1.
if gpxe is not installed, we got:
the link "pxe-e1000.bin" pointing to an illegal (not existed) path.

2.
if gpxe-roms-qemu.x86_64 0:0.9.7-8.el5 is installed, with

# rpm -qa |grep kvm
kmod-kvm-83-139.el5
kvm-qemu-img-83-139.el5
etherboot-zroms-kvm-5.4.4-12.el5
kvm-debuginfo-83-139.el5
kvm-tools-83-139.el5
kvm-83-139.el5

we got "Too many option ROMS".

Comment 1 lihuang 2009-12-24 10:04:33 UTC


> 
> Additional info:
> 1.
> if gpxe is not installed, we got:
> the link "pxe-e1000.bin" pointing to an illegal (not existed) path.

FYI : the problem is in 550053.

> 
> 2.
> if gpxe-roms-qemu.x86_64 0:0.9.7-8.el5 is installed, with
> 
> # rpm -qa |grep kvm
> kmod-kvm-83-139.el5
> kvm-qemu-img-83-139.el5
> etherboot-zroms-kvm-5.4.4-12.el5
> kvm-debuginfo-83-139.el5
> kvm-tools-83-139.el5
> kvm-83-139.el5
> 
> we got "Too many option ROMS".  

the problem of "Too many option ROMS" is fixed in kvm-83-140.el5
but have new issue when using e1000 NIC  -->  Bug 550265

Comment 2 Dor Laor 2009-12-28 10:45:39 UTC

How 550265 solved then?

Comment 3 Cao, Chen 2009-12-29 02:06:03 UTC

(In reply to comment #2)
> How 550265 solved then?  

after updated to kvm-83-140 and etherboot-5.4.4-13.el5, this problem disappears.

Comment 4 Dor Laor 2009-12-29 09:03:41 UTC

Can you please close the bug then?

Comment 5 Yaniv Kaul 2009-12-29 09:10:37 UTC

(In reply to comment #4)
> Can you please close the bug then?  

I just saw it yesterday, on:
kvm-debuginfo-83-140.el5
kvm-qemu-img-83-140.el5
etherboot-roms-kvm-5.4.4-13.el5
kvm-83-140.el5
kvm-tools-83-140.el5
etherboot-zroms-kvm-5.4.4-13.el5

(vbian tried - from RHEVM).

Comment 6 Cao, Chen 2009-12-29 10:23:39 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > Can you please close the bug then?  
> 
> I just saw it yesterday, on:
> kvm-debuginfo-83-140.el5
> kvm-qemu-img-83-140.el5
> etherboot-roms-kvm-5.4.4-13.el5
> kvm-83-140.el5
> kvm-tools-83-140.el5
> etherboot-zroms-kvm-5.4.4-13.el5
> 
> (vbian tried - from RHEVM).  

Hi, Yaniv,

I have tested on the machine that vbian used
yesterday, and cannot reproduce the bug.
And she cannot reproduce it too for now,
because of the env issue (?) of RHVEM on her
hand.
besides, the packages on the machine might be
not clean yesterday, people installed/uninstalled
difference versions of gpxe/etherboot-[z]roms.

So, according to the results I've got, I think
we can close this bug.

Thanks for your concern.

---

kcao --> Dor

Hi, Dor,

According to lihuang's comment (Comment #1), I'd
like to close this bug as dupcliated to bz#550053.

Thanks.

Cao, Chen
2009/12/29

*** This bug has been marked as a duplicate of bug 550053 ***