When i boot via pxe the client, nothing is happening after download files
-
@keurky In the pictures we see that it downloads
undionly.kpxebut the boot messages definitely stem from an UEFI based system. You need to setipxe.efias boot file for those machines. You wanna head this: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-ExistenceAbout the legacy system. Not sure why it hangs. You might try using
ipxe.pxeinstead ofundionly.kpxefor that and see if it makes a difference. -
Hi Sebastian Roth,
Thank You for your answer. I will test this tomorrow.
Keurky
-
That Work on Legacy avec this file “undionly.kpxe” :
https://drive.google.com/file/d/1_HRH87klCVQ46raZDAeB8kwCdto0z8MR/view
But does’nt work in Uefi with to set ipxe.efi
I will tryfor boot with an Machin MAC for capture image sys.Thank you, I hope someone can find the solution to my problem rated UEFI
Keurky
-
@keurky Please test this with a real machine, not hyper V. I understand your goal may be to capture a hyper-v image, but we need to find out where the problem isn’t. Right now we don’t know if this is a hyper-v issue, a pxe boot kernel issue, or something else. We need to start removing things from the problem until we find the solution. So test with a uefi based real computer first.
I can tell you when ever you see something saying downloading “NBP” that is a UEFI bios. It expects a UEFI based boot loader like ipxe.efi. You CAN NOT boot a uefi based system with a bios boot loader i.e. undionly.kpxe.
-
@george1421 said in When i boot via pxe the client, nothing is happening after download files:
Please test this with a real machine, not hyper V. I understand your goal may be to capture a hyper-v image, but we need to find out where the problem isn’t. Right now we don’t know if this is a hyper-v issue, a pxe boot kernel issue, or something else. We need to start removing things from the problem until we find the solution. So test with a uefi based real computer first.
I can tell you when ever you see something saying downloading “NBP” that is a UEFI bios. It expects a UEFI based boot loader like ipxe.efi. You CAN NOT boot a uefi based system with a bios boot loader i.e. undionly.kpxe.@george1421 I want test via VirtualBOx, because where i work we need a Virutal Machine server fog. But i will test with a real machine after VirtualBOx.
Thank U, for your answer.
-
@keurky I’m only asking to test the target computer pxe booting with a real computer and not a VM. The issue is with the target computer uefi firmware not the FOG server.
And FWIW, virtualbox does not support (AFAIK) uefi firmware emulation. So you can’t test a uefi based image using virtualbox. For hyper-v it has to be a type 2 (sorry its probably the wrong word, but I don’t use hyper-v) virtual machine to support uefi.
-
@keurky said in When i boot via pxe the client, nothing is happening after download files:
I want test via VirtualBOx,
I am not sure if this is still correct with most current versions of Virtual Box but as far as I know Virtual Box cannot PXE boot in UEFI mode!
-
@george1421 No problem, i test with a Computer “real Machine” in EUFI (files ipxe.pxe) and that Work !!!
Thank you for your Help !
Source problem: Hyper-V
-
@keurky said in When i boot via pxe the client, nothing is happening after download files:
Source problem: Hyper-V
If you still want to test this on a VM, I’m pretty sure vmware workstation supports uefi clients (I know 100% sure that ESXi does because that is where I build my uefi reference images). I’m not sure about vmware player. I have not used that platform in a while.
-
@keurky I am fairly sure we have people in the forums using Hyper-V and are able to PXE boot in UEFI mode. Not that can prove it myself but. @x23piracy
-
@Sebastian-Roth Actually, on the latest VirtualBox it seems that there is a way to UEFI PXE boot now. (chipset ICH9 and network adapter type to virtio-net), but I haven’t really tested it any significant amount. It gets to the FOG menu at any rate.
