Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ipxe chain to vmware boot
2018-01-26, 00:43 (This post was last modified: 2018-01-26 00:54 by danishm.)
Post: #1
ipxe chain to vmware boot
Im trying to double chain ipxe as following: (i've compiled ipxe.efi with DOWNLOAD_PROTO_HTTPS enable)

First Chain:
#!ipxe
echo info chain http://IPaddr:PORT/ipxe/${net0/mac:hex}
chain http://IPaddr:PORT/ipxe/${net0/mac:hex}

Second Chain:
#!ipxe
echo +--------- ipxe ---------------------------------------------
echo | OS Install
echo | mac.................: ${mac}
echo | uuid................: ${uuid}
echo | serial..............: ${serial}
echo | ip..................: ${ip}
echo | manufacturer........: ${manufacturer}
echo | product.............: ${product}
echo +------------------------------------------------------------
imgfree
set next-server IPaddr2
set filename https://${next-server}:PORT/somedir/tramp
chain https://${next-server}:PORT/somedir/tramp

Inside this file: https://${next-server}:PORT/somedir/tramp
#!gpxe

set max-retries 6
set retry-delay 20
post /some-dir/host-register?bootmac=${mac}

Can I do that ?
If not is there an alternative way to do this ?

ERROR from ipxe:
https://IPaddr2:PORT/some-dir/tramp... Error 0x3e11618e (http://ipxe.org/3e11618e)
Could not boot: Error 0x3e11618e (http://ipxe.org/3e11618e)
Find all posts by this user
Quote this message in a reply
2018-01-26, 01:01
Post: #2
RE: ipxe chain to vmware boot
(2018-01-26 00:43)danishm Wrote:  https://IPaddr2:PORT/some-dir/tramp... Error 0x3e11618e (http://ipxe.org/3e11618e)
Could not boot: Error 0x3e11618e (http://ipxe.org/3e11618e)

Did you try reading the page that iPXE is telling you to read: http://ipxe.org/3e11618e?

Michael
Visit this user's website Find all posts by this user
Quote this message in a reply
2018-01-26, 15:29
Post: #3
RE: ipxe chain to vmware boot
Yes I did. But Im using IPaddresses strictly.
Find all posts by this user
Quote this message in a reply
2018-01-26, 15:52
Post: #4
RE: ipxe chain to vmware boot
(2018-01-26 15:29)danishm Wrote:  Yes I did. But Im using IPaddresses strictly.

You are using a URI that does not contain an IP address. If you use a URI containing an IP address, then iPXE will never attempt DNS resolution. The error that you are seeing is coming from the DNS resolver code. Therefore you have entered a URI that does not contain an IP address.

What is the actual URI that you are trying to use?

Thanks,

Michael
Visit this user's website Find all posts by this user
Quote this message in a reply
2018-01-26, 19:27
Post: #5
RE: ipxe chain to vmware boot
(2018-01-26 15:52)mcb30 Wrote:  You are using a URI that does not contain an IP address. If you use a URI containing an IP address, then iPXE will never attempt DNS resolution. The error that you are seeing is coming from the DNS resolver code. Therefore you have entered a URI that does not contain an IP address.

Just thinking out loud here... What would happen if one has
Code:
set net0/ip 192.168.0.100
set net0/netmask 255.255.255.0
ifopen net0
https://192.168.0.1/file

Wouldn't that require a roundtrip to ca.ipxe.org to get the certificate roots? and that could be the reason for any DNS lookup?

Read the FAQ before posting.
Did you include relevant ipxe.org error urls?
Visit this user's website Find all posts by this user
Quote this message in a reply
2018-01-26, 21:00 (This post was last modified: 2018-01-26 21:40 by danishm.)
Post: #6
RE: ipxe chain to vmware boot
@NiKiZe, u r right since Im using HTTPs its most probably trying to reach out to ca.ipxe.org for root certs and Im behind a firewall which doesn't let us go out.

Can I generate my own certs on the ipxe server if the vmware binary server is different ?
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)