pkvmw's Posts

Hi, as @stadi13 correctly stated there's currently no implementation. Allowing ESXi to get sensor information requires a plugin/service from the hardware vendor, which isn't available as of today un... See more...
Hi, as @stadi13 correctly stated there's currently no implementation. Allowing ESXi to get sensor information requires a plugin/service from the hardware vendor, which isn't available as of today unfortunately. Passing through the data to a VM isn't technically possible. To my knowledge those sensors are e.g. queried using ACPI and this is not a device you can passthrough. (To my knowledge this is pre-defined memory address space where devices/BIOS/UEFI write the information to) Regards, Patrik
Hi, to downgrade the driver, as @CLINZ stated, you need to remove the newer driver (without reboot should be fine) and install the previous one. After a reboot the previous driver will be loaded the... See more...
Hi, to downgrade the driver, as @CLINZ stated, you need to remove the newer driver (without reboot should be fine) and install the previous one. After a reboot the previous driver will be loaded then. As the firmware is developed and flashed using tools from the hardware vendor, I'd recommend to discuss and confirm necessary steps with the hardware vendor. Some NICs have different software components on their physical NICs, so downgrades could be cause more issues than solve. Therefore, better verify with hardware vendor first. Regards, Patrik
Hi, beside I/O Controller being supported, also your other components like the hardware model, CPU, NIC, etc with their corresponding driver-, firmware-, and ESXi-version combination should be liste... See more...
Hi, beside I/O Controller being supported, also your other components like the hardware model, CPU, NIC, etc with their corresponding driver-, firmware-, and ESXi-version combination should be listed. That being said, VMware does not evaluate hardware compatibility. The hardware vendor approaches VMware using dedicated channels to certify their hardware for their own driver and firmware, which e.g. requires to run a test suite and pass tests. So you would need to reach out to your hardware vendor to either get a official written statement with approval it is supported or, even better, to start the certification process with us at VMware. But as it appears to be a older model and ESXi 6.5 is Out-Of-General-Support in just October 2022, I honestly wouldn't have too much hope. Regards, Patrik
Just to add, you could also leave the vSAN services untouched and exclude logs using logfilter: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-D0D77526-65DC-4D08-A52F... See more...
Just to add, you could also leave the vSAN services untouched and exclude logs using logfilter: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-D0D77526-65DC-4D08-A52F-51D5B0DAF8C3.html Could make things easier when you're updating and those VIBs will get re-installed. However not tested myself.
Hi all, I've been working on the SR and thought I'll keep everyone updated. I noticed that there're too much modules present, compared to my local setup. So we went ahead removing all modules, reins... See more...
Hi all, I've been working on the SR and thought I'll keep everyone updated. I noticed that there're too much modules present, compared to my local setup. So we went ahead removing all modules, reinstalling PowerCLI modules clean and the cmdlet was working again. Basically, the steps were: 1. To remove all VMware modules: # Get-Module -Name VMware* -ListAvailable | Uninstall-Module 2. Check if everything was removed: # Get-Module -Name VMware* -ListAvailable 3. Check if there're still modules left 3.1. User modules: %UserProfile%\Documents\WindowsPowerShell\Modules 3.2. System-wide modules: C:\program files\WindowsPowerShell\Modules 4. Attempt a clean installation of PowerCLI Regards, Patrik
Hi @IRIX201110141, today vCenter Update 3a was released to address this issue. See release notes here: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3a-release-notes.htm... See more...
Hi @IRIX201110141, today vCenter Update 3a was released to address this issue. See release notes here: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3a-release-notes.html Regards, Patrik
Since quite some times, especially with vSphere 7.0 GA, using SD-cards wasn't the preferred way going forward, even when it wasn't clearly stated somewhere. Now vSphere 7.0 Update 3 just now makes th... See more...
Since quite some times, especially with vSphere 7.0 GA, using SD-cards wasn't the preferred way going forward, even when it wasn't clearly stated somewhere. Now vSphere 7.0 Update 3 just now makes the obvious official to deprecate boot from SD-cards. While it's still supported for vSphere 7.x as of today, the support to boot from SD-cards might be removed in a next major release. )(Unclear if the ability to boot from such devices might be removed as well.) I'm not sure where you've got the data and evidence from, but from what I know and have seen the issue introduced in 7.0 U2a was fixed in 7.0 U2c. Even when there're similar messages like "state in doubt", it doesn't necessarily mean it's the exact same underlying root cause. The behavior can be seen in many, many different scenarios - not just with the USB sd-card bug. Regards, Patrik
Hi @jakorsme, as you've read in KB https://kb.vmware.com/s/article/83647 a fix (further checks) was added to ESXi 7.0 U2c, and you installed 7.0 U2a (so not containing the fix). As your VMFS6 is not... See more...
Hi @jakorsme, as you've read in KB https://kb.vmware.com/s/article/83647 a fix (further checks) was added to ESXi 7.0 U2c, and you installed 7.0 U2a (so not containing the fix). As your VMFS6 is not VFAT, it would have not converted it to OS-DATA.  Beside this, don't put the scratch location to a datastore root. To my knowledge it isn't best-practise. Regards, Patrik
Hi, the fixed matrix on the bottom of the site shows it's fixed in 6.7 U3o: https://www.vmware.com/security/advisories/VMSA-2021-0020.html The KB article I linked earlier at https://kb.vmware.com/... See more...
Hi, the fixed matrix on the bottom of the site shows it's fixed in 6.7 U3o: https://www.vmware.com/security/advisories/VMSA-2021-0020.html The KB article I linked earlier at https://kb.vmware.com/s/article/2143838 shows that version number 6.7.0.50000 corresponds to the name 6.7 Update 3o. tl;dr: Yes, it is. Regards, Patrik
Hi, as you stated, you are currently running on 6.7.0.50000. So you can't update with the ISO of version 6.7.0.50000-18485166-patch-FP, because you're already running this specific version. There i... See more...
Hi, as you stated, you are currently running on 6.7.0.50000. So you can't update with the ISO of version 6.7.0.50000-18485166-patch-FP, because you're already running this specific version. There is no newer release than 6.7.0.50000 to date - also see the vCenter versions list at https://kb.vmware.com/s/article/2143838. If you want to upgrade your VCSA, follow the upgrade procedure as documented: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.upgrade.doc/GUID-30485437-B107-42EC-A0A8-A03334CFC825.html Regards, Patrik
The vmx-coredumps generated when VMs crash can be analyzed from the VMware Support, hence I'd recommend filing a SR to get this investigated. Especially if this is a re-occurring behavior. Otherwise... See more...
The vmx-coredumps generated when VMs crash can be analyzed from the VMware Support, hence I'd recommend filing a SR to get this investigated. Especially if this is a re-occurring behavior. Otherwise it's pretty hard to guess to why the VMX world might have crashed. Regards, Patrik
Hi, by default you should rather use "xterm" (instead of e.g. "xterm-256color"), then it should work as well. Not sure if "linux" is a valid terminal type, to be honest. Regards, Patrik
Hi, obvious question: Do you have HA enabled on your vCenter? Regards, Patrik
Hi all, I know it's not really helpful, but just to add: ESXi itself (or the CIM server) can't directly read the sensor data from the hardware, because each hardware vendor has their own unique hard... See more...
Hi all, I know it's not really helpful, but just to add: ESXi itself (or the CIM server) can't directly read the sensor data from the hardware, because each hardware vendor has their own unique hardware and ways to get the required data. Therefore sfcb loads proprietary components from hardware vendors, where the 3rd-party plugins (from a ESXi-perspective) read out the information. When this 3rd party crashes, also VMware can't really analyze the dumps as it contains closed source from the hardware vendor. I can imagine HPE's components here might try to do something specific, which is not designed for their Gen8 hardware, which causes it to crash. Also unsupported, but you could try sfcb/CIM VIBs from 6.x under 7.x - never tried, but maybe this works out. On my private HPE DL360p Gen8 machines the sensors seems to work: I have installed HPE 7.0 GA ISO, then updated via VMware vanilla images up to 7.0 U2c. (So the CIM providers from HPE should still be stuck at 7.0 GA). Not the fanciest way, but as it's just older private lab... Regards, Patrik  
Hi @TheCiscoKid.  maybe the datastore itself does have some issues, like metadata corruption. Can you check /var/run/log/vmkernel.log on your ESXi host if you can see any log messages mentioning som... See more...
Hi @TheCiscoKid.  maybe the datastore itself does have some issues, like metadata corruption. Can you check /var/run/log/vmkernel.log on your ESXi host if you can see any log messages mentioning some (metadata) corruption? (e.g. grep -i "corruption" /var/run/log/vmkernel.*) Regards, Patrik
HI @ajlassi123, for some more detailed, official instructions and analysis (with the coredump provided) I'd recommend raising an official SR. The stacktrace looks a bit the same as in https://kb.vm... See more...
HI @ajlassi123, for some more detailed, official instructions and analysis (with the coredump provided) I'd recommend raising an official SR. The stacktrace looks a bit the same as in https://kb.vmware.com/s/article/50357, at least some of the same code functions involved. This one was fixed in ESXi 6.5 Patch 2, and I also can see a note that there might be similar PSOD which was addressed in 6.5 Update 3, maybe that's where the suggestion to update comes from. However you seem to run ESXi 6.5.0 U1 from mid-2017. So updating might be a good idea anyway. Verify the supportability with your hardware model and driver/firmware as well. Regards, Patrik
@mbartle For your concern, the build number is not relevant. The ESXi offline bundle (the ZIP file) was simply built/created AFTER the vCenter-ISO, hence the it has a higher build number. You don't ... See more...
@mbartle For your concern, the build number is not relevant. The ESXi offline bundle (the ZIP file) was simply built/created AFTER the vCenter-ISO, hence the it has a higher build number. You don't need to check build numbers (at least I don't know any scenarios where relevant). Checking the "public version naming" and supportability via https://interopmatrix.vmware.com is enough. Regards, Patrik
Hi @JM010101, ah, I see. This error is completely normal and was always there. The SCSI opcode 0x85 is "ATA PASS-THROUGH(16)", which is used to query SMART values from the storage device. As sdcards... See more...
Hi @JM010101, ah, I see. This error is completely normal and was always there. The SCSI opcode 0x85 is "ATA PASS-THROUGH(16)", which is used to query SMART values from the storage device. As sdcards/USB controllers don't understand this SCSI code, the SCSI command fails with "ILLEGAL REQUEST" what ESXi simply reports with this message. (To parse SCSI codes the site at https://www.virten.net/vmware/vmware-esxi-scsi-sense-code-decoder-v2/?scsiCode=failed+H%3A0x0+D%3A0x2+P%3A0x0+valid+sense+data%3A+0x5+0x0+0x0 is quite handy) These are just periodic attempts where ESXI queries SMART data from devices which don't support SMART. Nothing to worry about at all. Regards, Patrik
Hi @JM010101 , what failures are you referring to? Can you post an excerpt/a few lines of the messages you refer to? Regards, Patrik
You're welcome, @HCBV! Glad you mentioned it. There's unfortunately no ESXi 7.0 U2c ISO available for direct download. I'm not aware about the reasoning behind, but I do know there're discussions on... See more...
You're welcome, @HCBV! Glad you mentioned it. There's unfortunately no ESXi 7.0 U2c ISO available for direct download. I'm not aware about the reasoning behind, but I do know there're discussions ongoing. You can patch either via VCSA, or also download the Offline Bundle for 7.0 U2c over here: https://customerconnect.vmware.com/patch/. Using the latest available ESXi ISO and the offline bundle you can also create your own custom U2c ISO if required - see more details about Image Builder here: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-48AC6D6A-B936-4585-8720-A1F344E366F9.html, or via vLCM: https://williamlam.com/2021/03/easily-create-custom-esxi-images-from-patch-releases-using-vsphere-image-builder-ui.html  Regards, Patrik