Bug Reports, Requests, HowTo's about Tiny PXE Server

Erwan,

Indeed, initrd should be before kernel.

After making this change, the target started to load the image (I can see the percentage going up, until it says ok).

However, there's still something wrong with the script.

It insists that /memdisk operation is not supported:

BTW, ipxe.pxe was much quicker than ipxe-undionly.kpxe to load the image.

Which disk image are your loading? "mine" or "yours".

Attaching mine again.

Also, just to be sure, the kernel line is kernel /memdisk raw not /memdisk raw right?

And memdisk (file from syslinux 3.86) is in the Tiny PXE Server folder right? just next to the pxe boot loader.

Regards,

Erwan

EDIT : you should get the below screen if you boot "my" disk image.

I guess once we are done, I should write a clear "how to" as this is not as easy as it looks

The tutorial could cover how to make a bootable disk image as well. 

Erwan,

Finally, success!

Tried both ipxe-undionly.kpxe and ipxe.pxe.

As I mentioned earlier, ipxe.pxe loads the image very quickly.

My problem was that I somehow moved some files from "files" dir to TPS main dir. Fixed now.

I also have another important question:

 

Is it somehow possible to have the host PC (the one running the PXE server) to control the target machine using the host's monitor and keyboard?

What I mean is - After I manage to boot the target machine via PXE LAN, I want to see the output of its monitor on my PC's monitor, and control the target machine with my PC's keyboard (like VNC, RDP, etc).

 

This is useful when the target machine is not in the same room, and I need to boot it, control it and monitor it - all from my PC.

 

I heard that some recent Intel chipsets allow this sort of control, but all my target machines are old and don't even have an Intel chipset.

Since you are using Norton Ghost, you are out of luck. There is no solution for DOS except Norton PCAnywhere, I think. That's why I never considered using Norton Ghost or other DOS based disk cloning utility.

On the other hand Linux does have built in network functions. So it is relatively easy to create image with LAN, DHCP and SSHD server. My choice was SystemRescue CD.

Erwan,

 

Finally, success!

 

  

 

 

Tried both ipxe-undionly.kpxe and ipxe.pxe.

As I mentioned earlier, ipxe.pxe loads the image very quickly.

 

My problem was that I somehow moved some files from "files" dir to TPS main dir. Fixed now.

Hi Erircgl,

Happy it worked out for you !

Hope this will make life easier for your colleagues then.

You are correct : ipxe.pxe is much quicker than the undi-only version. Thanks for the tip!

Sidenote, I have made a tutorial on how to make a bootdisk disk image here to cover the first part of your scenario.

I will soon make a second tutorial to cover the second part (PXE boot).

Regards,

Erwan

First part of Ericgl scenario (disk image) explained here.

Second part (PXE boot) explained here.

Regards,

Erwan

Erwan,

What is HTTPd used for? I don't see an explanation anywhere.

Actually, you should write a brief explanation on what each option on top does, and why it's needed.

Thanks.

Hi Ericgl, Good point.

By default, a PXE server simply uses TFTP as file transfer protocol.

But TFTP is rather slow.

That's why I have added a HTTP daemon as an option in TinyPXE Server.

Whenever you want to achieve higher speed, you can there enable HTTPd.

You then need to adapt your ipxe script like below

#!ipxe
set boot-url http://${next-server}
initrd ${boot-url}/images/test.vhd
kernel ${boot-url}/memdisk raw
boot

/Erwan

Erwan,

I think that the line initrd is not correct.

You should add a parameter that indicates where PXE Server is running from, not only the IP of the server.

For example, I have PXE Server running from drive H: . 

We need something like:

initrd ${boot-url}/${PATH_TO_TPS_DIR}/images/test.vhd

 

Erwan,

 

I think that the line initrd is not correct.

You should add a parameter that indicates where PXE Server is running from, not only the IP of the server.

For example, I have PXE Server running from drive H: . 

We need something like:

initrd ${boot-url}/${PATH_TO_TPS_DIR}/images/test.vhd

Uhm, I have to disaggree there : TPS HTTP server is actually serving / exposing the folder (and files below) containing your boot filename.

Lets say TPS runs in C:\TPS but you picked up ipxe.pxe which is in H:\PXE, then ${boot-url} will actually point to H:\PXE.

The folder where TPS runs is actually not relevant.

The folder where your bootfilename is located is relevant.

This folder (lets call it root) is determined when you select the boot filename and go online.

When you click online, TPS will actually tell you where your root folder is (=http/tftp root).

You can also automatize it thru the config.ini.

Therefore if your images are (should be) in H:\PXE\IMAGES, the correct initrd will be initrd ${boot-url}/images/whatever.img.

My best advice thus is that you run it all in one unique folder.

Erwan,

 

What is HTTPd used for? I don't see an explanation anywhere.

Actually, you should write a brief explanation on what each option on top does, and why it's needed.

 

Thanks.

It's quite simple, in fact. When you need a certain service for a certain software you are turning the ones you are needing on.

For an instance, SystemRescue CD does use HTTPd as the default way to download filesystem image. It is possible to use TFTP but HTTP is many times faster. Still TFTP is used to download the kernel.

The strongest point of the Tiny PXE Server is large amount of different services available in just one user interface. When one needs to boot something over the network, some services are necesary to do so. DHCP and TFTP are a must, but different solutions require different additional services. Tiny PXE Server does have the most popular ones included, and this makes it a valuable asset for anyone, who tried to boot something over the network.

Edited by Sfor, 11 March 2014 - 03:22 PM.

Thank you very much Sfor

I would not have described it better !

In a previous post, Sfor was mentionning SystemRescueCD.

I decided to give a look at it.

I made a tutorial here : TinyPXE Server : PXE boot SystemRescueCD over HTTP.

On the same site, you will find similar articles on gParted, CloneZilla, Partition Wizard and Redo Backup Recovery.

/Erwan

Well. It is possible to boot the SystemRescueCD that way, but there will be no SystemRescueCD boot menu and all the tolls launched from it will be unaccessible.

As a matter of fact, the SystemRescueCD does have ability to act as a PXE server. The idea is to run the SystemRescueCD on one computer, configure the PXE server, then boot the system rescue CD over the network. But, it is a drag to do so. It is much simpler to let the SystemRescueCD prepare the PXE file set, copy it to a Windows based computer, then to use it along with Tiny PXE Server. It's much faster and simpler, at least in my opinion.

Since the SystemRescueCD does have it's own PXE boot menu and code, it is enough to set the pxelinux.0 as the boot file filename from the PXE ready set of files, enable HTTPd and all the SystemRescueCD functions along with all it's tools' images are available, just like they would be booted from a CD.

Edited by Sfor, 12 March 2014 - 08:05 PM.

Hi Sfor,

Thanks for the feedback.

Can you tell me more about missing tools when booted this way?

When I look at the iso/cd, I dont see much difference with the PXE Boot : initrd/kernel loading sysrescue.dat (a squashfs I guess like other similar distros).

I have tested the web browser, the file manager, gparted, etc and so far so good.

My main drive was to get another alternative to PartedMagic which unfortunately is no longer free.

Regards,

Erwan

The ones I can not live without are Memtest and MHDD. But there are a few other images booted separately from the main Linux distribution. Depending on the version there are FreeDOS, Ranish Partition Manager, Grub disk, GAG, Aida, Hardware Detect Tool and others.

Ah ok; I see what you mean now.

In the bootdisk folder indeed I can see (called from the isolinux cd boot menu) : aida, dban, freedos, gag, grubdisk, hdt, memtestp, mhdd.

I guess we could boot these from iPXE as well.

Thanks for the tip.

1.0.0.17 out, minor version, mainly bugfixes based on users feedback

• fixed : should detect if a socket is already in use
• fixed : messages sent from threads would not always reach the memo box
• added : will execute an executable/batch if cmd parameter is present in config.ini (cmd=c:\path\binary.exe)
• fixed : httpd will handle both non keep-alive (default) and keep-alive http requests (needed for sanboot)
• fixed : would create crashes (under certain conditions) if the root path was incorrect

my english is bad

can do like hanewin this?

Automatically determine the UEFI PXE and BIOS PXE

if PXEClient:Arch:00000: DHCPserver send bios boot file

if PXEClient:Arch:00007: DHCPserver send uefi boot file

Hi ljycslg,

Have you checked ipxe variables list : http://ipxe.org/cfg ?

I am pretty sure you should find what you are looking for there.

Then it is "only" a matter of writing the ipxe script.

Tons of examples here for example.

Regards,

Erwan

hi,Erwan

i can't see my post ,why?

i read the ipxe script

I think it is impossible to achieve，can show me example 

Edited by ljycslg, 19 March 2014 - 01:18 PM.

i can't see my post ,why?

Your post has been "unapproved".

I looked into your profile and saw no flags like "spammer" or "banned" etc.

And the content is also not "forbidden".

So for me there is no reason to hide your posts.

I approved it (made visible for non-admin users)

Peter

some suggest

add FTP Transfer Protocl

start program auto online option

some suggest

add FTP Transfer Protocl

start program auto online option

put start=1 in config.ini in [dhcp] section.

i'll add ftp daemon shortly.