@Dark000- I’m happy that I helped in the smallest of ways, and only hope this helps others.

All,

I don’t know that FOGPrep or Partition adjustments, alone, corrected this problem. One way, I guess, to test would be to recreate the image, without FOGPrep. I’m more than certain the partition adjustments didn’t do this as the imaging process doesn’t know anything about the partitions them selves. All Partimage does is copy the data to the file, it’s really the FOG Scripts that create the partition specific images. Because of this, I am pretty certain these were not a problem in the first place.

I’m almost sure FOGPrep wouldn’t have been the fix for this either. Mostly because, to my knowledge, all FOGPrep does is get the UUID information (hostname and hardware specifics) cleaned up from the registry. At that point, it really doesn’t care.

It’s starting to sound, more, like the Image being under a certain size has helped improve the speed of this issue.

Nothing broke between them. A core kernel such as the one you’re describing (default install) contains drivers for video cards. With this comes the idea of kernel mode setting (KMS) which makes the terminal screen fit to the native resolution (if I understand it correctly) to your display.

The issue was KMS was not a fully tested feature and hence would show a snowy screen on some systems. Other systems it would display perfectly fine.

I imagine that an updated kernel (which one did you use 3.8.8 or something somebody built?) just has more support for video and can properly negotiate the KMS needed for the display.

If you’re using a custom one, I imagine you’re using a kernel that doesn’t care about the video card and just displays no matter what, which would also explain why you’re not seeing the “snowy” screen anymore.

Turning off compression can be pretty difficult as you’d be modifying the init.gz script files to stop having it compress, and uncompress the files.

I’ve never had to play with this, but there are a lot of areas in which you’d need to make the modifications. Mind you this wouldn’t affect already uploaded images, and may even make them unusable at that point as you’re no longer having anything that will decompress the files.

I’d recommend giving the system just a few more resources to peck at. Maybe another CPU (3 total if I’m understanding this correct) and maybe limit the amount of hosts able to image at the same time. Defaults usually sit at 10 systems, but you can adjust this under Storage management.

Then play with the number of systems to image at the same time. Maybe lower the numbers. Don’t force systems to image either as it defeats the purpose of the limits you’ve set.

You can, relatively safely, use the VM as that’s how I do all of my testing right now.

Just expect to get the “pinging” of the CPU as it is working pretty hard to keep up. It shouldn’t maintain that level of load for extremely long. I would even, possibly, recommend not having to watch the load average of that CPU as it should be expected, during heavy imaging times, that it is going to be used rather heavily. I even see these on our FOG Dedicated server (4 Xeon 3.2GHz 32GB ram).

Hi Adrian,
Did you ever get this fixed? If not… I think I know what’s going on.

The new switch has port security enabled. By default, port security on Cisco switches only allows one mac address per port. The port is allowing the windows 7 machine to connect initially, but blocks your VM when it attempts to connect because the VM has a different mac address.

Try this. On your switch, enter these commands.

en (enter enable mode)
conf t (configure from the terminal)
interface f0/2 (tell it which interface you want to work with)
switchport port-security maximum 2

This tells the switch that you will have 2 mac addresses using this port. You’ll come across this command at some point in your CCNA studies 🙂

Let us know if this works!

IPTables isn’t, to my knowledge, the firewall that’s running.

Ubuntu 12.04, to my knowledge, uses ufw for its firewall program. try:
[code]sudo ufw disable[/code] On both of the boxes and try again. I’m currently installing two Ubuntu 12.04 boxes just to give it a shot as well to help in troubleshooting.

I would take a look at the file:
[code]/var/www/fog/management/includes/dashboard.include.php[/code]
[COLOR=#000000]Lines 79-87[/COLOR]
[php]for( $i = 30; $i >= 0; $i-- )
{
$res = mysql_query(“SELECT COUNT(*) AS c, DATE(NOW() - INTERVAL $i DAY) AS d FROM tasks WHERE DATE(taskCreateTime) = DATE(NOW()) - INTERVAL $i DAY”, $conn) or die(mysql_error());
if ($ar = mysql_fetch_array($res))
{
// NOTE: Must multiply timestamp by 1000 for unix timestamp in MILLISECONDS
$Graph30dayData[] = ‘["’ . strtotime($ar[‘d’])*1000 . '", ’ . $ar[‘c’] . ‘]’;
}
}[/php]
[COLOR=#000000]The $ar[‘c’] variable is what gives you your Number of machines imaged, and for what ever reason, either your database is store the values as 1.0000000000000, or the sql statement is turning the value into a floating number rather than an integer.[/COLOR]

[COLOR=#000000]This is what my value shows. Also, as you’re running on Ubuntu 8.04, what version of PHP do you have?[/COLOR]

[COLOR=#000000]JPGraph (the thing that creates the graphs), all versions included with FOG 0.32, requires 5.1.0 or above to operate properly.[/COLOR]

Glad you got it going! Good luck!

Looks like I managed to resolved issue. I am pretty new to linux command, so I ask my co-worker how to add dns entry on my ubuntu lts. So he gave me commands below.

vi /etc/network/interfaces
then go to the end of the line gateway, type a, then hit enter.
type dns-nameservers ipaddressofdns
then hit ESC
then :wq
then /etc/init.d/networking restart

My fogserver is faster than ever.

thanks 🙂

Glad I could be of assistance!

Yes dnsmasq works with ubuntu 11.10, and any ubuntu revision.

ehm, it seems like we fixed it on our own.

The server was set up with DNS and gateway, which we really dont need since it is in local network.
We removed DNS and gateway from the IPv4 settings, rebooted the server and it is no longer delaying.

Thanks for the replies anyway!

I am astounded that I had this exact problem, and found this answer six months later.

I successfully imaged the previous XP image tho. On the same test PC.

p.s. I did notice via gui of the fog server that the XP image in question in the image folder is now 98gb instead of 35 that it should be.

Based on the results, my guess is somebody already had this same type of issue but disabled it with:[code]setenforce 0[/code] on the server, which is why it was working. On the next reboot, because it wasn’t disabled before, it just reset to enforcing.

i have hp system with Win7 and three partitions i can do upload the image and it does with all partition but one parttition d1p3.img has size of 340 Kb actually its is 30gb partition with data of 26GB. i can restore the image but while restoring the parttition d1p3 it does not locate image file and ask for full path.

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

[media=youtube]69gJvHjTKNQ[/media]

Yeah that works too lol 🙂

I didn’t have access to my WDS server, and I am the only one adopting FOG in my corporation, the rest wants to spend all their time dicking with that WDS server, FOG is easier for me to use. So long story short, I wasn’t allowed to just disable the service 🙂