Unable to ping Virtual Machines within ESXi host (vSphere Home Lab)

Similar Questions

• Problems of time (NTP) on the virtual machines within ESXi 4

  I had synchronization problems of intermittent time with my computers running on ESXi4 for quite a while now.  I thought that there were problems with my VM themselves and made some changes that appear to clear things for awhile.  The problems are back, and I'm starting to wonder if this is something being induced with ESXi itself.  My configuration is:

  ESXi 4.1.0

  -2 x Windows domain controller

  -Exchange Server x 2

  -FreeNAS

  VMWare tools are installed on all windows boxes.  FreeNAS is running without installed VMTools.  Domain controllers are set to use time NTP, servo out of an internet time server.  Client Windows have the default configuration and should be pulling the exact time of one of the two domain controllers.  FreeNAS is taking time to DCs.  Often when problems begin with authentication, it is because of the difference in clock being too great between servers, or between the Server / client.

  Are there recommended solutions for these issues?  I dug through the forum messages and the KBs and found a good bit of info but nothing that does not seem to solve these problems.

  I recommend you to configure a time outside of your virtual environment for you server ESXi hosts.

  Imagine that nothing is under tension, and you begin to start.

  Your domain controller will begin with your host ESXi (UTC) time until it can connect to the Internet to update time.

  At this time most VMs are probably on the wrong time, and it creates a lot of problems.

  After the updating of the DC then only will be hosting ESXi synch at the exact time. Quite a turn messed up

  If your ESXi have an external NTP server, they boot with the exact time and start all the virtual machines with the exact time.

  It may be useful

• Unable to ping Virtual Machines between VMWare

  I currently have two VM installed and have two Windows XP.  I can ping the computer host for virtual machines, but I can't use a ping on the other. VM - get "Request timed out".  Two virtual machines are in network NAT configuration.  I also tried to put on a team, but they still cannot ping each other. Did I miss something? - I think that changing the Bridge connections can work, but I think that NAT should also work. - especially when they are in a team.

  Thanks in advance for the help.

  Make sure that the security/AntiVirus/firewall software does not block ICMP requests and if need be, temporarily disable the firewall/AntiVirus/security software during the test.   Note also that some AntiVirus/firewall/security software fix protocols on the network that are still activated card to temporarily disable the firewall/AntiVirus/security software.

  If it does not then need to see output of the ipconfig/all command on the host and the guests.

  Copy & paste the following commands, as is, and then press ENTER...

  On the host computer in a in a command prompt. (Start > all programs > Accessories > prompt)

  ipconfig /all > "%USERPROFILE%\Desktop\host_ipconfig.txt"
  

  This will create a file on the desktop of the host named host_ipconfig.txt

  On the guests in a command prompt. (Start > all programs > Accessories > prompt)

  ipconfig /all > "%USERPROFILE%\Desktop\guest_ipconfig.txt"
  

  This will create a file on the client named guest_ipconfig.txt Office

  Note: Of course change the name of the guest_ipconfig.txt file to make the difference between the guests.

  Archive the files together unreleased and attach the .zip file to a response message.

• List virtual machines within a host, the data store and the specified how cluster?

  Hello
  I found the code shows but not able to understand. The exit is not what I want.

  Get-VM | Select Name, @{N="Cluster";E={Get-Cluster -Name "Site1UCSCluster01" }}, @{N="ESX Host";E={Get-VMHost -VM $_}},@{N="Datastore";E={Get-Datastore -VM $_}} |fl

  But, the exit wrong that these virtual machines do not reside on Site1UCSCluster01:

  Name      : CBEDM
  Cluster   : Site1UCSCluster01
  ESX Host  : Host1
  Datastore : CBEDM-DS3-R5
  
  Name      : CBEDMTest
  Cluster   : Site1UCSCluster01
  ESX Host  : Host2
  Datastore : CBTEST-DS1-R5

  Thanks for your help,

  So try like this

  $clusterName = "MyCluster" 
  
  Get-Cluster -Name $clusterName | Get-VM | Select Name, @{N="Cluster";E={$clusterName}},@{N="ESX Host";E={Get-VMHost -VM $_ | Select -ExpandProperty Name}},@{N="Datastore";E={Get-Datastore -VM $_ | Select -ExpandProperty Name}} |fl
  

• One migrated from my virtual machine to another host VSphere and it does not start

  I have a virtual machine that I've initially converted to Hyper-V to host VSphere. After I did it would start very well, but I got up two errors when starting.

  "An IDE controller is found but the VM does not support the option" and

  "A plate supporting the option not found."

  When I looked at the hard drive in the settings it looks like it is not supported. Is it because I badly converted to Hyper-V to VSphere using VMWare Converter?

  But now, I configure VCenter Server and tested a migration of these machines to another host and using the VSphere Client. It does not start now. I get an error message that says.

  "Device 'drive hard 1' uses a controller that is not supported." This is a general limitation of the compatibility of the virtual machine with the selected host ESXi version. »

  Remember that it is the same VSphere host it is running on initially. Any suggestion would be appreciated.

  If it works now - is that correct? n ' forget not to award points useful and/or correct

  I removed these entries;

  ide0:0. FileName = 'PIC-JVM-v0001 - 000001.vmdk ".
  IDE1:0. Present = 'TRUE '.
  IDE1:0.clientDevice = 'TRUE '.
  IDE1:0. DeviceType = "cdrom-raw"
  IDE1:0.startConnected = "FALSE".
  ide0:0. Redo = «»
  IDE1:0. FileName = ' / usr/lib/vmware/isoimages/windows.iso '.
  scsi0:0. DeviceType = "scsi-passthru.
  scsi0:0. FileName = ' / vmfs/devices/cdrom/mpx.vmhba1:C0:T0:L0 '.
  scsi0:0.allowGuestConnectionControl = "FALSE".

  And added to them;

  ide0:0.clientDevice = 'true '.
  ide0:0. DeviceType = "cdrom-raw"
  ide0:0.startConnected = "false".
  scsi0:0. FileName = 'PIC-JVM-v0001 - 000001.vmdk ".
  scsi0:0. DeviceType = "scsi-disk" hard
  scsi0:0. Redo = «»

  Although there is a high probability that the other six you have to do will be similar to this, they will have to be assessed individually and modified accordingly.

  See you soon,.

  Jon

• Wrong message 'VMware Tools can be updated' for the virtual machine within ESXi 4.1

  These VMware tools in my guest operating system keep on the list "VMware Tools can be updated" and the yellow exclamation point.

  Host operating system is ESXi 4.1.0 build 348481

  VMware Tools version is 8.4.8 build 491717

  It is not on the files with the extension.001 as described in the following article

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

  I checked and there is no file with this extension.

  I think that VMware tools is unable to read or to compare the correct numbers.  Or is there another reason?

  Reply to my own post:

  The answer, in fact the procedure, is inside this article:

  https://communities.VMware.com/docs/doc-31365

  For some reason VMware Tools is not installed correctly (for example files from previous versions are left inside the hard disk).  So I have to do a manual cleaning before you reinstall the tools.

• No network connection between the virtual machines on different hosts ESXi

  I have several 5.0 ESXi hosts in a cluster managed by vCenter Server 5 and I have network problems:

  1. [Host A] running a virtual machine can ping any other computer virtual running on the [host A] great!
  2. A virtual machine running on host [B] can ping any other virtual machine running on [B] home - very well!
  3. [host A] (from the ESXi console) can ping any virtual machine running on [B] home - even better!
  4. [B] home (from the ESXi console) can ping any virtual machine running [host A] - beautiful set!
  5. A virtual machine running [host A] can not ping any virtual computer running on host [B] and vice versa - bad, very bad!

  So basically the problem is that the virtual machines can communicate on hosts. It is a major problem that I need to fix, for obvious reasons.

  Networking on all hosts is configured exactly the same way: a unique and standard vSwitch with a pair of gigabit network cards grouped, vmkernels configured for the vMotion, NFS and network management and a group of ports configured for the VIRTUAL local area network used by the VMs. (vMotion works fine on hosts, storage vMotion works very well too.) All virtual machines are servers Windows (2003 and 2008).

  Reason #3 and #4 above, my assumption is that #5 must be the result of an ESXi/vCenter configuration issue and not a problem with the switches of material upstream. Is this a reasonable assumption?

  Whatever it is, can anyone offer suggestions on how can I fix? It is quite annoying as I'm pretty sure that these hosts are configured in the same manner as those of our production cluster, which does not at all these problems!

  Thanks in advance for any help you guys can provide.

  To be honest, it looks like a problem with your physical network-

  How is the physical network configured - are NIC connects it to the same physical switches? Are the virtual machines on the same subnet? If this is not the case, they are able to ping the gateway sbnet? Can you piing host IP address from the virtual machines?

  I also moved it to a forum more approiate.

• Migration of virtual machines in ESXi 4.1 to 5.5 to new hardware

  I'm new to VMware and our company bought 4 new servers and a SAN to replace our old VSphere 4.1 installation of 12 year.  The old configuration consisting of a server VCenter 4.1 physics 2003, 2 Dell 2900 ESXi hosts and 1 MD300i SAN.  Gen9 again the Installer 4 HP DL360 (3 host 1 VCenterServer) and MSA 2040.  Can someone please explain to me what would be the best way to go about moving more of our VM current for the new hardware? I found this from a previous post here, but it does not move the virtual machine to a SAN to another.

  Migration of the VMs of ESXi 4.x to 5.5

  "If I understand your question, continue to build the new environment of 5.5 with your 3 hosts from scratch 'ignoring' your old hosts. Once your new environment up & running, connect 4.1 guests to your new server vCenter Server and vMotion to move virtual machines while they run to the new cluster (live migration without interruption).

  VMTools upgrades do not have place automatically during migration.

  Once your virtual machines on new hosts, update tools as usual and you can then also upgrade virtual hardware of your virtual machines.

  Virtual HW update is optional, though; If you do not have the VMs that need the new features you can skip this last step and keep them as they are. »

  TYIA.

  The previous answer is pretty good, but I would like to add a few elements.

  You can 'disconnect' your 4.1 hosts of your old vcenter with running virtual machines, and then when you connect the hosts in your environment of 5.5 it will import your VM running as well.  As long as you have properly configured virtual networks you can live migrate vmfs old host and the old store of data simultaneously via the web client as long as your esx license allows it.  Otherwise close your virtual machines down to 1 at a time to migrate them above.

  Alternatively, you can consider running your vcenter as a virtual machine within the cluster it manages.  This gives you some DRS and HA for vcenter, plus a 4th host for virtual machines.

  If you don't have additional license you can also install your new hosts of 5.5 and run for 60 days before that you upgrade your 4.1 licenses to apply to your new host.

• IO emits virtual machines in a host

  Hi guys

  I have a 2 Server ESXi cluster build 1065491 for a month of monitoring reported some problems with virtual machines - ping has disappeared.

  After that, I found that VMs statement of losers pings were accommodated in the same server ESXi. Today, a problem has been reported with the vCenter apparatus which did not... do more research I found that all of the virtual machines that are hosted in this particular host appeared this message Windows - Linux

  Source: LSI_SAS

  Event ID: 129

  \Device\RaidPort0, restore the device, has been published.

  Source: disk

  Event ID: 153

  The operation of e/s to 142f8d address logical block to Disk 0 has been retried.

  kernel: mptscsih [40114.926402]: ioc0: quit the task! (sc = ffff8802116c3d80)

  kernel: [40114.926410] sd 0:0:0:0: [sda] CBD: Read (10): 28 00 00 05 57 80 00 00 40 00

  kernel: mptscsih [40115.055129]: ioc0: abandonment of the task: SUCCESS (rv = 2002) (sc = ffff8802116c3d80) (sn = 529576)

  any idea what could cause this problem? or how to fix it?

  Important that I moved a Windows 2012 VM without ESXi server to the problem and messages LSI_SAS and disc problems began to appear

  Thanks a lot guys

  Hello

  I do not understand the LSI SAS and mptscsi messages are coming inside the guests who are having a controller LSI. I agree to a point that the vmhba0 of LSI in the server maybe nothing to do with errors inside the guests because you do not have virtual machines in the local data store but CF.

  So, let's take a look at the usual suspects:

  1. as Memmad has pointed out, in the vmkernel journal, we can see if the FC lun is seen no problem and is reported.

  2 the ESX does very slowly during the execution of commands like esxcfg-scsidevs - m or esxcfg-rescan vmhbaX [X your CF Adapter]

  3 - is the lun configured for multi path in the face of questions, CF once again, it can be newspapers vmkernel. ?

  4. I'm sure that the paging file will be generated when the FC lun, but they have a check if the last file to update the directory of the virtual machine swap at the present time. This is to eliminate any delay in the swap file in writing of the customer due to CF issues.

  5. There was questions previous similar to yours as VM lose pings, decline in performance, but they were in iscsi and 4.1 KB here

  It seems that the guests are abandoned or their scsi reset commands that seems to be the issue here.

• Shared behavior of the virtual machine on the host system shutdown

  Shared behavior of the virtual machine on the host system shutdown

  Greetings,

  I installed WIn7 - 64 bit host system, WS8 and there seems to be a very nice and high quality configuration. I am very happy.

  There is a shared VM and it's a Setup 64-bit Ubuntu 10.04 Server functioning as a base configuration LAMP for some basic web applications, etc..

  I was unable to find the settings to control the behavior of the VM shared with the system that hosts stop. When I stop the host system, I believe that the common VM is off tension or stop gracefully, I don't know who. What I like best is for the shared VM will not apply instead. The reason is that starting the virtual machine is a bit complicated and requires manual intervention. Whereas, if it is stopped since a State suspended without manual intervention is necessary.

  I found that if there is a loss of power, I can hibernate the host system in time before my battery runs out. Resuming the host hibernate system works correctly and the VM shared within WS8 is back to its previous functional State.

  It would be nice and helpful being able to stop or restart the host system and know that the shared virtual machine has been automatically suspended. So now I have to log on to the user account from the host system and open WS8 and manually suspend the virtual machine before you stop or restart the host system.

  Is there a way to have the shared VM automatically suspended when the host system is stop?

  Thank you for your time and attention.

  You can configure the stop action by editing the following file:

  %ProgramData%\VMware\hostd\vmAutoStart.XML

  If you want to configure the action stop for all virtual machines, find the section of under the section. Change it on hold

  If you want to change the action stop for only this one machine virtual, you must first configure this shared VM to be started automatically (in WS, right-click on the item 'VMs shared' in the library, select "manage computers virtual auto-start '). After doing this, manually change the vmAutoStart.xml. Find the entry for the virtual machine in the section (if you have more than one computer configured to autostart virtual, it will take some more digging to understand what VM to change). Change the entry for this virtual machine to hang.

  Save the file. Reboot the host (not auto-start power actions are only made when the host is restarted). Now when stop you the host, WS should suspend the VM (s)

  As always, manually edit the configuration files is not considered supported its use. Save the file before you edit. Adjust at your own risk.

• ESXi installation before vCenter Server?  How can I get vCenter Server on a virtual machine on ESXi servers?

  My plan for a new vSphere Essentials Plus 5.5 U2a installation is to have the vCenter Server on a virtual machine on the servers of the host on which is installed ESXi.  However, all the installation instructions I found indicate the user to first install the vCenter Server.  How can I get vCenter Server on a virtual machine on ESXi servers?

  Thank you for your help.

  Hi munkyman welcome to communities.

  After you have installed your first ESXi host, open a browser and go to https://your-ESXi-ip-or-FQDN

  You can download the vSphere Client here. It is a windows application that you can install on your desktop. It is often referred to as the "c# Client vSphere" in communities and blog posts, because it is a new implemented in the vCenter Server Web client.

  But for the beginning, install the vSphere Windows Client. You can then launch it and connect directly to your ESXi host. Here you can create your first virtual machine, which can be the VM vCenter (installation of Windows or device, that is you).

  You can use the web client or connect to the Server with the client c# vSphere vCenter VCenter runs.

  Tim

• Replying to a virtual machine within the same site

  I try to install vSphere replication v5.1.  I do this without SRM, but just the OVF appliance (s).  We currently have 8 guests distributed between two groups.  We have a vCenter control all this, and all is listed in a Data Center.  The second group is in our DR site and has different storage mapped to it.  I try to use vSphere replication as a means to keep our important VM replicated to our centre of DR disaster.  Is it possible to do so in the only current configuration?

  I'm having a hard time comes to work.  I have deployed two replication OVF devices and I'm stuck trying to replicate a virtual machine actually.  It gives me an error that the data object is not found.  I thought that I needed to 'Connect' from the local site to the remote site, but since this is all a time installing vCenter, I get an error indicating it cannot connect to itself.

  Is what I'm trying to do possible?  If not, could you let me know what I need to change to make it work properly.  Thank you.

  Hello

  The scenario you describe is supported - you can replicate virtual machines from one host to another within the same VC.

  To do this:

  -you will need to deploy vSphere 5.1 replication for a VC and no specific host

  -VR requires VC 5.1. If you liked VC - standalone VR will not work. If you have more recent VC, for example 5.5, you need RV 5.5

  -For replication within the VC even you don't need to link to the target site.

  -Simply select the computer virtual you want to replicate, when you opened a session in vSphere Web Client connected to the VC, point to the same location - must be available in the list, and select the appropriate data store and move through the wizard.

  Kind regards

  -Martin

• Creating virtual machines on ESXi 5 and move to ESX 4.1

  Hello

  I need to create and configure computers virtual (with operating system and applications) on an environment with vSphere host ESXi 5.0 U1 U1 5.0.

  After that, I want to move the virtual machine to another environment vSphere, located in a branch office, but this time the version is 4.1 U1 (ESX 4.1 U1).

  Do you know if it is supported by VMware? will be the machine working properly?

  Thank you.

  Andrea

  No, it is not necessary because the tools are backward compatible

• How to create disk shared across virtual machines on different hosts

  Hello

  We implement Oracle RAC on two virtual machines, one on each of the two armies for redundancy. For our installation:

  • The two ESXi hosts two SAN access a logical unit number.
  • Two virtual machines on the hosts must have access to a single virtual disk on this LUN (or unit number logic itself) at the same time.

  We tried the following:

  • Creation of a data store associated with the LUN, and then creating a new hard drive on each virtual machine using the same virtual disk on the data store. This operation failed because as soon as a virtual computer runs, the other virtual computer cannot run since the first has a lock on the file from the disk.
  • Creation of a new hard drive on the virtual machine through RDM. This operation failed because only the first virtual machine has this option of disc. Once the ROW has been assigned to the LUN, the other virtual computer cannot create its own RDM for the LUN.

  I'm learning just VMware so I can miss a fundamental method to accomplish this, or perhaps, it is not possible at all. You know a way to create the installer I described?

  Welcome to the community,

  I can not specifically help with the Oracle RAC, however, I would recommend that you take a look at MSCS documentation for how to configure shared disks. There is a difference in the way in which you have installed the VM, for example all VMs on an ESXi host or on different hosts. Please keep in mind that MSCS is a cluster without sharing, which means that only one node at a time has access to a shared virtual disc/RDM.

  André

  PS: I forgot to add the link: http://kb.vmware.com/kb/1004617

• How to move virtual machines from one host to another without full VI and vMotion?

  Hello

  could you help me with a question?

  I have two installed hosts with ESXi 3.5 U5, which are connected to the shared iSCSI (Openfiler) - VMs storage are installed on the storage disk. My requirement is to have a cheap solution of DR - in case of failure of a host, I need to move and start VM on the host of work. How to achieve without going through VMware Infrastructure 3.5 and vMotion?

  I found this article:

  http://www.virtualizetips.com/2010/04/how-to-move-a-VM-without-vCenter-or-storage-VMotion/

  but RCLI needs Infrastructure of VMware ESXi does not have default CLI So, how to move VMs between hosts (of course I mean "cold" move) without byuing any additonal VMware SW? It is generally possible in my situation?

  Thank you.

  ARO

  Danas

  If the virtual machines are running in shared storage (two guests see the same storage iSCSI or NFS) then it's simple. If a host goes down, then look for the data store on the ESXi host work. Navigate through folders for each virtual machine, right-click on the VMX file and add to the inventory. You will then be able to turn on the virtual machine.

  To move a virtual machine from one host to another, as long as both hosts had the same processors, you can pause the VM on the single host, browse and add the virtual machine to the inventory on the second break host and the United Nations.

  If the virtual machines are on local storage, but the two hosts are connected to the same shared storage, clone virtual machines on a daily basis from local storage to shared storage. Use something like ghettoVCB http://communities.vmware.com/docs/DOC-8760 make the clone. In the case of a server failure, you will be able to browse the data store, add to the inventory on the shared storage and switch the cloned machine.