Allocation of VM to Host failed by MIPS

[Alessio Viola]

Hello, i'm practising whit CloudSim for my thesis.
Executing CloudSimExample4 i get this output:

Starting CloudSimExample4...

Initialising...

Starting CloudSim version 3.0

Datacenter_0 is starting...

Datacenter_1 is starting...

Broker is starting...

Entities started.

0.0: Broker: Cloud Resource List received with 2 resource(s)

0.0: Broker: Trying to Create VM #0 in Datacenter_0

0.0: Broker: Trying to Create VM #1 in Datacenter_0

[VmScheduler.vmCreate] Allocation of VM #1 to Host #0 failed by MIPS

0.1: Broker: VM #0 has been created in Datacenter #2, Host #0

0.1: Broker: Creation of VM #1 failed in Datacenter #2

0.1: Broker: Trying to Create VM #1 in Datacenter_1

0.2: Broker: VM #1 has been created in Datacenter #3, Host #0

0.2: Broker: Sending cloudlet 0 to VM #0

0.2: Broker: Sending cloudlet 1 to VM #1

160.2: Broker: Cloudlet 0 received

160.2: Broker: Cloudlet 1 received

160.2: Broker: All Cloudlets executed. Finishing...

160.2: Broker: Destroying VM #0

160.2: Broker: Destroying VM #1

Broker is shutting down...

Simulation: No more future events

CloudInformationService: Notify all CloudSim entities for shutting down.

Datacenter_0 is shutting down...

Datacenter_1 is shutting down...

Broker is shutting down...

Simulation completed.

Simulation completed.

========== OUTPUT ==========

Cloudlet ID    STATUS    Data center ID    VM ID    Time    Start Time    Finish Time

    0        SUCCESS        2            0        160        0,2        160,2

    1        SUCCESS        3            1        160        0,2        160,2

CloudSimExample4 finished!

I don't know why broker fails creating VM#1 in Host#0 (of Datacenter#0). I thought that the problem was the argument VmSchedulerSpaceShared passed to the Host of each Datacenter, but replacing "VmSchedulerSpaceShared" with "VmSchedulerTimeShared" the output is the same.

Could someone help me?

[AbdolNaser Dorgalaleh]

Change VMs configuration it may helps you to avoid this, but in general it is not an important problem.

[Alessio Viola]

Ok, thank you

2013/10/9 AbdolNaser Dorgalaleh <n.dor...@gmail.com>

--
 
---
You received this message because you are subscribed to a topic in the Google Groups "cloudsim" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cloudsim/Bg707BR2WlE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cloudsim+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Gandhi Kishan]

AbdolNaser Dorgalaleh , 

sir , i want to know what is the reason behind it . why creation of vm is failed due to MIPS ??

[aida nasr]

hi,

Often this problem occurs , when MIPS of pe is less than MIPs of VM

like this code 

(createDatacenter Method-------------->)

List<Host> hostList = new ArrayList<Host>();

// 2. A Machine contains one or more PEs or CPUs/Cores.

// In this example, it will have only one core.

List<Pe> peList = new ArrayList<Pe>();

int mips = 100;

// 3. Create PEs and add these into a list.

peList.add(new Pe(0, new PeProvisionerSimple(mips))); // need to store Pe id and MIPS Rating

Main Method --->>>>

vmlist = new ArrayList<Vm>();

//VM description

int vmid = 0;

int mips = 1000;

long size = 10000; //image size (MB)

int ram = 512; //vm memory (MB)

long bw = 1000;

int pesNumber = 1; //number of cpus

String vmm = "Xen"; //VMM name

//create two VMs

Vm vm1 = new Vm(vmid, brokerId, mips, pesNumber, ram, bw, size, vmm, new CloudletSchedulerTimeShared());

vmid++;

Vm vm2 = new Vm(vmid, brokerId, mips, pesNumber, ram, bw, size, vmm, new CloudletSchedulerTimeShared());

//add the VMs to the vmList

vmlist.add(vm1);

vmlist.add(vm2);

[aida nasr]

read also 

https://groups.google.com/forum/#!topic/cloudsim/jChEqBrZOHM