New ipxe tarball

New ipxe tarball

[Boris Ostrovsky]

Looks like new ipxe tarball disappeared from xenbits:

ostr:/tmp$  /usr/bin/wget -c -O _ipxe.tar.gz http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
--2016-10-16 09:07:20--  http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
Resolving xenbits.xen.org (xenbits.xen.org)... 104.239.192.120
Connecting to xenbits.xen.org (xenbits.xen.org)|104.239.192.120|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-10-16 09:07:20 ERROR 404: Not Found.

ostr:/tmp$ 


I can see the previous version (ipxe-git-9a93db3...) but not the new one.


-boris

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: New ipxe tarball

[Wei Liu]

Ian might be able to help with this.

On Sun, Oct 16, 2016 at 06:10:47AM -0700, Boris Ostrovsky wrote:
> Looks like new ipxe tarball disappeared from xenbits:
> 
> ostr:/tmp$  /usr/bin/wget -c -O _ipxe.tar.gz http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
> --2016-10-16 09:07:20--  http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
> Resolving xenbits.xen.org (xenbits.xen.org)... 104.239.192.120
> Connecting to xenbits.xen.org (xenbits.xen.org)|104.239.192.120|:80... connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2016-10-16 09:07:20 ERROR 404: Not Found.
> 
> ostr:/tmp$ 
> 
> 
> I can see the previous version (ipxe-git-9a93db3...) but not the new one.
> 
> 
> -boris

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: New ipxe tarball

[Ian Jackson]

Wei Liu writes ("Re: New ipxe tarball"):
> On Sun, Oct 16, 2016 at 06:10:47AM -0700, Boris Ostrovsky wrote:
> > Looks like new ipxe tarball disappeared from xenbits:

It was never there.

> > ostr:/tmp$  /usr/bin/wget -c -O _ipxe.tar.gz http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
> > --2016-10-16 09:07:20--  http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
> > Resolving xenbits.xen.org (xenbits.xen.org)... 104.239.192.120
> > Connecting to xenbits.xen.org (xenbits.xen.org)|104.239.192.120|:80... connected.
> > HTTP request sent, awaiting response... 404 Not Found
> > 2016-10-16 09:07:20 ERROR 404: Not Found.
> > 
> > ostr:/tmp$ 
> > 
> > I can see the previous version (ipxe-git-9a93db3...) but not the new one.

The code (AFAICT from looking at tools/firmware/etherboot/Makefile)
first tries to download the tarball, and if that fails, uses git
clone.

Does the lack of the tarball cause your actual build to fail ?

I think it's probably sensible to retain this "try tarball first"
arrangement but we should provide a tarball at least for tag mentioned
in the release versions of Xen.

Wei, are we expecting to update IPXE_GIT_TAG again ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: New ipxe tarball

[Wei Liu]

On Mon, Oct 17, 2016 at 12:12:06PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Re: New ipxe tarball"):
> > On Sun, Oct 16, 2016 at 06:10:47AM -0700, Boris Ostrovsky wrote:
> > > Looks like new ipxe tarball disappeared from xenbits:
> 
> It was never there.
> 
> > > ostr:/tmp$  /usr/bin/wget -c -O _ipxe.tar.gz http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
> > > --2016-10-16 09:07:20--  http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
> > > Resolving xenbits.xen.org (xenbits.xen.org)... 104.239.192.120
> > > Connecting to xenbits.xen.org (xenbits.xen.org)|104.239.192.120|:80... connected.
> > > HTTP request sent, awaiting response... 404 Not Found
> > > 2016-10-16 09:07:20 ERROR 404: Not Found.
> > > 
> > > ostr:/tmp$ 
> > > 
> > > I can see the previous version (ipxe-git-9a93db3...) but not the new one.
> 
> The code (AFAICT from looking at tools/firmware/etherboot/Makefile)
> first tries to download the tarball, and if that fails, uses git
> clone.
> 

Yes.

> Does the lack of the tarball cause your actual build to fail ?
> 
> I think it's probably sensible to retain this "try tarball first"
> arrangement but we should provide a tarball at least for tag mentioned
> in the release versions of Xen.
> 

I agree.

> Wei, are we expecting to update IPXE_GIT_TAG again ?
> 

No, not for this release.

I expect ipxe to be configurable just like qemu in the next release.

Wei.

> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: New ipxe tarball

[Boris Ostrovsky]

On 10/17/2016 07:12 AM, Ian Jackson wrote:
> Wei Liu writes ("Re: New ipxe tarball"):
>> On Sun, Oct 16, 2016 at 06:10:47AM -0700, Boris Ostrovsky wrote:
>>> Looks like new ipxe tarball disappeared from xenbits:
> It was never there.
>
>>> ostr:/tmp$  /usr/bin/wget -c -O _ipxe.tar.gz http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
>>> --2016-10-16 09:07:20--  http://xenbits.xen.org/xen-extfiles/ipxe-git-827dd1bfee67daa683935ce65316f7e0f057fe1c.tar.gz
>>> Resolving xenbits.xen.org (xenbits.xen.org)... 104.239.192.120
>>> Connecting to xenbits.xen.org (xenbits.xen.org)|104.239.192.120|:80... connected.
>>> HTTP request sent, awaiting response... 404 Not Found
>>> 2016-10-16 09:07:20 ERROR 404: Not Found.
>>>
>>> ostr:/tmp$ 
>>>
>>> I can see the previous version (ipxe-git-9a93db3...) but not the new one.
> The code (AFAICT from looking at tools/firmware/etherboot/Makefile)
> first tries to download the tarball, and if that fails, uses git
> clone.
>
> Does the lack of the tarball cause your actual build to fail ?

Yes it did but now that I looked at the logs more carefully it failed
because both wget *and* clone failed, the latter was due to DNS lookup
failure, most likely some sort of intermittent error since it didn't
happen on a subsequent build this morning.

But (as you said below) we should be able to fetch the file that the
Makefile references. (I didn't realize it was never put up there because
presumably git clone worked until the DNS hiccup here).

-boris


>
> I think it's probably sensible to retain this "try tarball first"
> arrangement but we should provide a tarball at least for tag mentioned
> in the release versions of Xen.
>
> Wei, are we expecting to update IPXE_GIT_TAG again ?
>
> Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: New ipxe tarball

[Ian Jackson]

Boris Ostrovsky writes ("Re: New ipxe tarball"):
> But (as you said below) we should be able to fetch the file that the
> Makefile references. (I didn't realize it was never put up there because
> presumably git clone worked until the DNS hiccup here).

I've arranged for an apparently-correct file to be in the right place,
and it seems to WTFM.  (I checked the file's contents corresponded to
the git commit in Config.mk but have not verified the provenance of
that git commit hash.)

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Re: New ipxe tarball

[Boris Ostrovsky]

On 10/17/2016 11:35 AM, Ian Jackson wrote:
> Boris Ostrovsky writes ("Re: New ipxe tarball"):
>> But (as you said below) we should be able to fetch the file that the
>> Makefile references. (I didn't realize it was never put up there because
>> presumably git clone worked until the DNS hiccup here).
> I've arranged for an apparently-correct file to be in the right place,
> and it seems to WTFM.  (I checked the file's contents corresponded to
> the git commit in Config.mk but have not verified the provenance of
> that git commit hash.)
>
> Ian.


Thanks. I did a sample build and run and it looks good for me too (I
verified that I pulled the tarball)


-boris

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel