Hello Everyone
I was able to get everything ready to go following some of the
documentation from github https://github.com/kireevco/wimaging but now I am
having an issue with booting the VMs/Servers into wimboot with an error of:
Could not find kernel image: linux.c32
<https://lh3.googleusercontent.com/--SdfciPMUd0/VrToeCB6QxI/AAAAAAAAPeM/cA7KK-_MhCU/s1600/foreman3.jpg>
According to the MAC address file in /var/lib/tftpboot/pxelinux.cfg,
wimboot file should be in the boot directory (which is there) and the bcd,
bootsdi, and boot.wim (even bootmgr is there) under /var/lib/tftpboot/boot/
folder but I can't get any VM to boot into the Windows Installation
LABEL menu
COM32 linux.c32 boot/wimboot
APPEND
initrdfile=boot/windows-x64/bcd,boot/windows-x64/boot.sdi,boot/windows-x64/boot.wim
The proxy.log files show a 404 Error: Not Found so I guess what I am not
sure is why? the srvvannagios server is accessible and open without
security. I also don't understand the double slashes
"windows-pe-x64//wimboot" which doesn't seem make sense.
E, [2016-02-05T09:36:06.792481 #14336] ERROR – : [25387] 2016-02-05
09:36:06 ERROR 404: Not Found.
E, [2016-02-05T09:36:06.922288 #14336] ERROR – : [25395]
http://srvvannagios/pub/windows-pe-x64/sources/boot.wim:
E, [2016-02-05T09:36:06.922559 #14336] ERROR – : [25395] 2016-02-05
09:36:06 ERROR 404: Not Found.
E, [2016-02-05T09:36:11.396401 #14336] ERROR – : [25363]
http://srvvannagios/pub/windows-pe-x64//wimboot:
E, [2016-02-05T09:36:11.396551 #14336] ERROR – : [25363] 2016-02-05
09:36:11 ERROR 404: Not Found.
Has anyone setup wimaging corrrectly and tell me what I'm doing wrong?
Thank You
Joey
Ok so things changed a bit after I copied a very important file: linux.c32
from /usr/lib/syslinux/ to /var/lib/tftpboot/
However now I am getting an error like so:
Loading
initrdfile=boot/windows-x64/bcd,boot/windows-x64/boot.sdi,boot/windows-x64/boot.wim
…failed!!
Kernel load failure (insufficient memory?)
Anyone seen this before?
···
On Friday, February 5, 2016 at 10:28:29 AM UTC-8, Joey Jojo wrote:
>
> Hello Everyone
>
> I was able to get everything ready to go following some of the
> documentation from github https://github.com/kireevco/wimaging but now I
> am having an issue with booting the VMs/Servers into wimboot with an error
> of:
>
> Could not find kernel image: linux.c32
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> According to the MAC address file in /var/lib/tftpboot/pxelinux.cfg,
> wimboot file should be in the boot directory (which is there) and the bcd,
> bootsdi, and boot.wim (even bootmgr is there) under /var/lib/tftpboot/boot/
> folder but I can't get any VM to boot into the Windows Installation
>
> LABEL menu
> COM32 linux.c32 boot/wimboot
> APPEND
> initrdfile=boot/windows-x64/bcd,boot/windows-x64/boot.sdi,boot/windows-x64/boot.wim
>
> The proxy.log files show a 404 Error: Not Found so I guess what I am not
> sure is why? the srvvannagios server is accessible and open without
> security. I also don't understand the double slashes
> "windows-pe-x64//wimboot" which doesn't seem make sense.
>
>
> E, [2016-02-05T09:36:06.792481 #14336] ERROR -- : [25387] 2016-02-05
> 09:36:06 ERROR 404: Not Found.
>
> E, [2016-02-05T09:36:06.922288 #14336] ERROR -- : [25395]
> http://srvvannagios/pub/windows-pe-x64/sources/boot.wim:
>
> E, [2016-02-05T09:36:06.922559 #14336] ERROR -- : [25395] 2016-02-05
> 09:36:06 ERROR 404: Not Found.
>
> E, [2016-02-05T09:36:11.396401 #14336] ERROR -- : [25363]
> http://srvvannagios/pub/windows-pe-x64//wimboot:
>
> E, [2016-02-05T09:36:11.396551 #14336] ERROR -- : [25363] 2016-02-05
> 09:36:11 ERROR 404: Not Found.
>
>
> Has anyone setup wimaging corrrectly and tell me what I'm doing wrong?
>
> Thank You
>
> Joey
>
>
Ok moving on I found out that the version of syslinux is too old for
Foreman proxy to work with so I need to upgrade syslinux, never done that
before.
[puppet@puppet](Fri Feb 05 15:18:00)~ $ dpkg -l |grep syslinux
ii syslinux 3:4.05+dfsg-6+deb8u1
amd64 collection of boot loaders
ii syslinux-common 3:4.05+dfsg-6+deb8u1
all collection of boot loaders (common files)
I need to upgrade it, is it just as easy as
$ sudo syslinux -update
Anybody?
···
>
>
> Hello,
>
I was able to find the kernel syslinux 5.x
https://www.kernel.org/pub/linux/utils/boot/syslinux/5.xx/ and copied over
the linux.c32 stored in /com32/modules/
But now I am getting this error:
<https://lh3.googleusercontent.com/-u2MQ67zMyow/Vrt4o5UC3pI/AAAAAAAAPfE/lvoESo4nd2I/s1600/foreman4.jpg>
I think it's not even a Foreman error, might be a linux.c32 error so I
moved back the old one stored in /usr/lib/syslinux/linux.c32 and still the
same error. Maybe I broke something?
Anyone?
>
> I got passed all those errors but I am getting the
>
No DEFAULT or UI configuration directive found!
Anybody know how to get passed this?
Hello Joey,
> Ok moving on I found out that the version of syslinux is too old for
> Foreman proxy to work with so I need to upgrade syslinux, never done that
> before.
>
> [puppet@puppet](Fri Feb 05 15:18:00)~ $ dpkg -l |grep syslinux
>
> ii syslinux 3:4.05+dfsg-6+deb8u1
> amd64 collection of boot loaders
> ii syslinux-common 3:4.05+dfsg-6+deb8u1
> all collection of boot loaders (common files)
>
>
> I need to upgrade it, is it just as easy as
>
> $ sudo syslinux -update
>
> Anybody?
I can remember something reading about minum syslinux 5. On CentOS7 it
works with the supplied syslinux:
syslinux-5.10-1.el7.rfx.x86_64
Please note, you need a lot more than that. I have a pull request with
templates here [1]
Do not forget you need wimboot to boot your WIM; PXElinux template
should look like this:
LABEL menu
COM32 linux.c32 boot/windows-x64/wimboot
APPEND initrdfile=#[ … bcd,boot.sdi,boot.wim ]
This assumes you are using the default directories the tftp poxy
creates, witch in turn only works of you did create the installation
media correctly using wimboot.
tree /var/lib/tftpboot/boot/
[…]
/var/lib/tftpboot/boot/
-- windows-x64 >-- bcd >-- boot.sdi >-- boot.wim– wimboot
Also, if linux.c32 needs to be in accessible.
If all goes well, wimboot should output "Encapsulating …" at boot
Also, you might want to have a look at deep dive [2]
The foreman part is covered in the foreman manual [3]
[1] https://github.com/theforeman/community-templates/pull/209
[2] https://www.youtube.com/watch?v=_R8-0KAkoPc
[3] Foreman :: Manual
···
On 06.02.2016 00:29, Joey Jojo wrote:
–
Daniel Helgenberger
Schivelbeiner Str. 46
10439 Berlin
