Bug 511912 - ne model failed to get ip address
Summary: ne model failed to get ip address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: etherboot
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Naphtali Sprei
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 526124
TreeView+ depends on / blocked
 
Reported: 2009-07-15 15:52 UTC by Jia Dong
Modified: 2013-01-09 21:47 UTC (History)
6 users (show)

Fixed In Version: etherboot-5.4.4-11.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 526124 (view as bug list)
Environment:
Last Closed: 2010-03-30 08:20:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
etherboot zrom generated from rom-o-matic site for the ne2k-pci (32.00 KB, application/octet-stream)
2009-09-22 10:56 UTC, Naphtali Sprei
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0227 0 normal SHIPPED_LIVE etherboot bug fix update 2010-03-29 12:34:41 UTC

Description Jia Dong 2009-07-15 15:52:10 UTC
Description of problem:
When using etherboot zrom files to NIC boot with ne model,it failed to get ip address.Other models of virtio,rtl8139,e1000,pcnet32 are all ok to get ip address.


Version-Release number of selected component (if applicable):
rhel5.4 x86_64 etherboot-zroms-kvm-5.4.4-10.el5


How reproducible:
100%

Steps to Reproduce:
1.# qemu-img create rom.img 10G
2.# qemu-kvm -name 'pxe' -m 256 -vnc :10  -net nic,vlan=0,macaddr=00:11:22:33:44:00,model=ne2k_pci -net tap,vlan=0,ifname=pxe,script=/etc/qemu-ifup-switch -boot n
  
Actual results:
It couldn't get ip address and accessed to profile selection menu(we are using cobbler to test this)
It threw out:
Probing pci nic...
Probing isa nic...
[NE*000]
<sleep>


Expected results:
Should get ip address and accessed to profile selection menu.

Additional info:
Using that commands above,virtio,rtl8139,pcnet32,e1000 all work well.

Comment 3 Naphtali Sprei 2009-09-17 14:09:51 UTC
reproduced by running qemu-kvm from package qemu-system-x86-0.10.6-1 (from the lfarkas repository) the with following params:
-boot n -name 'pxe' -m 256 -vnc :10  -net nic,vlan=0,macaddr=00:11:22:33:44:00,model=ne2k_pci   -net tap,vlan=0

The installed package has a soft-link from /usr/share/qemu/pxe-ne2k_pci.bin to ../etherboot/ne.zrom, which is the one used for this nic.

Replacing the file /usr/share/etherboot/ne.zrom from the package etherboot-zroms-kvm-5.4.4-16.el5 with the latest pc-bios/pxe-ne2k_pci.bin of the qemu-kvm git repository solves the problem.

Comment 4 Naphtali Sprei 2009-09-22 10:56:35 UTC
Created attachment 362067 [details]
etherboot zrom generated from rom-o-matic site for the ne2k-pci

generated from rom-o-matic site, on 22-September-2009, etherboot format,  5.4.4(i386),  rtl8029.zrom, default values suggested by site, except for: ASK_BOOT=-1, PXE_DHCP_STRICT selected

Comment 5 Naphtali Sprei 2009-09-22 11:01:15 UTC
zrom attached solves the problem: network boot works fine.

Comment 6 Naphtali Sprei 2009-09-27 09:55:49 UTC
The etherboot package should put the rtl8029 images in the kvm supported part.
The kvm package should point the ne2k-pci pxe file[s] to the rtl8029 from the etherboot package.

Comment 7 Eduardo Habkost 2009-09-28 21:54:33 UTC
bug 526124 was created for the kvm side of the changes.

Comment 9 Lawrence Lim 2009-10-08 14:10:56 UTC
Moving to ON_QA for bug verification to take place.

Comment 12 koka xiong 2009-12-18 05:17:13 UTC
Having verified on 
Red Hat Enterprise Linux 5Server-VT - x86_64
Red Hat Enterprise Linux 5Client-VT - x86_64
1.# qemu-img create rom.img 10G
2.# qemu-kvm -name 'pxe' -m 256 -vnc :10  -net
nic,vlan=0,macaddr=00:11:22:33:44:00,model=ne2k_pci -net
tap,vlan=0,ifname=pxe,script=/etc/qemu-ifup-switch -boot n
It can boot from network well.

Comment 14 errata-xmlrpc 2010-03-30 08:20:00 UTC
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/RHBA-2010-0227.html


Note You need to log in before you can comment on or make changes to this bug.