+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: Recent Build HTTP Oddness (/showthread.php?tid=7850)
Recent Build HTTP Oddness - danberk - 2015-10-22 02:02
Hello!
I want to start with the devs here are great and do great work!
I did a new build today, after not doing one for a few months, and at first I was having a lot of issues getting http://ipxe.org/420c6001 errors. Then I switched to using Tomcat (which does have keep alive and chunking) as the backend HTTP server. Now it's working again but A TON slower than in the past. A 200mb image takes about 4 minutes to load. I am doing a wimboot, it get to the actual wim file really fast, then instantly goes to 100%, then down to 99%, stays there for the 4 minutes, then boots fine.
Any thoughts?
Dan
RE: Recent Build HTTP Oddness - mcb30 - 2015-10-22 09:18
(2015-10-22 02:02)danberk Wrote: I did a new build today, after not doing one for a few months, and at first I was having a lot of issues getting http://ipxe.org/420c6001 errors. Then I switched to using Tomcat (which does have keep alive and chunking) as the backend HTTP server. Now it's working again but A TON slower than in the past. A 200mb image takes about 4 minutes to load. I am doing a wimboot, it get to the actual wim file really fast, then instantly goes to 100%, then down to 99%, stays there for the 4 minutes, then boots fine.
Could you post a copy of the iPXE script that you are using to load wimboot, and a screenshot of the output when it's stuck on 99% progress?
Thanks,
Michael
RE: Recent Build HTTP Oddness - danberk - 2015-10-22 17:05
Here is the wimboot script. Note this has never been a problem before and I have been using this for over a year in different configs.
:generic
echo Booting Generic Ghost Image
kernel ${boot-server}/windowsboot/wimboot
initrd ${boot-server}/images/Generic_v2/bootmgr bootmgr
initrd ${boot-server}/images/Generic_v2/boot/bcd BCD
initrd ${boot-server}/images/Generic_v2/boot/boot.sdi boot.sdi
initrd ${boot-server}/images/Generic_v2/sources/boot.wim boot.wim
boot
https://www.dropbox.com/s/ro6g54q8ft7z1qr/iPXE.mov?dl=0
I uploaded a 15 second video (forum wouldnt allow upload) of it booting, the video is of a VM, but the exact same thing, happens with multiple Dell laptops I have tried with. Different ones from realtek chipsets to intel. If you look at 13 seconds in, it flickers to 100% then goes back.
RE: Recent Build HTTP Oddness - mcb30 - 2015-10-29 15:43
(2015-10-22 17:05)danberk Wrote: https://www.dropbox.com/s/ro6g54q8ft7z1qr/iPXE.mov?dl=0
I uploaded a 15 second video (forum wouldnt allow upload) of it booting, the video is of a VM, but the exact same thing, happens with multiple Dell laptops I have tried with. Different ones from realtek chipsets to intel. If you look at 13 seconds in, it flickers to 100% then goes back.
Thanks. That is strange. Could you try building iPXE with DEBUG=httpcore:3 and see what the debug output says?
Michael
RE: Recent Build HTTP Oddness - danberk - 2015-10-30 17:42
Hi! Thanks for helping
Here is a new clip with that output, about 15 seconds in you see my background change, that is because I cut 7 minutes of it sitting there and going between 99% and 100% out. Also I did a packet capture, and about halfway through it switched from a packet length of 1500ish bytes to 1254, which I thought was odd because its a virtual network thus shouldnt have packet loss.https://www.dropbox.com/s/ogvqdvl2cy16fb0/iPXE2_trimmed.mov?dl=0
RE: Recent Build HTTP Oddness - danberk - 2015-10-30 21:14
I dont know if it helps, but I set my server to disable keep alives, and this is the new output.
https://www.dropbox.com/s/srx6hyqo850fe5r/Screen%20Shot%202015-10-30%20at%204.12.00%20PM.png?dl=0
RE: Recent Build HTTP Oddness - danberk - 2015-11-13 21:06
@mcb30 Anything I can do to help in the investigation of this?
RE: Recent Build HTTP Oddness - danberk - 2015-12-16 02:04
HI! Good news! I fixed it. With the newer HTTP core in iPXE and my HTTP server, I was not sending content-size, and that was causing my problem. Added it and it worked!