zXi_Gamer's Posts

Hi Thamilarasan,                             Welcome to the communities, As Rommel Humarang suggested the feature is called as VMdirect path or Passthrough in other words, however, you have ... See more...
Hi Thamilarasan,                             Welcome to the communities, As Rommel Humarang suggested the feature is called as VMdirect path or Passthrough in other words, however, you have to  make sure that the card is not an onboard card, but a PCI-Express one to make this feature work and more importantly your processor should support vt-d [Intel] , Iommu [AMD] If possible, do post our the esxcfg-nics -l output and your processor info, we can suggest the possibility of pass-through
Not quite from the screenshot. But it looks like something to do with usb? You also said you have faced crashes with previous releases of ESXi, it would be good to run a system health check on th... See more...
Not quite from the screenshot. But it looks like something to do with usb? You also said you have faced crashes with previous releases of ESXi, it would be good to run a system health check on the server and update it to latest BIOS
VMware KB: ESXi 5.5 host fails with a purple diagnostic screen and the error: Usage error in dlmalloc i have seen this error multiple times across  the communities and also the vmware kb addres... See more...
VMware KB: ESXi 5.5 host fails with a purple diagnostic screen and the error: Usage error in dlmalloc i have seen this error multiple times across  the communities and also the vmware kb addresses it.. Seems some driver is causing it across the systems. can you take a look at the kb and find out what driver in your system needs to be updated?
You might need to contact support if you have contracts..
IBM 3650 is supported till 5.5 U1 VMware Compatibility Guide: System Search Can you specify which server and which CPU you are trying to match up for installing 5.5?
If the rebuild has been done and is in vmfs partition "fb", then esx should detect it automatically and present  you in configuration>storage. If not, you can try for a rescan on that adapter man... See more...
If the rebuild has been done and is in vmfs partition "fb", then esx should detect it automatically and present  you in configuration>storage. If not, you can try for a rescan on that adapter manually
i have not installed a rollup bundle, but you can try: cat /etc/vmware/.buildinfo which should be different for update/rollup builds
Does this answer your question> http://www.virten.net/2013/04/intel-cpu-evc-matrix/
There seems to be a hardware problem related to hpsa card. This is causing the NMI interrupts and one of the pcpus gets locked up failing to update the TLB. Please do ask the customer to run a di... See more...
There seems to be a hardware problem related to hpsa card. This is causing the NMI interrupts and one of the pcpus gets locked up failing to update the TLB. Please do ask the customer to run a diagnostics on the server, if possible
Can you check on the error messages of the datastore 4ebbfcf1-3c0c4770-9fa6-001c23d7bce2 while booting?? Also, can you check the vmdks of the vms are still in tact.?
I want to know in which scenario this message will be displayed Though I dont know exactly the reason, one possible theory could be heapfree is called and again dlmfree is called. it could b... See more...
I want to know in which scenario this message will be displayed Though I dont know exactly the reason, one possible theory could be heapfree is called and again dlmfree is called. it could be dlmfree is trying to free the same regions freed by heapfree and getting PF or dlmfree is trying to access invalid page which could have been marked noaccess by kernel, but the driver does not know it yet. It will be helpful if i get dlmalloc.c file to debug further. I am not sure if you would get access to dlmalloc.c from VMware, but dlmalloc.c is opensourced from linux http://www.cs.virginia.edu/~wh5a/personal/House-0.8.92/kernel/user/dlmalloc.c
It does look like a driver related issue: VMware KB: ESXi 5.5 host fails with a purple diagnostic screen and the error: Usage error in dlmalloc  The above is for cnic driver.
since the upgrade to ESXi 5.5 every time I reboot the host it will reboot with maintenance mode enabled Going by the scenario that you are using plain install instead of autodeploy, can you ... See more...
since the upgrade to ESXi 5.5 every time I reboot the host it will reboot with maintenance mode enabled Going by the scenario that you are using plain install instead of autodeploy, can you check the /var/log/syslog.log file and look for "maintenance" word and find out which activity leads to host being in maintenance mode.? Also, are the hosts upgraded by VUM?
Upgraded to   ESXi 5.5 Update 1, messages are no longer spewing..
No Luck there.. Still getting the messages...
On a side note, where the screen comes up to allow some intervention and has the Shift+o in the lower right corner, there is now a line for "shift+r.to enter recovery mode" Yes the option Sh... See more...
On a side note, where the screen comes up to allow some intervention and has the Shift+o in the lower right corner, there is now a line for "shift+r.to enter recovery mode" Yes the option Shift +O will be present during every boot. This is to facilitate troubleshooting any boot time issues or to configure the box to boot with user set advanced settings...
To remove the cache involvement, I can suggest to remove the memory modules and reinsert them again and try it out. Or go for a full cold down shutdown and start the system It seems for some s... See more...
To remove the cache involvement, I can suggest to remove the memory modules and reinsert them again and try it out. Or go for a full cold down shutdown and start the system It seems for some strange reason, the boot is still pointing to the installation boot record.
Have you tried disconnecting or removing the media which you are using to install when you reboot the box?
Can you provide the vmware.log and the vmx file of the VM?
La raison pour laquelle vous trouvez les fenêtres redémarrage continu est qu'il se bloque en raison d'un ensemble de matériel incorrecte. Cela peut aller de contrôleur ou processeur trop. Dans vo... See more...
La raison pour laquelle vous trouvez les fenêtres redémarrage continu est qu'il se bloque en raison d'un ensemble de matériel incorrecte. Cela peut aller de contrôleur ou processeur trop. Dans votre poste de travail et d'accueil, ce qui est le CPU? Aussi, lorsque Windows démarre, appuyez sur F8 pour aller en mode sans échec et de trouver le module à laquelle les fenêtres commence à tomber en panne et redémarrage