WuGeDe's Posts

I am running build 17491160 now and the problem seems not to be gone here. Metrics per virtual machine are still not available. I have a case open at vmware an they pointed at that kb https... See more...
I am running build 17491160 now and the problem seems not to be gone here. Metrics per virtual machine are still not available. I have a case open at vmware an they pointed at that kb https://kb.vmware.com/s/article/79596 Which in my case is not the problem.    
Here is the answer I got on my case: Below is the reply from our engineering team: This is expected for qlnativefc driver. qlnativefc driver uses one port to support scsi and nvme device. It will... See more...
Here is the answer I got on my case: Below is the reply from our engineering team: This is expected for qlnativefc driver. qlnativefc driver uses one port to support scsi and nvme device. It will create NVMe adapter and scsi adapter for same port. The wwnn and wwpn are same for NVMe and SCSI adapter,   vmhba3 qlnativefc_unstablelink-up fc.2000f4e9d454acac:2100f4e9d454acac (0000:05:00.0) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter vmhba4 qlnativefc_unstablelink-up fc.2000f4e9d454acad:2100f4e9d454acad (0000:05:00.1) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter vmhba5 qlnativefc_unstablelink-up fc.20000024ff54a464:21000024ff54a464  (0000:85:00.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA vmhba6 qlnativefc_unstablelink-up fc.20000024ff54a465:21000024ff54a465  (0000:85:00.1) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA  vmhba64 qlnativefc_unstablelink-up fc.2000f4e9d454acac:2100f4e9d454acac (0000:05:00.0) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter vmhba65 qlnativefc_unstablelink-up fc.2000f4e9d454acad:2100f4e9d454acad (0000:05:00.1) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter If you don't want to use NVMe device, it can set parameter as: $esxcfg-module -s 'ql2xnvmesupport=0' qlnativefc $reboot It will disable nvme adapter.  
Yes you are right. I agree.
Yes @a_p_  I found that vmware KB2127274 also. But it only refers to versions prior to 6.7. If I look at my esx.conf file I can not find these duplicate entries there mentioned in the KB. I opened ... See more...
Yes @a_p_  I found that vmware KB2127274 also. But it only refers to versions prior to 6.7. If I look at my esx.conf file I can not find these duplicate entries there mentioned in the KB. I opened a case and if I got a solution post it here.
Hello @a_p_  Yes I patched this host to the latest patches / updates via Lifecycle Manager.
Hello guys I have an ESXi where my FC HBA is listed as vmhba0 and vmhba1 and also a second time as vmhba64 and vmhba65. Why is that the case? Please have a look at my attached pictures. ESXi is r... See more...
Hello guys I have an ESXi where my FC HBA is listed as vmhba0 and vmhba1 and also a second time as vmhba64 and vmhba65. Why is that the case? Please have a look at my attached pictures. ESXi is running 7.0.1, 17551050 and vcsa is 7.01 17327586 Thank you much for help!  
@vXav thanks for your reply. I found that kb too and checked for that. That is not the problem in my case.
@Nubai none so far. @DARKINF mine are perfectly in sync to our centralized gps time source
Hello guys I updated my vcsa from 6.5 to 7.0.1. In the update section the default predefined baselines "critical patches" and "host security patches" are still at esxi version 6.5.0. I already hav... See more...
Hello guys I updated my vcsa from 6.5 to 7.0.1. In the update section the default predefined baselines "critical patches" and "host security patches" are still at esxi version 6.5.0. I already have some esxi on 7.x. What went wrong? How to get these baslines to esxi 7.x? Thanks for help!    
Same issue here. No VM metrics shown. Any updates on that topic?  
sapreaper​ thank you for your reply. i was wondering because i did the steps you did but the peer and witness were sill there and powered on after.
sapreaper What have you done in detail after you ran into that error? Have you powered off and deleted the already deployed peer and whitness before you did the steps mentioned in your post?
@all I can not recommend to enable this ESXi Side-Channel-Aware-Shedule until VMware has fixed ALL the flaws that comes with it. Planning Phase: Assess Your Environment The Concurrent-con... See more...
@all I can not recommend to enable this ESXi Side-Channel-Aware-Shedule until VMware has fixed ALL the flaws that comes with it. Planning Phase: Assess Your Environment The Concurrent-context attack vector is mitigated through enablement of the ESXi Side-Channel-Aware Scheduler which is included in the updates and patches listed in VMSA-2018-0020. This scheduler is not enabled by default. Enablement of this scheduler may impose a non-trivial performance impact on applications running in a vSphere environment. The goal of the Planning Phase is to understand if your current environment has sufficient CPU capacity to enable the scheduler without operational impact. The following list summarizes potential problem areas after enabling the ESXi Side-Channel-Aware Scheduler: VMs configured with vCPUs greater than the physical cores available on the ESXi host VMs configured with custom affinity or NUMA settings VMs with latency-sensitive configuration ESXi hosts with Average CPU Usage greater than 70% Hosts with custom CPU resource management options enabled HA Clusters where a rolling upgrade will increase Average CPU Usage above 100% Important: The above list is meant to be a brief overview of potential problem areas related to enablement of the ESXi Side-Channel-Aware Scheduler. The VMware Performance Team has provided an in-depth guide as well as performance data in KB55767. It is strongly suggested to thoroughly review this document prior to enablement of the scheduler. Note: It may be necessary to acquire additional hardware, or rebalance existing workloads, before enablement of the ESXi Side-Channel-Aware Scheduler. Organizations can choose not to enable the ESXi Side-Channel-Aware Scheduler after performing a risk assessment and accepting the risk posed by the Concurrent-context attack vector. This is NOT RECOMMENDED and VMware cannot make this decision on behalf of an organization. This is simple ridicolous what VMware here expects of its customers. Regards