Bug 1038630

Summary: make ipxe 256k for rhel7 machine types
Product: Red Hat Enterprise Linux 7 Reporter: Paolo Bonzini <pbonzini>
Component: ipxeAssignee: Paolo Bonzini <pbonzini>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: acathrow, flang, hhuang, juzhang, knoel, kraxel, michen, mrezanin, pbonzini, qiguo, qzhang, virt-maint, xwei
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipxe-20130517-3.gitc4bce43.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1038604 Environment:
Last Closed: 2014-06-13 13:24:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1038603, 1038604    
Bug Blocks:    

Comment 3 langfang 2014-01-22 13:28:41 UTC
Hi, Paolo
   There are 3 bugs for different component(bug 1038630(ipxe),bug 1038603(seabios),bug 1038603(qemu-kvm).As you said,for this bug "This is important if we want to support UEFI on RHEL/KVM". I have two prolbems
   1)Using the fixed qemu-kvm and seabios version,what's the differents between 
fixed version(for this bug) and not fixed version(for this bug)?
   2)how can i check the  "256k " file  for ipxe.



thanks 

fanglang

Comment 4 Paolo Bonzini 2014-01-22 13:51:29 UTC
There is no difference.  It's just a preparation for future changes.

To test it, check that the files installed in /usr/share/ipxe are 256k in size.

Comment 5 langfang 2014-01-24 06:37:23 UTC
Hi Paolo
     thanks for your help .

Reproduce this bug as follow version:
Host:
# uname -r
3.10.0-64.el7.x86_64
# rpm -qa |grep ipxe
ipxe-bootimgs-20130517-2.gitc4bce43.el7.noarch
ipxe-roms-20130517-2.gitc4bce43.el7.noarch
ipxe-roms-qemu-20130517-2.gitc4bce43.el7.noarch

Steps:
#cd /usr/share/ipxe
#ll 
....
-rw-r--r--. 1 root root   66048 Dec 28 13:22 10b74500.rom
-rw-r--r--. 1 root root   66560 Dec 28 13:22 10b75900.rom
-rw-r--r--. 1 root root   66560 Dec 28 13:22 10b75950.rom
-rw-r--r--. 1 root root   66560 Dec 28 13:22 10b75951.rom
-rw-r--r--. 1 root root   66560 Dec 28 13:22 10b75952.rom
-rw-r--r--. 1 root root   66048 Dec 28 13:22 10b76055.rom
-rw-r--r--. 1 root root   66048 Dec 28 13:22 10b77646.rom
-rw-r--r--. 1 root root   67584 Dec 28 13:22 10b77770.rom
-rw-r--r--. 1 root root   70656 Dec 28 13:22 10b780eb.rom
-rw-r--r--. 1 root root   66048 Dec 28 13:22 10b79000.rom
...

Results:rom files size not 256K'

verify this bug as follow version
Host:
# uname -r
3.10.0-64.el7.x86_64
# rpm -qa |grep ipxe
ipxe-bootimgs-20130517-3.gitc4bce43.el7.noarch
ipxe-roms-20130517-3.gitc4bce43.el7.noarch
ipxe-roms-qemu-20130517-3.gitc4bce43.el7.noarch

#cd /usr/share/ipxe

#ll
..
-rw-r--r--. 1 root root  262144 Jan 16 15:35 808610f0.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 808610f5.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 808610f6.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 808610fb.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 808610fe.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861209.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861227.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861228.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861229.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861501.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861502.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 80861503.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 8086150a.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 8086150c.rom
-rw-r--r--. 1 root root  262144 Jan 16 15:35 8086150d.rom
...

Results:
all the *.rom files size are 256k

According to above test ,this bug fixed

Comment 6 juzhang 2014-01-24 08:27:51 UTC
According to comment5, set this issue as verified.

Comment 7 Ludek Smid 2014-06-13 13:24:54 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.