Skip to main content

Posts

Showing posts from September, 2018

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-...

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 versi...