@Dee DM me with specifics and I’ll see if I can help.
Posts made by SaxxAppeal
-
RE: VirtualBox FOG Server Download
-
RE: VirtualBox FOG Server Download
@george1421 said in VirtualBox FOG Server Download:
@Riggie8 This thread has been long abandon. Its much easier now to spin up a new linux server and then install FOG on it. We can guide you if you need.
Here is the wiki page for installing Centos 7 and then FOG: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
This thread has certainly not been abandoned… A lot of members have messaged me for the link and I’ve continued to share it!
It’s quite easy to spin up a new server and install a clean FOG, I agree. But some people have trouble or are not comfortable with working in the LINUX CLI. And to that end, I continue to offer the VM for all who are interested.
I’m also working on a new VM with v. 1.4 installed, hopefully I’ll have that in the next week or two.
As always, I’m available to share the bit that I know with all.
-
RE: Fog Web GUI Login Problem
Just to be clear, the default user name and password you were using were “fog” and “password”?
Did you capitalize “fog” for the user name?
-
RE: VirtualBox FOG Server Download
An updated FOG VM is now available, PM me for download link.
-
Updated FOG Virtual Machine Available
Hi all,
I have built an updated FOG VM for VirtualBox, available for download. It runs Ubuntu Server 14, a recent FOG trunk version, and a custom setup script to configure your network settings. I hope it’s helpful to those who want to try out FOG and are a little less than LINUX proficient.
If you’re interested in downloading, send me a PM and I will reply with the link.
Thanks again to the developers for their continued efforts on the project, looking forward to seeing what’s coming in future releases!
-
RE: Upgrade to Trunk, Kernel Panic
@SaxxAppeal Just figured it out!!
the boot line should read:
dhcp-boot=undionly.kpxe,, XXX.XXX.XXX.XXX
The double comma is required because it expects the server name first, then the IP.
Hope that helps someone…
Thanks EVERYONE for your help on this!!
-
RE: Upgrade to Trunk, Kernel Panic
@Sebastian-Roth The symlink works as well… But still asks me to enter the TFTP server. I think its just a matter of knowing exactly where and how to pass the FOG IP to dnsmasq…
-
RE: Upgrade to Trunk, Kernel Panic
@Sebastian-Roth Got it, that’s what I figured. I’ve been trying to figure out where I need to pass the FOG server address, so far no luck.
Requested info:
dhcp-boot=/tftpboot/ipxe.krn
I’ve played with this line over the last week, but it seems to work great this way.
-
RE: Upgrade to Trunk, Kernel Panic
@Sebastian-Roth Tried the 745 and the Lenovo notebook, both are perfect.
Only other thing that has been happening is when I PXE boot, I get the following prompt:
“Please enter TFTP server:”
When I enter it, everything goes through fine and it brings up the FOG menu. I’m sure it’s just an argument that needs to be passed, but not sure where I need to specify this. Any ideas?
-
RE: Upgrade to Trunk, Kernel Panic
@george1421 THIS WORKED!!!
I renamed the pxelinux.0 file to something else, and created the sym link… Booted right in!
I’ll continue to test with some other machines, if anyone else has any other tidbits to contribute please let me know!
-
RE: Upgrade to Trunk, Kernel Panic
@george1421 said in Upgrade to Trunk, Kernel Panic:
@SaxxAppeal Would you post the complete line from your dnsmasq for this prefix: pxe-service=X86PC
@Quazz I may have been reading more into what the OP didn’t say than reality.
The line you requested is as follows:
pxe-service=X86PC, "Boot from network", pxelinux
-
RE: Upgrade to Trunk, Kernel Panic
@george1421 After I installed FOG and dnsmasq, the /tftpboot directory has pxelinux.0 and pxelinux.0.old
undionly.kpxe is also present in the directory. My dnsmasq tsp.conf file points to /tftpboot as the directory to get everything from. -
RE: Upgrade to Trunk, Kernel Panic
Thanks for the suggestions, everyone.
In the original post I didn’t mention that I am using dnsmasq in my setup (always have), and it seems like it isn’t the issue because I get an IP from the FOG server, boot into the FOG splash screen, and am able to choose Full Host Reg/watch the bzImage and init files download to the client… Then I get the kernel panic.
Today I’ve tried setting up another virtual machine from scratch with Ubuntu 14, and just FOG with dnsmasq; same result.
Any other thoughts?
-
RE: Upgrade to Trunk, Kernel Panic
@Tom-Elliott said in Upgrade to Trunk, Kernel Panic:
http://<ip>/fog/service/ipxe/boot.php?mac=<macofhost>
Sorry for the delay.
Here is the output:
#!ipxe set fog-ip 10.1.0.154 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set colour --rgb 0x00567a 1 || colour --rgb 0x00567a 2 || colour --rgb 0x00567a 4 || cpair --foreground 7 --background 2 2 || goto MENU :alt_console cpair --background 0 1 || cpair --background 1 2 || goto MENU :get_console console --picture http://10.1.0.154/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console :MENU menu colour --rgb 0xff0000 0 || cpair --foreground 1 1 || cpair --foreground 0 3 || cpair --foreground 4 4 || 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.quickimage Quick Image item fog.multijoin Join Multicast Session item fog.sysinfo Client System Information (Compatibility) choose --default fog.local --timeout 3000 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :fog.memtest kernel memdisk iso raw initrd memtest.bin boot || goto MENU :fog.reginput kernel bzImage32.1 loglevel=4 initrd=init_32.xz.1 root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.1.0.154/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg imgfetch init_32.xz.1 boot || goto MENU :fog.reg kernel bzImage32.1 loglevel=4 initrd=init_32.xz.1 root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.1.0.154/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg imgfetch init_32.xz.1 boot || goto MENU :fog.quickimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.sysinfo kernel bzImage32.1 loglevel=4 initrd=init_32.xz.1 root=/dev/ram0 rw ramdisk_size=127000 keymap= web=10.1.0.154/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo imgfetch init_32.xz.1 boot || goto MENU :bootme chain -ar http://10.1.0.154/fog/service/ipxe/boot.php##params || goto MENU autoboot```
-
RE: Upgrade to Trunk, Kernel Panic
@Tom-Elliott Hi Tom!! What do you mean by browser output? The GUI loads and operates perfectly, not sure if you’re asking something else.
-
RE: Upgrade to Trunk, Kernel Panic
@Quazz I’ve tested it so far with a physical Dell 745 as the server, and a VirtualBox machine as the server.
I’ve tried with a Dell 745 client, Dell 760 client, Lenovo T430 client…
Not sure if I have any other hardware available that is vastly different from the ones I’ve mentioned.
-
RE: Upgrade to Trunk, Kernel Panic
@george1421 I see. Thanks for the help so far! I hope someone else can shed some light, I’ve been pulling my hair out for 2 days with this one.
-
RE: Upgrade to Trunk, Kernel Panic
@george1421 I just tried again. Full error text:
"Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(1,0)
Kernel Offset: disabled
—[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) -
RE: Upgrade to Trunk, Kernel Panic
@george1421 Okay, no problem, thanks for the help.
FWIW, I ran wget and pulled fresh files. Same result when I run the file command, same result when the client tries to load the kernel.
-
RE: Upgrade to Trunk, Kernel Panic
When I run “file bzImage”, my output is:
bzImage: x86 boot sector
So it seems the bzImage file in place is the wrong architecture, if I’m not mistaken??
I wonder how that happened. If I am right, how can I obtain a new x64 version?