Skip to main content


"Unknown" status showing in host compliance status

There were several practices where we use host profile into our environment to get the compliance among all other ESXi host into the cluster. There are mostly 3 types of status identified to the hostprofile which is attached to the ESXi host. 1) Compliant 2) Not-compliant 3) Unknown As you know when all the features and settings of host profile and ESXi meets perfectly then only status shows as Compliant status. Not-compliance status shows when the hostpofile unable to meet the complete requirement on the host and some feature are missing. Unknown status is the one which suspect even when you have ESXi host into the Compliance status or sometime could be in Not-compliant status. There are several indentified cause for that. Most of the time we found that all good from ESXi UI and hostprofile where all the parameters are meet successfully and even then host profile status shows as "UNKNOWN" status. In my case i found one glitch where the dvs configuration

RAM Disk Full Due To Inodes In ESXi Host

Last week I got into issue where one of my ESXi host was prompting error while creating virtual machine. I verified the task and events of ESXi host and found below error generating while creating Virtual machine "A general system error occured: Failed to open "/var/log/vmware/journel/ for write: There is no space ". While further digging, I identified the ESXi host from where its generating this error from Task and Event section in vCenter. Tried to take SSH of the question ESXi host but its was inaccessible via putty. However, ESXi host was up and running fine. Last option left to access the ESXi host from its management console which is ILO as its ESXi installed on HP server. Also you can try accessing the SSH via other ESXi host or Linux machine using below command ssh -T servername. However, this will not give your prompt but you can type the command to get the output, but that was not giving any luck at that time so we use ILO for further troublesho

RAM Disk full on ESXi host

Sometime we used to get issue where were are not able to perform vMotion or logging was unable to write under /var/log.. While trying to do some normal things – like vMotion. I noticed an error which states just “A general system error occurred.”  On further investigation, I found that the underlying message was an out of disk space message while trying to proceed with a Storage vMotion. Observations during issue While vMotion   – “A general system error occurred:” While performing Storage vMotion  – “/var/log/vmware/journal/xxxx error writing file. There is no space left on the device.” Steps during troubleshooting Go to Configuration tab on host in vCenter client, go to Security Profile, click Properties link on the Services section. Scroll down to SSH and highlight – click options – click start to start SSH service. Use putty or reflections to ssh to the host. If you get a connection rejected – root filesystem ramdisk is probably full. Go to console (either throug

Monitoring VCSA & PSC disk partitions from vRop's

In our day to day life we encounter many disk alert issue on different operating system when they move above predefined threshold size. Here, in this article we go through how we can set alert and notification of disk partitions of VCSA and PSC. Here we'll take example of VCSA 6.5 ( Appliance) which has following partitions in Guest OS as mentioned in Fig.1 Figure:1 Here we'll set alert of partitons like /storage/seat , /storage/db, /storage/autodeploy, /storage/log etc.. To start we defined we set of steps. Overall process of creating alert definition are below:   Create a Symptom > Add these symptoms to Alert Definition > Then create a Notification for the Alert Definitions What is Symptom: The symptom sets comprise an expression that is evaluated to determine if an alert should be triggered. To add one or more symptoms from the symptom list to an existing symptom set, drag the symptom from the list to the symptom set. To create a new symptom

Oracle Linux VM unable to boot after P2V conversion.

Recently, I was having issue where I had decided to migrate one of my Oracle Linux machine which was running in HP Blade server to visualize and migrated through VMware converter. Migration went successful and VM migrated successfully without any error but while powering on the Oracle Linux VM its failed with below error. To resolve this issue I tried to boot the VM with Linix iso and run into rescue mode. Please find below steps which I followed to boot the VM successfully. 1)      Mount the linux iso to the VM and boot it from CD 2)      At the first prompt, type linux rescue and press Enter. 3)      Change root to the mounted installation. Type chroot /mnt/sysimage and press Enter 4)      Type   ls /boot 5)      There you will see lots of initrd-xxxxx.EL.img files with different name. 6)      To verify the correct initrd-file used to /boot. Type cat /etc/grub.conf, and press Enter. 7)      From the location /etc/grub.conf I found there are t

Total Logon Time metric display "No Data" in vRops for Horizon dashboard

Last week I was working with one of my customer who has recently upgraded their vRops environment to 6.7 version.  Their environment consist of  VDI environment running on VMware Horizon. Here in vRops environment they have default Horizon dashboard as they have configured Horizon adapter for their VDI environment. From some time we are getting issue into Horizon dashboard where they were not able to see Total Logon Time metric display where its display "No Data" as seen below To resolve the issue of " No Data" there is a solution which works for me and recommended by VMware. This issue identified when we not enable the time profiler. The logon time is calculated by 'First_idletime - logon_starttime' The 'logon_starttime' is retrieved from DB and 'first_idletime' is retrieved from DA (Desktop agent). Its because the DB is not consistent with DA. This will cause the "logon_startime" be sm

Issue with VMware Tools 10.3.0

There is an issue identified with VMware Tools 10.3.0 release that can cause the ESXi host to PSOD. Multiple issues, including the PSOD,  have been brought in attention with the VMXNET3 driver that shipped with the VMware Tools 10.3.0 release. In response to this, VMware is puling this release from availability through myVMware. In order to be exposed to these issues, all of the following must be true: ·        Windows 8/Windows Server 2012 or higher ·        VMXNET3 network adapters in the VM hardware configuration ·        VM Hardware version 13 ·        ESXi 6.5 hosts ·        VMware Tools 10.3.0 installed ·        VMware Tools 10.3.0 includes the applicable VMXNET3 driver version. ·        The problematic VMXNET3 driver is version VMware been made aware of issues with the VMXNET3 driver released in VMware Tools 10.3.0, and that we recommend downgrading to VMware Tools 10.2.5 for the configurations outlined above. You may also refere

Major Update to VMware Certification Naming

Major Update to VMware Certification Naming and Schedule VMware have announced a major shift in the naming and versioning for all certifications - alignment to the year in which a certification is earned, and a new annual release/update schedule for all VCP, VCAP, and VCDX certifications! Naming Convention Using the Data Center Virtualization (DCV) track, here's an example of the the next generation of certification names: VCP-DCV 2019 VCAP-DCV Design 2019 VCAP-DCV Deploy 2019 VCDX-DCV 2019 Certifications launched from this month will use this new convention, starting with the release of: VMware Certified Professional – Desktop and Mobility 2018 (VCP-DTM 2018) VMware Certified Advanced Professional – Data Center Virtualization Deploy 2018 (VCAP-DCV Deploy 2018) VMware Certified Advanced Professional – Cloud Management and Automation Deploy 2018 (VCAP- CMA Deploy 2018) Release Schedule As you might expect from such a naming convention, there's also a switch

LT1F Vulnerability (L1TF) VMware

I would like to inform about important issue: Intel L1 Terminal Fault Vulnerabilities which high impact to vSphere Infrastructure. That issue had been announced at 00:00 AM today (10:00 AM PDT). This new class of vulnerabilities can occur on current and past Intel processors (from at least 2009 - 2018) when affected Intel microprocessors are speculating beyond an unpermitted data access. Reference: This new class of vulnerabilities can occur on current and past Intel processors (from at least 2009 - 2018) when affected Intel microprocessors are speculating beyond an unpermitted data access. By continuing the speculation in these cases, the affected Intel microprocessors expose a new side-channel for attack, allowing a malicious VM to infer data in the hypervisor and other VM’s running on a core. The most severe of the three vulnerabilities (CVE-2018-3646: L1 Terminal Fault – VMM) im