I was playing with the same idea of running FOG on a VM and allocate all physical resources to it. It seems like there’s some network slow down in the emulation layer and I couldn’t get more that 250MB/min. Where as on the same physical server if I did a raw Ubuntu 11.10/FOG0.32 install I could get steady 1.6GB/min speeds. I think you’ll find you’ll be much better off on a dedicated server even if it’s not a super beefy machine. I also messed around with Bonding mulitple NICs and got nothing but trouble unless you just want it as a hot backup. There are a lot more errors when trying to load balance and ended up not being worth the trouble.

[quote=“Amir, post: 785, member: 335”]There are several places that you can check in order to make sure that your new hosts are communicating with the right FOG server IP address specified on /tftpboot/pxelinux.cfg/default[/quote]
I forgot all about the ip addresses passed in the append lines of the default config file! That did it!
I’m going to add this to the wiki page for [URL=‘http://www.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address’]changing the IP address of a FOG server[/URL].

I had the same exact issue before with Optiplex 790 Series. In order to resolve this issue you need to rebuild your FOG kernel with the latest KITCHENSINK and import your drivers.

[url]http://fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]

Hope it helped.

If your systems are outdated and do not support PXE boot on BIOS you can still boot them via PXE by using RBFG bootdisk. RBFG stands for Remote Boot Floppy Generator which creates the capability for those clients that natively do not support boot via PXE.
In order to create this bootdisk, either you need to have a Windows 2000 Server Disk or if you do not have one then follow the instruction on this site: [url]http://registration.argontechnology.com/rbfg/index.shtml[/url]

Hope it helps you.

Depends on your distro, in ubuntu try “nano /etc/dhcp3/dhcpd.conf” and look for “option routers”.

Thank you for coming back to explain how you fixed your issue. It adds value to the forums and the FOG community.

yeah thanks i got pxe boot/registering working, didnt have time to upload/download today will test next week

FOG runs on top of Ubuntu Server (or centos)

so yes you will need to install Ubuntu as a VM

Have you tried using kernel arguments like nomodeset?

That sounds fine. Let me know if any code needs to change in FOGController or FOGManagerController

You should have a look at the latest code i have submitted. I have made a lot of changes to how Tasks are generated.

$Host->startTask was written by microleaks, but never put into prodution. The old production code was in ‘management/includes/tasks.confirm.include.php’’

Task creation is now handled in Host.class.php. There are 3 functions for instant deployment, single run scheduled deployment and cron style deployment:

[url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk/packages/web/lib/fog/Host.class.php[/url]
[code]$Host->createImagePackage($taskTypeID, $taskName = ‘’, $shutdown = false, $debug = false, $deploySnapins = true, $isGroupTask = false)
$Host->createSingleRunScheduledPackage($taskTypeID, $taskName = ‘’, $scheduledDeployTime, $enableShutdown = false, $enableSnapins = false, $isGroupTask = false, $arg2 = null)
$Host->createCronScheduledPackage($taskTypeID, $taskName = ‘’, $minute = 1, $hour = 23, $dayOfMonth = ‘', $month = '’, $dayOfWeek = ‘*’, $enableShutdown = false, $enableSnapins = true, $isGroupTask = false, $arg2 = null)[code][/code]

There has been a new class to handle “TaskTypes” (aka download, upload, multicast, wipe, av, etc) and this class reads it’s information from the ‘TaskTypes’ table. You are able to specify custom kernel and kernel arguments per TaskType.

GUI code for Task creation is in HostManagementPage.class.php & GroupManagementPage.class.php
(functions deploy() & deploy_post() handle the calls to the Host functions.

[url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk/packages/web/lib/pages/HostManagementPage.class.php[/url]
[url]https://freeghost.svn.sourceforge.net/svnroot/freeghost/trunk/packages/web/lib/pages/GroupManagementPage.class.php[/url]

Hi.

I’m working with the OP at the same place so I can give you more information:

We have two separated networks which should be served by a single fog server.

I have 3 nics on the fog server

Subnet A (10.10.200.) Subnet B (10.11.200.) iSCSI Network

I have 2 DHCP Servers. Both have option 066 and 067 configured. DHCP Subnet A has FOG_IP_SUBNET_A and DHCP Subnet B has FOG_IP_SUBNET_B Fog works perfectly on Subnet A.

However, today we needed to deploy 84 Machines on subnet B and even though I had access to the webmanagement (through NIC B) and also to the PXEBOOT (as assigned through DHCP B), I couldn’t do neither registrations nor deploy the images. To solve the issue (working against Time), I changed all the configs in the management window and FOG started to operate exclusively on Subnet B. I managed to deploy all 84 Images without problems. Now I would like not to have to change manually everything each time I need to deploy an image in diferent Subnets.

On the old forum I found a topic dealing with this were the OP changed iptables’s configuration to forward requests to NIC A but I’m not sure if that was all he did to accomplish what we also want to do. I also have serious doubts about the new DHCP config that has to be made (should both continue to point to the correct interfaces or should I point DHCP B it to Fog’s Subnet A NIC)?

here what he did:

[code]
/usr/sbin/iptables -A FORWARD -i eth0 -d 192.168.1.15 -j ACCEPT
/usr/sbin/iptables -A FORWARD -s 192.168.1.15 -o eth0 -j ACCEPT
[/code]

I also have some doubts about the risks of forwarding packets like that in the Fog Server because our two subnets work like this:

---- -----Internet Gateway A ----- Subnet A ---------- FOG SERVER NIC A > (limited comunication possible here. Out of our reach and not suitable for Image transfer/deployment ---- -----Internet Gateway B ----- Subnet B ---------- FOG SERVER NIC B

So, basically, they arn’t allowed to comunicate inside our scope but Subnet A can comunicate to Subnet B on some protocols using the gateways (which is by design and won’t be changed as it is out of our reach).

Answering your question, our Switches are all HP Procurves 2650 (Layer 2) and a central HP6100 (which then connects to the gateways) interconnected with gigabit fibre but this seems irrelevant to the case since we need to treat the Subnets as isolated (being able to PXboot from Subnet B using NIC B and accessing the management on both NICs is rather peculiar and I can’t explain it unless both TFTPD and Apache are listening on both interfaces). The bottom problem remains… I can’t register hosts or deploy the image through Subnet B) when FOG is configured as primary on Subnet A. I can however PXBOOT and access the Web management interface

Multicasting is set on the switches or I wouldn’t be able to deploy the images on both Subnets (just not at the same time without changing Fogs configuration)

Thank you for any input

Best Regards

Tony

You are not able to boot and install Windows XP from the TFTP boot menu due to the way ramdisk and memdisk handle the system.

More info here - [url]http://www.syslinux.org/wiki/index.php/MEMDISK#Windows_NT.2F2000.2FXP.2F2003.2FVista.2F2008.2F7_.28NT_based.29[/url]