+- Stresslinux community (https://www.stresslinux.org/community)
+-- Forum: Stresslinux Main (https://www.stresslinux.org/community/forumdisplay.php?fid=1)
+--- Forum: General discussion (https://www.stresslinux.org/community/forumdisplay.php?fid=2)
+--- Thread: PXE boot not working (/showthread.php?tid=191)
PXE boot not working - zallik - 08-12-2013
Hello
I'm using a PXELINUX on a Windows 2008 r2 WDS server.
I have it set up to what i think should work (followed the defaults), but I'm still unable to get it to boot.
When i select the option, it tells me its loading the files, then it returns to the boot menu.
I have placed the files from stresslinux_11.4.x86_64-0.7.190-Build1.10-pxe into a folder called image
They are being loaded correctly, but it doesn't boot, just returns to the menu.
I tired other options but they didnt work.
Im not sure what the KIWI folder did, but i added it aswell.
My default file is as follows
DEFAULT vesamenu.c32
PROMPT 0
MENU TITLE PXE Boot Menu
MENU INCLUDE pxelinux.cfg/graphics.conf
MENU AUTOBOOT Starting Local System in 8 seconds
LABEL stresslinux
MENU LABEL ^Stresslinux x86-64 0.7.177
KERNEL image/initrd-netboot-suse-11.4.x86_64-2.1.1.kernel
APPEND initrd=image/initrd-netboot-suse-11.4.x86_64-2.1.1.gz ramdisk_size=1101824
## I have then tried to use the USB image to boot instead (not worked)
LABEL Stress2
MENU LABEL Stress2Lable
KERNEL memdisk
APPEND initrd=stresslinux.raw
##I then tried the ISO, which stopped at "Loading boot sector ..Booting..."
LABEL Stress3
MENU LABEL Stress 3
KERNEL memdisk
append initrd=stresslinux_64bit_11.4.x86_64-0.7.106.iso
RE: PXE boot not working - stresslinux - 08-12-2013
Hello zallik,
i never tried to boot stresslinux from a windows based pxe environment, but maybe you can try to replace / with \ in all paths
see http://www.syslinux.org/wiki/index.php/WDSLINUX
You say it jumps back to menu, you mean your pxe menu? If so it normally never loaded any kernel/initrd and the slashes may be
the cause.
Also you need at least the config.default file in the KIWI folder, without that the root image can't be loaded during boot.
RE: PXE boot not working - zallik - 08-13-2013
[quote='stresslinux' pid='325' dateline='1376333804']
Hello zallik,
i never tried to boot stresslinux from a windows based pxe environment, but maybe you can try to replace / with \ in all paths
see http://www.syslinux.org/wiki/index.php/WDSLINUX
You say it jumps back to menu, you mean your pxe menu? If so it normally never loaded any kernel/initrd and the slashes may be
the cause.
Also you need at least the config.default file in the KIWI folder, without that the root image can't be loaded during boot.
[/quote]
It seams to be loading the files ok, as it loads them then says ... OK
Can you explain what the KIWI folder does. None of my other images need this. Does the boot folder also need to be shared?
I have a variety of other boot images, and they all work fine.
It loads the kernal, says ok, then takes a while to load the initrd, then goes to back to the menu.
My KIWI\config.default file
IMAGE=/dev/ram1;stresslinux_11.4.x86_64;0.7.177;10.10.10.1;4096;compressed
My whole default file
DEFAULT vesamenu.c32
PROMPT 0
MENU TITLE PXE Boot Menu
MENU INCLUDE pxelinux.cfg/graphics.conf
MENU AUTOBOOT Starting Local System in 8 seconds
# Option 1 - Exit PXE Linux & boot normally
LABEL bootlocal
menu label ^Boot Normally
menu default
localboot 0
timeout 80
TOTALTIMEOUT 9000
# Option 2 - Run WDS
LABEL wds
MENU LABEL ^Windows Deployment Services
KERNEL pxeboot.0
# Option 3 - Exit PXE Linux
LABEL Abort
MENU LABEL E^xit
KERNEL abortpxe.0
LABEL SpinRite
MENU LABEL SpinRite
KERNEL memdisk
APPEND initrd=Spinrite.img
LABEL Memtest
MENU LABEL Memtest
KERNEL memdisk
APPEND initrd=memtest.img
LABEL dban
KERNEL dban.bzi
APPEND nuke="dwipe" silent vga=785
LABEL Clonezilla
MENU LABEL ^Clonezilla BootDisk
KERNEL memdisk
append initrd=clonezilla-live-2.1.1-25-amd64.iso
LABEL CPUSTRESS
MENU LABEL CPUSTRESS
KERNEL bzImage
APPEND initrd=initrd.gz noapic ubcdcmd=burn
LABEL stresslinux
MENU LABEL ^Stresslinux x86-64 0.7.177
KERNEL image/initrd-netboot-suse-11.4.x86_64-2.1.1.kernel
APPEND initrd=image/initrd-netboot-suse-11.4.x86_64-2.1.1.gz ramdisk_size=1101824
LABEL Stress2
MENU LABEL Stress2Lable
KERNEL memdisk
APPEND initrd=stresslinux.raw
LABEL Stress3
MENU LABEL Stress 3
KERNEL memdisk
append initrd=stresslinux_64bit_11.4.x86_64-0.7.106.iso
[hr]
This is why i think it is finding the files. <attached pic>
RE: PXE boot not working - stresslinux - 08-15-2013
maybe it's just the ip address in config.default "10.10.10.1" which needs to be changed to your tftp servers address or does it really use 10.10.10.1 ?
RE: PXE boot not working - stresslinux - 08-15-2013
the KIWI dir holds config.default or config.<mac-address> with details on what image (root fs) to load after initrd, more information about this can be found in kiwi documentation at http://doc.opensuse.org/projects/kiwi/doc/#sec.pxe.client-config-file
As most other Liveimages (like Clonezilla) are not build with kiwi, they do not use that structure.
RE: PXE boot not working - kanita - 12-12-2014
I've finally succeeded in downloading the 64-bit version of the ISO image, too, and I have some space to spare on my web server. Would you mind me making the two ISO images available for download on this server and, perhaps, on amule, and would you provide alternative download links on your download page which point to the two files on my web server? I do not have a paid bittorrent or rapidshare account, which, AFAIK, is needed when one wishes to upload large files to these networks.