Fix in Datacenter: one initial update step was been skipped, what caused

maufunctions in the schedulers.

modules/cloudsim-examples/src/main/java/org/cloudbus/cloudsim/examples/CloudSimExample6.java

@@ -55,7 +55,7 @@ public class CloudSimExample6 {
 		//VM Parameters
 		long size = 10000; //image size (MB)
 		int ram = 512; //vm memory (MB)
-		int mips = 250;
+		int mips = 1000;
 		long bw = 1000;
 		int pesNumber = 1; //number of cpus
 		String vmm = "Xen"; //VMM name
@@ -80,7 +80,7 @@ public class CloudSimExample6 {
 		LinkedList<Cloudlet> list = new LinkedList<Cloudlet>();
 
 		//cloudlet parameters
-		long length = 4000;
+		long length = 1000;
 		long fileSize = 300;
 		long outputSize = 300;
 		int pesNumber = 1;

modules/cloudsim/src/main/java/org/cloudbus/cloudsim/Datacenter.java

@@ -911,7 +911,9 @@ public class Datacenter extends SimEntity {
 	protected void updateCloudletProcessing() {
 		//Log.printLine(CloudSim.clock()+": PowerDatacenter #: updating cloudlet processing.......................................");
 		//if some time passed since last processing
-		if (CloudSim.clock() > this.getLastProcessTime()+0.1) {
+		//R: for term is to allow loop at simulation start. Otherwise, one initial
+		//   simulation step is skipped and schedulers are not properly initialized
+		if (CloudSim.clock() < 0.11 ||  CloudSim.clock() > this.getLastProcessTime()+0.1) {
 			List<? extends Host> list = getVmAllocationPolicy().getHostList();
 			double smallerTime = Double.MAX_VALUE;
 			//for each host...