Cannot ping my virtual machines!

Similar Questions

• Cannot ping the Virtual Machine by host

  Hi all,

  Please help, I use VMWare Workstation 6.5 and I have a physical operating system which is Windows XP SP2, I have a network card, but not connected to a physical switch, the IP address is 192.168.0.1. I installed a Virtual Machine using Microsoft Windows 2003 server as the operating system, promote as domain controller, install the DHCP, DNS service and assign an IP 192.168.0.2, no default gateway.

  My VMnet1 on physical operating system has an IP 192.168.204.1 and VMNet8 has an IP 192.168.126.1.

  The host, I cannot ping the 192.168.0.2 which is the IP address of the Virtual Machine. Even in the Virtual Machine, I can not ping 192.168.0.1 is the IP address of the host. From what I read, the physical and the virtual machine were connected with a virtual switch. Am I wrong?

  Any advice?

  Thanks in advance.

  They SEEM to be in different networks, you need search routing between them,... since they differnet networks...

  on the other

  they do host and the virtual machine on the same subnet / network for EXAMPLE: class C class network 192.168.200.0/24

  granting of points if my answer was helpful... Thank you > > > > > > > >

  concerning

  Joe

• Cannot ping a virtual machine, except on the host computer.

  I have a host of SuSE, built on a chassis of IBM. It has a link for the failover interface. It has an IP of 10.10.138.196. SM 255.255.255.128. DG 10.10.138.129. I can ping this machine without problem. On that note, I have a virtual machine of SuSE. It has the same mask and gateway with an IP address of 10.10.138.197. It can ping the host (196) and the host can it ping. However, he cannot ping to the gateway by defaut.129. He receives a message Impossible to its own virtual interface. I have installation bridged networking early with no luck.

  I tried to change the DG on the guest a.196. I have installation routes by default, and specific directions to 10.10.138.129 on the host and the guest without success. I talked to a few colleagues and they are not of course either. I need this available, so it can be used for a variety of applications.

  You will not see a virtual NETWORK adapter for bridged interface, only for NAT and the host-only networking. There will be a device/dev/vmnet0, but that is not actually used to fill itself.

  Your problem is that your bridged interface is bound to the wrong card on the host: it must be related to "bond0" not "eth0". You will need to re - run /usr/bin/vmware-config.pl to address which forces all running VMs to be stopped.

  ---

  If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

• [Q] cannot start a virtual machine - internal error [SOLVED]

  Hallo,

  I installed Workstation 8 and cannot start a virtual machine - or those created those previous or new. Turn the machine gives me an "internal error."

  My characteristics: Win 7 64-bit (SP1), Core i7 2600 K with 8 GB of Ram

  The newspaper of vmware:

  011 10 - 03 T 19: 22:38.013 + 02:00 | VMX | I120: Log for VMware Workstation pid = 3424 version 8.0.0 = Build = build-471780 option = output
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: The process is 64-bit.
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: Host = encoding windows-1252 = windows-1252 codepage
  2011-10 - 03T 19: 22:38.013 + 02:00 | VMX | I120: Host is Windows 7 Home Premium, 64-bit Service Pack 1 (Build 7601)
  2011-10 - 03T 19: 22:37.713 + 02:00 | VMX | I120: VTHREAD initialize main thread id 0 "vmx" host 6336
  2011-10 - 03T 19: 22:37.738 + 02:00 | VMX | I120: Settings REGIONAL windows-1252-> user NULL = System = c07 c07
  2011-10 - 03T 19: 22:37.738 + 02:00 | VMX | I120: Msg_SetLocaleEx: HostLocale = windows-1252 UserLocale = NULL
  2011-10 - 03T 19: 22:37.743 + 02:00 | VMX | I120: FILE: FileLockDynaLink: other process validation tools are: available
  2011-10 - 03T 19: 22:38.014 + 02:00 | VMX | I120: Hostname = KOENIG
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = d fe80::41: e6a3:5dd2:fa9f % 11
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = fe80::1cf:3682:36e8:4ccb % 17
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = fe80::1 d 80: 2f6e:979 c: b57d 18%
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP 192.168.1.4 =
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = 192.168.30.1
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: IP = 192.168.158.1
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: HOSTINFO 1074415970 @ 3331240Hz-> 0 Hz 1000000000
  2011-10 - 03T 19: 22:38.017 + 02:00 | VMX | I120: HOSTINFO ((x * 2518163806) > > 23) + 322527338056
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: System uptime 321912074 us
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: command line: "C:\Program Files (x 86) \VMware\VMware" "-s" 'vmx.stdio.keep = TRUE' "-#" "product = 1; name = VMware Workstation; version 8.0.0 =; BuildNumber = 471780; licensename = VMware Workstation; licenseversion = + 8.0; ""-@ ""pipe=\\.\pipe\vmxf3ce37cf9b6f9c3e;" "D:\VM\Windows 7 x64\Windows 7 x64.vmx".
  2011-10 - 03T 19: 22:38.037 + 02:00 | VMX | I120: Msg_SetLocaleEx: HostLocale = windows-1252 UserLocale = NULL
  2011-10 - 03T 19: 22:38.056 + 02:00 | VMX | "I120: UI connection on pipes '\\.\pipe\vmxf3ce37cf9b6f9c3e' user (null)".
  2011-10 - 03T 19: 22:38.057 + 02:00 | VMX | I120: VMXVmdb: local connection timeout: 60000 ms.
  2011-10 - 03T 19: 22:38.104 + 02:00 | VMX | I120: VmdbAddConnection: cnxPath = / db/connection / #1 /, cnxIx = 1
  2011-10 - 03T 19: 22:38.105 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:483]: VMAutomation: initialize VMAutomation.
  2011-10 - 03T 19: 22:38.105 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:780]: VMAutomationOpenListenerSocket() to listen
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Past vmx/execState/val of poweredOff
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 2, newAppState = 1877, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:4067]: VMAutomation_ReportPowerOpFinished: VarEtat = 3, newAppState = 1881, success = 1 additionalError = 0
  2011-10 - 03T 19: 22:38.122 + 02:00 | VMX | I120: VMMon_GetkHzEstimate: calculated 3411189 kHz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: VMMon_RememberkHzEstimate: calculated 3411189 kHz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC kHz estimates: Memoirs of vmmon 3411189, 3411189, osReported 3401000. With the help of 3411189 kHz.
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU 0 # TSC = 1100186590922
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 1 TSC = 1100186590888
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: # 2 CPU TSC = 1100186590603
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 3 TSC = 1100186590637
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 4 TSC = 1100186590948
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # TSC 5 = 1100186590906
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 6 TSC = 1100186590898
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: CPU # 7 TSC = 1100186590836
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC of measured first delta 345
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: TSC 387 min Delta
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: PTSC: RefClockToPTSC 0 3331240 Hz-> 0 to 3411189000 Hz
  2011-10 - 03T 19: 22:38.123 + 02:00 | VMX | I120: PTSC: RefClockToPTSC ((x * 4294966339) > > 22) +-1100565306901
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: tscOffset-1100187618517
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: using TSC
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: material TSCs are synchronized.
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: PTSC: PTSC current = 289960
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Module CPUID initialization failed.
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:869]: VMAutomation_LateShutdown()
  2011-10 - 03T 19: 22:38.124 + 02:00 | VMX | I120: Vix: [6336 mainDispatch.c:819]: VMAutomationCloseListenerSocket. Close the socket of the receiver.
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | I120: VMX VMDB Flushing connections
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | "I120: VmdbDbRemoveCnx: remove Cnx Db for ' / db/connection / #1 /"
  2011-10 - 03T 19: 22:38.125 + 02:00 | VMX | I120: VmdbCnxDisconnect: Disconnect: pipe closed for pub cnx ' / db/connection / #1 /' (0)
  2011-10 - 03T 19: 22:38.129 + 02:00 | VMX | W110: Failed to initialize the virtual machine.

  I scored an error... I tried to reinstall, clean... nothing helps.

  Curiously, I can use the Player app to run all VM´s without problem...

  All solutions?

  Thanks in advance

  Marcus4Aspern

  Is - the name change "vmware.exe" with something else?

• No ping between virtual machines

  Hello

  I use VMWARE 7 program... I installed two virtual machines (windows server 2008 and windows 7)... I have attached two pic for each other... .my problem is... There is no rattling between these two machines... I disabled the firewall in both entities... How you can help me in this...

  My respects

  Post edited by: a.p. - changed the subject of the "Greetings" to "no ping between virtual machines.

  I do a bit of practice for MCITP study... In windows server 2008, I use Bridge and in the Windows NAT using 07:00

  Well, I guess you should start your trip MCITP become familiar with the IP configuration and routing

  Addresses that you configured do not work that way. Assuming that the physical - bridged - network (if connected) is 192.168.100.x, you may be able to access the Windows Server 2008, but you will never be able to access the virtual from Windows 7 computer with the NAT configuration, because NAT is running on another network (vmnet8 - 192.168.201.x). Depending on the need or not to be able to access the outside world of the virtual machine, you should consider is instituted two virtual machines with an IP address in the range of vmnet1 (Host-Only - 192.168.80.x) or vmnet8 (NAT - 192.168.201.x). In the case of NAT, configure the virtual machine for DHCP or use IP addresses between x.x.x.3 and x.x.x.127.

  André

• Cannot convert a virtual machine while it is powere on or suspended. Shut down and power off the virtual machine before the conversion.

  Hi all

  I am currently using preinstalled VMware 7.1 and I try to import a virtual machine, I used to work on my windows XP. Recently, I am using windows VISTA and I am trying to import my VM (.vmx) and I get this error "cannot convert a virtual machine, although it is powere on or suspended. "Shut down and power off the virtual machine before the conversion.

  This virtual machine worked very well under windows XP and VMware 6.5, but now I am not able to import it. Please suggest how I can make this virtual machine running in my VISTA and vmware 7.1.

  I am also attaching the converter file logs and .vmx vmware.

  Thank you...

  Is there a problem with this backup?

  It is possible. How big is she?

  Right-click on the vmdk file in Solution Explorer, then select «Map virtual disk...» "Does it work?

  André

• Cannot ping between virtual servers on the same host

  I have a 5 ESXi host with 3 virtual copies of Windows Server 2008R2 running on them. The ESXi host is connected to my switch, which has the Windows 2008 R2 DC to my test network and my laptop management with VSphere branch above as well. I can ping host, mobile and ad server of each of the individual virtual servers and can ping and RDP for all 3 from other devices not on that host, but I cannot communicate between the three. I have Windows Firewall disabled on all three. I have no firewall, and all machines have an IP address in the 10.0.0.X range I deleted then recreated the only virtual switch on the host on which appear all 3. I've been VERY frustrated for the last 3 days on it. Why my virtual machine cannot talk to each other?

  When you have registered virtual machines in ESX you selected moved VM or Coiped VM? Go to editing parameters and watch the MAC addresses. My guess is that if you copied power (including the vmx files) then the MAC address is the same for all virtual machines. You can stop the machine and change for a MAC address mac address. You can also remove the network adapters, one of each, and then add the new network cards. Remember to reconfigure the IP addresses on the box and remove the ghost network maps after doing this.

  Check this KB to change the mac address.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=507

  Also, can you connect to the switch and look at the ARP table and see if the system VMs register here.

• Cannot RDP into virtual machine after the reboot

  Hi all

  I use VMware ESXi4.0

  I'm having a problem where if I reboot a virtual machine, once it restarts I try to use the Remote Desktop Connection Manager to access and receive this error:

  "The connection cannot be completed because the remote computer that has been reached is not the one that you specified.  This could be caused by an outdated entry in the DNS cache.  Try using the IP address of the computer instead of the name. »

  The current machine I noticed the error is Windows 7 but also for me Server 2008.  not sure if this relevant.  I can still access the machine through vSphere, but not Remote Desktop.  When I ping the name of the machine as well as IP address, they both similar deadlines.

  I checked my DC for dns entries, and they are there for this computer as well as in the reverse lookup zones.  I tried to do a/flushdns and / registerdns on the virtual machine.

  I would usually have for this problem to connect to vSphere virtual machine, then RDCM is there to connect.

  I saw another post on this topic in the forum, but he had a solution. This post is here > http://communities.vmware.com/message/1304004

  I tried the recommendations here and they did not help.

  Any ideas on what I can try?

  Thanks in advance,

  John

  Here's the update to which I was referring... He had to be reissued in June because of the problems that it caused on some systems.

  http://support.Microsoft.com/kb/2667402

  But, if you are able to connect via IP, then the RDP patch will probably not help.

• Cannot create a virtual machine with a vmdk file copied from another location, please find the attached error

  Hi all

  I copied a file from one place vmdk and try to make a new virtual machine with this vmdk file. But when I turn on after the creation of vm error is coming. Error in the text and the image below

  Power on the virtual machine: cannot open scsi0:0 disc: disc not supported or not valid type 7. Ensure that the disk has been imported.

  See the error of the stack for more details on the cause of this problem.

  Time: 31/03/2015-14:40:05

  Target: DBServer

  vCenter Server: vcsa

  Error stack

  An error was received from the ESX host turning on DBServer VM.

  Unable to start the virtual machine.

  Power DevicePowerOn module has failed.

  Unable to create the virtual SCSI device for scsi0:0, ' / vmfs/volumes/543d140b-feb33d52-7640-90b11c9796c3/vmdk/kapuatdb.vmdk'

  Could not open scsi0:0 disc: disc not supported or not valid type 7. Ensure that the disk has been imported.

  This error message generally if the hard files have been copied hosted as VMware Workstation product, which uses a format of sparse file that is not supported on an ESXi host. Instead of the hard copy, you can use VMware Converter, or - if you prefer - you can convert the hard using vmware-vdiskmanager (before transfer) or vmkfstools (after downloading). I deal to use vmkfstools you will need to load the mutliextent module (see for example "Clone or migration operations involving virtual discs non-VMFS on ESXi fail with an error" vSphere 5.1 Release Notes)

  André

• VMware 6.5.5 cannot import the virtual machine that uses 2GB "disks of split.

  Hello

  I'm using VMware Workstation 6.5.5 under Win XP. I tried to import a virtual machine that was created by using the option 'Split' virtual disks into files of 2 GB. The import fails and presents a pop-up: ' Conversion Assistant/cannot determine the guest operating system. The log file includes the line "could not find the disk cofortcol3v01 - cl1.vmdk. This file does not exist of course, there are more files cofortcol3v01-cl1 - s001.vmdk, cofortcol3v01-cl1 - s002.vmdk and so on. The machine virtual original (cofortcol3v01) has been created under VMware Workstation 5.1, and it does not under Workstation 6.5.5.

  Is this a known problem in the conversion utility? Is there a work around for this problem?

  Thank you.

  -Phil Anzel

  FYI... VMware Workstation peut import a Virtual Machine that uses twoGbMaxExtentSparse discs.

  The log file includes the line "could not find the disk cofortcol3v01 - cl1.vmdk. This file does not exist of course, rather there are files cofortcol3v01-cl1 - s001.vmdk, cofortcol3v01-cl1 - s002.vmdk and so on. The machine virtual original (cofortcol3v01) has been created under VMware Workstation 5.1, and it does not under Workstation 6.5.5.

  Is this a known problem in the conversion utility? Is there a work around for this problem?

  The problem is that you're missing the "disk DescriptorFile", "cofortcol3v01 - cl1.vmdk" and which is why it's a failure and not a limitation of the Conversion utility.

  Also if you actually had a Virtual Machine created in VMware Workstation 5.1 you can simply run directly under VMware Workstation 6.5.5 without having to run the import command.

  Anyway, if you have a backup that you can recover the file "cofortcol3v01 - cl1.vmdk" then you should be fine and if you have not then a new can be created.  If you can archive (compress) files vmware*.log (usually 4 of them) in a single zip file archive and tied him to a post in response, then one of us will create a new file "cofortcol3v01 - cl1.vmdk", based on the information contained in files vmware.log for you, if you don't know how to do it yourself.

• Cannot start multiple virtual machines.  Maybe I corrupted the model

  We had problems with disk space, and I was looking around to see if he had left garbage data store.  I am very new to VM, but even though I'm new I'm responsible for helping maintain.  So I learn a lesson the hard way.

  I found a number of virtual machines in organized which did not seem to relate to existing models.  For example, we have a model name 000729-Server2008 Server 2008, that they are in lm401\729.  But it appers to be a clone of 729 to lm401\16.  I'm going to guess that 16 was the original version and changes or clones have been made for him and we are now sitting to 729.

  Then I moved 16 in another data store, but it failed because there is a lock on the hard master.  So I moved everything back.  Now, when we try to start up of VMs driven from this model we get "file & lt; filename not specified & gt; not found"I went back and tried to deploy and supply on the model but I get

  Impossible to deploy virtual machines in the pool of resources 'resgroup-131.

  • Not to feed one or more virtual machines.

  • Error when powering on a virtual machine '2008 X 86'.

  • Cannot power on the operation on a virtual machine
    carried out because one of the files is locked. Consolidation of the
    virtual machine can solve this problem.

  • The operation cannot be performed because a file is locked.

  So I cancelled and tried to consolidate while I get

  Host '172.31.7.111' reported an error. A disk error has occurred: the parent of this virtual disk could not be opened. Host '172.31.7.111' reported an error. A disk error has occurred: the parent of this virtual disk could not be opened.

  Can someone help me?

  This article may help: http://www.vmware.com/kb/1007969

  If you have found this helpful at all prices please points using the correct or useful!  Thank you!

• Cannot open 2 Virtual Machines at the same time to access the same database

  People,
  
  Hello.
  I'm installing RAC Oracle Database 11 g 2 system with 2 Virtual Machines (rac1 and rac2) on top 3 VMPlayer.
  
  The VM rac1 and rac2 when one of them is stopped.
  Their locations are F:\VM_RAC\rac1 and F:\VM_RAC\rac2.
  
  
  I opened rac1 rac2 is running. But this error message appears:
  
  Error: "cannot open F:\VM_RAC\sharerac\asm1.vmdk drive or one instant records, that depends. Reason: cannot lock the file. »
  
  
  While rac1 running, I opened rac2. But this error message appears:
  
  Error: "cannot open F:\VM_RAC\sharerac\asm1.vmdk drive or one instant records, that depends. Reason: cannot lock the file. »
  
  
  2 error messages are the same. This means that I can not open 2and rac1 rac2 VMs at the same time. When we run RAC system, must open 2 "machines" or machines to more than 2 at the same time, so that all machines can access the same database server.
  
  My question is:
  
  Can all folk tell me how have rac1 and rac2 run at the same time?
  
  Thank you.

  Unfortunately no, Oracle RAC requires that all nodes can visit the same set of shared disks. If your database resides within the DSO, each instance ASM (one per node) must also see the same set of disks to ASM diskgroup containing the data of the database files.

  Best regards
  Bryan Wood

• Cannot start the virtual machine guest after receiving "License expired message" host ESXi 5.5

  I can't start computer virtual invited after receiving "License expired message" 5.5 ESXi host. I am able to copy the vm folder prompted with all its files using WinSCP I had already installed on a desktop computer in the network.

  However, it takes an extremely long time to download the VM [2.5 mb/s], which is of course a different question.

  It seems that I was still on the trial with my vsphere client license, until it expired. I am able to view the virtual machine within the workstation 10, but I can't turn it on. It says "Please install a license to power on this computer" there is no way to install a license anywhere.

  My question is... .will I be able to access this virtual machine if I download on an external hard drive, then add it to 10 VMWorkstation that I possess a current valid license?

  Even if the evaluation license has expired, you should be able to connect to the ESXi host using the vSphere Client and follow the steps mentioned in the article that I posted before you enter the free license key.

  André

• Cannot start the virtual machine after you create snapshop

  I found a strange behaviour. I have a Windows 2008 guest that I just copied in my new box ESXi. I am trying to create a snapshot before upgrading the guest to 2012 Windows operating system. The virtual machine has currently no snapshots. Whenever I have create a snapshot, he succeeds, but then I can't start the virtual machine saying that it does not find the vmdk file delta even though I see there in the data store. In order to start the virtual machine, I have to delete the inventory and it readd, but then I lose the snapshot. I also have another computer virtual running Windows 8.1 that does exactly the same thing. How can I create snapshots safely without damaging the virtual machine? I also tried to create the snapshot while the virtual machine has been activated but that makes crashing and then it does not start again, so I have to repeat the process to remove the inventory and it time. Frustrating. See the screenshots, I have attached.

  Once these virtual machines have been in Hyper-V in the past and I just convert to VMware format using the StarWind V2V converter.

  Yes, for an ESXi host and target you must either select the ESX f.vmdk as format target (growable option is for VMware Workstation), or you must convert the virtual machine once more instead of simply upload the files to an ESXi host.

  André

• ESXi 5.1 cannot start a virtual machine with Admission check has no memory error

  I see that there were a number of people who have this error and adjusting the reserve memory for the VIM under resources system has solved this problem, but not for me. My booking in the VIM process setting is '0'. Vital signs:

  Reference Dell T110 II server

  4 GB OF RAM

  Intel Xeon processor E31220 @ 3.10 GHz

  4 cores of the processor

  Hard drive 500 GB

  ESXi version 5.1

  A Linux VM with 4 GB RAM allocation, 2 cores of CPU and 45 GB of storage.

  Error I get on a attempted to start:

  Has no power on the virtual machine.

  Could not power on VM: check for Admission has no resource memory see the management of VMware ESX Resource Guide for management information settings.

  Group vm.4757: invalid memory for VM vmm0:Mitel_Applications_Suite allocation settings. (min: 524288, max:-1, minLimit:-1 actions:-4, units: pages)

  Group vm.4757: can not admint VM: admission of memory has failed. booking request: 536579 pages

  I changed the memory to the VM all the way up to 1 GB, no change.

  I played a bit with the allocation of memory VIM, no change.

  A fact interesting is that the Allocation of resources for the tab host watch memory @ 1747MB capacity, capacity reserved @ 0MB and available @ 1747MB capacity, but I have 4 GB of RAM and the vSphere Client shows it under the Configuration tab.

  Take a look at this blog post: http://www.vmwarearena.com/2012/07/failed-to-power-on-vm-admission-check.html