New install - No menu on clients!
-
What type of VM is this you’re having issues with.
-
Hi,
This is on a Hyper environment. So both the server and the client both running in the HyperV (2012 r2 DataCentre) environment.
The version of FOG is 1.2 installed on Centos 6.6
regards
-
So I decided the start again. Reinstalled Centos, updated, installed Fog 1.2. Still I have the same issue.
This is the /var/log/httpd/error_log contents:
[Tue Nov 11 09:36:42 2014] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r$
[Tue Nov 11 09:36:42 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Nov 11 09:36:42 2014] [notice] Digest: generating secret for digest authentication …
[Tue Nov 11 09:36:42 2014] [notice] Digest: done
[Tue Nov 11 09:36:42 2014] [warn] ./mod_dnssd.c: No services found to register
[Tue Nov 11 09:36:42 2014] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured – resuming normal ope$
[Tue Nov 11 09:37:30 2014] [error] [client 192.168.1.1] Directory index forbidden by Options directive: /v$
[Tue Nov 11 09:37:30 2014] [error] [client 192.168.1.1] File does not exist: /var/www/html/favicon.ico
df: `/images’: No such file or directory
df: no file systems processed
[Tue Nov 11 09:40:07 2014] [notice] caught SIGTERM, shutting down
[Tue Nov 11 09:41:00 2014] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Nov 11 09:41:00 2014] [notice] Digest: generating secret for digest authentication …
[Tue Nov 11 09:41:00 2014] [notice] Digest: done
[Tue Nov 11 09:41:01 2014] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured – resuming normal ope$
[Tue Nov 11 09:41:01 2014] [warn] ./mod_dnssd.c: No services found to registerThere is no folder under /var/log/ called apache2 and so have no error log for that.
The foginstall.log file has everything installing and checking as OK.regards
-
[COLOR=#000000]Here is the output of [url]http://192.168.1.1/fog/service/ipxe/boot.php[/url][/COLOR]
[COLOR=#000000] [/COLOR]
[COLOR=#000000]#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
colour --rgb 0xff6600 2
cpair --foreground 7 --background 2 2
console --picture [url]http://192.168.1.1/fog/service/ipxe/bg.png[/url] --left 100 --right 80
:MENU
menu
colour --rgb 0xff0000 0
cpair --foreground 0 3
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
exit || goto MENU
:fog.memtest
kernel memdisk iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=192.168.1.1/fog/ consoleblank=0 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=192.168.1.1/fog/ consoleblank=0 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.sysinfo
kernel bzImage32 root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= keymap= web=192.168.1.1/fog/ consoleblank=0 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
autoboot[/COLOR] -
this is a known issue with hyper-v, there are a few threads on how to fix it. i think you will find that physical clients work fine.
-
Hi,
Thanks for that. Do you mean because the FOG server is on HyperV or because the client machine is a hyperV vm?
regards
-
client. it’s an issue with limited pxe capabilities in the implementation of the nic rom in the vm. the server should be fine.
-
Thanks Dude! Virtualisation - its just not quite there yet is it!!??
In general I mean…not just for FOG!!Thanks for your help! If you do know of a link to a thread about to fix it, it would be much appreciated! Have had a scout through but nothing that really stood out as a fix…
cheers
-
if i recall correctly, there’s a line in a php file you need to comment out so that the more advanced console environment stuff doesn’t load in the ipxe boot menu. i think someone even had a bit of code that would test for hyper-v by mac address or something and disable that section of code. i think virtualbox and vmware work fine at this point, though.
-
That will be this then! :
[COLOR=#007700][FONT=monospace]if ([/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]substr[/FONT][/COLOR][COLOR=#007700]FONT=monospace==[/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“00:15:5d”[/FONT][/COLOR][COLOR=#007700][FONT=monospace]){
print [/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“# Hyper-V MAC address detected - no console background\n”[/FONT][/COLOR][COLOR=#007700][FONT=monospace];
} else {
print [/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“console --picture [/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]$this[/FONT][/COLOR][COLOR=#007700][FONT=monospace]->[/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]booturl[/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]/ipxe/bg.png --left 100 --right 80\n”[/FONT][/COLOR][COLOR=#007700][FONT=monospace];
}[/FONT][/COLOR][COLOR=#007700][FONT=monospace]Will give that shot! :)[/FONT][/COLOR]
