Questions[syslinux](server)

I am trying to install windows 10 via network boot on a VM (later on, I want to do that on real computers). Therefore I use Debian 9 and VMWare 12.

On my Debian system I have implemented an isc-dhcp-server and a tftpd-hpa-server. On top of that I have syslinux. I changed the menu so that I am able to boot Debian 10 and Kali-Linux via network with images from netboot. This works fine.

Nevertheless, I am not able to boot a windows 10 iso. My file looks as follows:

label install
    menu label ^Install
    kernel windows10-installer/amd64/memdisk
    initrd windows10-installer/amd64/win10pe.iso
    append iso raw

I created the win10pe.iso from a windows 10 iso by mounting it to a startup script as explaind in this link https://wiki.archlinux.org/index.php/Windows_PE. Therefore I used the package mkwinpeimg.

When I choose windows 10 to boot, I can see:

Loading /memdisk... ok
Loading /winpe10.iso...

After one or two minutes the following error message appears:

e820: 00000000fffe0000 0000000000020000 2
e820: 0000000100000000 0000000040000000 1
RAMdisk at 0xa833b000, length 0x17ba5000
command line: BOOt_IMAGE=/memdisk iso raw initrd=/win10pe.iso
MEMDISK: IMAGE seems to have fractional end cylinder
MEMDISK: IMAGE appears to be truncated
Disk is hd96, 97189 K, C/H/S = 65535/255/15 (E1 Torito/E1 Torito), EDD on, rw
Using raw access to high memory 
Code 1860, meminfo = 264, cmdline 98, stack 512
Total size needed = 2734 bytes, allocating 3K
Old dos MEMORY at 0x9f000 (map says 0x09f000), loading 0x9e400
1588: 0xfff   15E801:  0x3c00 0xa733
INT 13 08: Success, count = 1, BPT = 0000:0000
Drive probing gives drive shift limit: 0xe1
old: int13 = cd00012b  int15 = f000f895  int1e = f000efc7
new: int13 = 9e40000a  int15 = 9e4003fd  int1e = f000efc7
Loading boot sector... booting...
CDBOOT: Cannot boot from CD - Code: 5
_ 

I am not sure what I have done wrong. Is there a mistake with my winpe or my startup script or is ca. 300MB to much for my ftp server? I have also read something about gpxelinux.0 instead of pxelinux.0, but I do not know where tp get gpxelinux.0. Any help is appreciated. Thanks in advanche.

Does anyone know how i could shutdown ACPI Bios computer (without APM) using Syslinux ?

This is the configuration I am using :

 LABEL Shutdown
    MENU LABEL ^Shutdown computer
    KERNEL /tools/poweroff.c32
    TEXT HELP
        Shutdown the computer
    ENDTEXT 

On a non-APM Bios computer I got the error:

 APM not present

I heard that new Bios use most of the time ACPI instead of APM. So i tried acpioff.c32 from https://launchpadlibrarian.net/187530745/acpioff.c32

and replaced poweroff.c32 with it

 mv acpioff.c32 poweroff.c32

But i got the error :

 Failed to load com32 poweroff.c32

Maybe it require some dependencies? but I didn't found them...

I tested it from CDRom, USB Key and LPXE with the same result

Does anyone know how I could have shutdown works on ACPI using Syslinux ?

Thanks

PS

I already tried COM32 instead of KERNEL, but it is the same as said in : http://www.syslinux.org/wiki/index.php?title=SYSLINUX#KERNEL_file

KERNEL recognized extension (case sensitive)

.0 PXE bootstrap program (NBP) [PXELINUX only] .bin "CD boot sector" [ISOLINUX only]

.bs Boot sector [SYSLINUX only]

.bss Boot sector, DOS superblock will be patched in [SYSLINUX only]

.c32 COM32 image (32-bit COMBOOT)

.cbt COMBOOT image (not runnable from DOS)

.com COMBOOT image (runnable from DOS)

.img Disk image [ISOLINUX only]

I tried with Syslinux libraries from BIOS folder and EFI64 with the same result

This is the list of file I included :

A variety of machines will happily boot a custom bzImage via PXE in legacy mode using syslinux.

In UEFI mode, one of these machines and a newer UEFI only board get assigned an IP address, TFTP syslinx.efi from the server and then freeze.

Now I'm not quite sure why the freeze.

There are no further TFTP requests as seen when using pxelinux.0.

Wireshark shows that the machine is sending the correct PXE/BOOTP extension for an x64 machine PXEClient:Arch:00007:UNDI:003016.

The syslinux.efi binary is x64 build from the 6.03 sources.

Is syslinux.efi even the correct loader? Any thoughts welcomed.

I am working on a mock up of a PXE server for the place I work. I am trying to put the image files and configuration file in places that keep things a little more organized. Even though my dhcpd.confspecifies the configuration options needed to tell PXELinux where to look for config files it still does not find said files.

Here is what my /etc/dhcp/dhcpd.conf looks like, this is where I imagine the issue is.

option space PXE;
option PXE.mtftp-ip             code 1 = ip-address;
option PXE.mtftp-cport          code 2 = unsigned integer 16;
option PXE.mtftp-sport          code 3 = unsigned integer 16;
option PXE.mtftp-tmout          code 4 = unsigned integer 8;
option PXE.mtftp-delay          code 5 = unsigned integer 8;
option arch                     code 93 = unsigned integer 16;

option space pxelinux;
option pxelinux.magic                   code 208 = string;
option pxelinux.configfile              code 209 = text;
option pxelinux.pathprefix              code 210 = text;
option pxelinux.reboottime              code 211 = unsigned integer 32;

ddns-update-style none;

option domain-name "lab.solignis.com";
option domain-name-servers ns01.lab.solignis.com;

default-lease-time 600;
max-lease-time 7200;

authoritative;
log-facility local7;

subnet 192.168.147.0 netmask 255.255.255.0 {
        range 192.168.147.100 192.168.147.254;
        option subnet-mask 255.255.255.0;
        option routers 192.168.147.2;
        option broadcast-address 192.168.147.255;
        default-lease-time 600;
        max-lease-time 7200;

        class "pxeclients" {

                match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";
                next-server 192.168.147.10;

                if option arch = 00:00 {
                        option pxelinux.configfile "common.cfg";
                        option pxelinux.pathprefix "/configs/";
                        filename "/pxelinux/images/BIOS/pxelinux.0";
                } elsif option arch = 00:06 {
                        #option pathprefix "/configs/";
                        #option configfile "/EFIx64/default";
                        filename "/images/EFIx64/syslinux.efi";
                } elsif option arch = 00:07 {
                        #option pathprefix "/configs/";
                        #option configfile "/EFIx64/default";
                        filename "/images/EFIx64/syslinux.efi";
                } elsif option arch = 00:09 {
                        #option pathprefix "/configs/";
                        #option configfile "/EFIx64/default";
                        filename "/images/EFIia32/syslinux.efi";
                }
        }

}

Parts of the config were compiled from various parts of documentation, the parts that are commented out are old pieces that I have not fixed yet disregard those. For now I just want to get standard BIOS working (arch = 00:00).

Here is what my file structure looks like for my tftpboot directory.

server01@server01:/var/lib/tftpboot$ tree
.
└── pxelinux
    ├── configs
    │   └── common.cfg
    └── images
        ├── BIOS
        │   ├── ldlinux.c32
        │   └── pxelinux.0
        ├── EFIia32
        │   └── syslinux.efi
        └── EFIx64
            └── syslinux.efi

6 directories, 5 files

I was pretty sure I have it setup right for pxelinux but it does not see the config file so something is not configured right. Can anyone provide an idea of what I misconfigured? I have been banging my head on this all day.

How do I check what version of syslinux I have?