zXi_Gamer's Accepted Solutions

esxupdate -b cross_cisco-vem..... remove VMware KB: Upgrading an ESX host with VEM400-200909001-BG installed fails if host is part of DVS more info 
Hi and welcome to the communities, It seems that the vmware tools have been uninstalled either during upgrade or manual. Can you confirm if sudo is not the prob here by giving sudo /usr/bin/vmwar... See more...
Hi and welcome to the communities, It seems that the vmware tools have been uninstalled either during upgrade or manual. Can you confirm if sudo is not the prob here by giving sudo /usr/bin/vmware-config-tools.pl
vicfg-cfgbackup.pl is supported only on embedded platforms.
Check with RVC, Solarwinds.
~ # cat /etc/vmware/esxupdate/esxupdate.conf [platform] product = embeddedEsx version = 4.0.0 build = 1228870 [visor] bootbankdir = /bootbank altbootbankdir = /altbootbank ... See more...
~ # cat /etc/vmware/esxupdate/esxupdate.conf [platform] product = embeddedEsx version = 4.0.0 build = 1228870 [visor] bootbankdir = /bootbank altbootbankdir = /altbootbank packagingdir = /tmp/stage stagedir = /tmp/stage/firmware oemstgdir = /tmp/stage/oemstage customstgdir = /tmp/stage/customstage distribution = ESXi [log] level = DEBUG file = /locker/db/esxupdate.log size = 1024000 [default] # Float # of seconds to timeout for downloads, 0.0 = no timeout timeout = 30.0 retry = 5 cachedir = /var/tmp/cache defaultcachemb = 400 mincachemb = 100 ~ # cat /etc/vmware/esxupdate/esxupdate.conf [platform] product = embeddedEsx version = 4.0.0 build = 1228870 [visor] bootbankdir = /bootbank altbootbankdir = /altbootbank packagingdir = /tmp/stage stagedir = /tmp/stage/firmware oemstgdir = /tmp/stage/oemstage customstgdir = /tmp/stage/customstage distribution = ESXi [log] level = DEBUG file = /locker/db/esxupdate.log size = 1024000 [default] # Float # of seconds to timeout for downloads, 0.0 = no timeout timeout = 30.0 retry = 5 cachedir = /var/tmp/cache defaultcachemb = 400 mincachemb = 100 ~ # vmware -v VMware ESXi 4.0.0 build-1228870 ~ # Good luck
If so, does anyone know a particluar site that I might be able to get the correct version of ESXi 5.1 for this dell PowerEdge R820 server. Try this site: VMware Front Experience: ESXi-Custo... See more...
If so, does anyone know a particluar site that I might be able to get the correct version of ESXi 5.1 for this dell PowerEdge R820 server. Try this site: VMware Front Experience: ESXi-Customizer Struggling Graduate Student Get ready to struggle more on completing graduation
So will formatting that C:\ drive will it affect datastore on which that VM is located..... No. not at all. It will be the vmdk file residing on the datastore which will get changed.
I remember using vcli for the same. Check out this kb if helpful
Esxi 5.1 host with 2x8 core processors, giving a total of 32 logical processors. it sometimes sees spikes of 100% across all vCPU. From, the esxtop or from vsphere client, find out who is ho... See more...
Esxi 5.1 host with 2x8 core processors, giving a total of 32 logical processors. it sometimes sees spikes of 100% across all vCPU. From, the esxtop or from vsphere client, find out who is hogging all the cpu cycles. If we allocated more vCPU than physical cores to one single guest, would this mean that it would work fine for certain loads Might not be a good option in a environment where latency is not appreciated. I guess it just depends if Vmware can communicate to the guest which vCPU are on the same physical core. You can do that by setting the CPU Affinity to the particular VM where the performance is expected more. i managed to convince the relevant parties to just go for more smaller VM's and resource allocation and that has worked well. That is an excellent suggestion too.
There is a fix in Patch 01 of ESXi 5.1 which might be helpful to you in your PSOD case. However, one simple question, if you are making on-board storage controller as pass-through, then is you... See more...
There is a fix in Patch 01 of ESXi 5.1 which might be helpful to you in your PSOD case. However, one simple question, if you are making on-board storage controller as pass-through, then is your ESXi installed on another SCSI/SAS Add on controller?
Hi,      I do understand the LSI SAS and mptscsi messages are coming inside the guests which are having a LSI controller. I can agree to a point that the LSI vmhba0 in the server might have noth... See more...
Hi,      I do understand the LSI SAS and mptscsi messages are coming inside the guests which are having a LSI controller. I can agree to a point that the LSI vmhba0 in the server might have nothing to do with the error messages inside the guests since you do not have the vms in the local datastore but from FC. So, let us take a look at the usual suspects: 1. Like Memmad pointed out, from the vmkernel log, we can see if the FC lun is having any trouble and is being reported. 2. Does the ESX itself perform very slow while running any commands like esxcfg-scsidevs -m or esxcfg-rescan vmhbaX [X adapter of your FC] 3. Is the FC lun configured for multi path facing any issues, again this can be from vmkernel logs.? 4. I am sure that the swap file would be generated on the FC lun, but do have a check if the last updated swap file on the vm directory is having current time. This is to rule out any delay in the swap file writing from the guest due to FC issues. 5. There were earlier issues similar to yours like VM losing pings, slower performance, but they were in iscsi and in 4.1 kb here It does seems that the guests are aborting or resetting their scsi commands which seems to be the issue here.
Like mentioned earlier, ESX would psod in case of PFs or cpu locks but wont restart. Need say, that none of the agents in ESXi would restart the server itself, which could makes us shift the view... See more...
Like mentioned earlier, ESX would psod in case of PFs or cpu locks but wont restart. Need say, that none of the agents in ESXi would restart the server itself, which could makes us shift the view to the hardware itself excluding the intrusion of a person hard resetting the server. Check in the bios/management software for any alerts of Temperature, memory failed modules et al. Also, in vmkernel logs [messages in ESXi 4.1], check for "Booted successfully." which is the start time of the kernel. Again, if the server is bought down by hard methods, or hardware faults by bios, it cant be logged in vmkernel.
Maybe this kb will help you.
Do you agree with me? Is it a good configuration? Yes, I had asked for the outputs to confirm on the driver models.
Hmmm.. there are cims available and monitoring from Adaptec in ESX server. Check out these threads just for feeding the information part of brain http://communities.vmware.com/thread/158690... See more...
Hmmm.. there are cims available and monitoring from Adaptec in ESX server. Check out these threads just for feeding the information part of brain http://communities.vmware.com/thread/158690?start=75&tstart=0 http://www.thomas-krenn.com/en/wiki/Adaptec_RAID_Controller_Monitoring_in_VMware Glad you got your query by using rvtools... cheerios..
Alrighty then.... Lets check the usual suspects: When using vSphere Client to do so, I throws an error as "Error reading Data: the remote server is not available (Errorcode 503)". 1. Chec... See more...
Alrighty then.... Lets check the usual suspects: When using vSphere Client to do so, I throws an error as "Error reading Data: the remote server is not available (Errorcode 503)". 1. Check the firewall settings from the ESX/the client side. 2. Check if the ESXi server dns is resolved and configured properly. it does not open the directory and leaves a blank page (and of course not even the https login/password protection appears). 3. Can you confirm from a different windows machine to check out the windows tcp/ip bug
Windows 7 x32 It does look our old friend has come back. Two checklists 1. Check the VGA driver version of the VM, if it is the case, you need to update the display driver to WDDM dri... See more...
Windows 7 x32 It does look our old friend has come back. Two checklists 1. Check the VGA driver version of the VM, if it is the case, you need to update the display driver to WDDM driver. 2. Make sure that  you are using HW 7 and above. More info here
My sincere apologies. I tried out in a 5.1 environment where the namespace is there. Also, in 5.0, I tested out ethtool -S vmnic0  to be giving similar data.
Well, sorry on my part. esxcfg-vswitch -U vmnicX vSwitchA and again esxcfg-vswitch -L vmnicX vSwitchA When I said vmnicX, I meant to refer the vmnic which is under subject. Do a esxcfg-nics... See more...
Well, sorry on my part. esxcfg-vswitch -U vmnicX vSwitchA and again esxcfg-vswitch -L vmnicX vSwitchA When I said vmnicX, I meant to refer the vmnic which is under subject. Do a esxcfg-nics -l and find out which nic you are facing the issue. Also, when I said vSwitchA or vSwitchB, I meant to say the vSwitch under subject, this you can find out by esxcfg-vswitch -l
nothing on how it does it If the vendors say how it does it, they might end up bankrupt. Just to give a simple explanation, vshield enables the drivers in VMs, These drivers have the unders... See more...
nothing on how it does it If the vendors say how it does it, they might end up bankrupt. Just to give a simple explanation, vshield enables the drivers in VMs, These drivers have the understanding of the corresponding API's which call them. These APIs are endpoints from vendors. The main communication is via vmware tools. While said that, consider instead of having to install antivirus on ALL virtual machines, you can install the AV db in one VM and have the corresponding management software to use the agents to get information on the VMS on what files have been changed, perform scan of all files in VMs. While it is a very basic explanation, look at the attached jpg for a better understanding.