Hi bmstewart
Yes upgrading the brcmfcoe to version 12.0.1216.4 has fixed this issue for me. It will be worth checking if the ESXi host has an old driver installed which is why you are seeing the warning. If the driver is installed but not loaded then disabling the driver should also fix these warnings.
Cheers, Onil
Hello,
i can confirm Lionel's idea.
Here it happened after upgrading to ESXi 6.7 and changing the password. The inventory software "hammered" on the server trying to check the inventory.
After removing the device in the inventory software and rescanning the server the WebAccess worked again.
I've had a Samsung EVO 970 Plus 1 TB installed in my EXSI 6.7 host. This is formatted as a VMFS6 datastore called NVME. I also have a datastore that is SSD backed by RAID1.
I'm sorry if I come across as a newbie. My VM's are for webhosting, should I place the entire VM on the NVME, or place it on the SSD, and create a second volume is that is placed on the NVME?
The reason I ask this is because I'm worried that NVME may not be reliable? From what I read about them they are best suited for temporary data / caching?
Hello,
I am trying to install ESXI 6.7 U3 Fujitsu ( matching with hardware) but once the set up is running, I have the error message "no such file: '/KS.cfg'
I have tried to install 6.5 U2 but no luck.
Any idea to get it ?
Thank you
Wow - thank you for this guide!
I followed it all the way through and it worked as described!
I thought I had maxed out my motherboard using a USB Datastore for an OmniOS/Napp-it VM and passed through the SATA controller. It seamed such a waste to lose all the USB ports, but now I can pass through an external USB drive to my backup VM for backup copies.
I noticed that If a USB device is removed and reconnected, the device is not automatically re-enabled for passthrough and not recognised by the VM. To reconnect the device I have to rerun the command:
localcli hardware usb passthrough device enable --device [Bus:Dev:VendorID:ProductID]
and then in ESXi, remove (if device is still listed) and re-add the device
The device then re-appears in the VM, without restart.
Is there a way to allow the device to be automatically re-enabled for passthrough and reconnect to the VM?
Thanks again!
To be honest - no idea. I am just a private user of the free ESXi and far from being a pro for this product. Happy that everything runs as it should now. Hope you can find a solution for your problem as well. Best of luck!
I also noted that after a reboot of the ESXi the following commands need to be re-executed in order to allow the pass-through of USB devices again.
Not 100% sure if it might work if I just re-enable the usbarbitrator service to start automatically (-> need to check):
[root@esxi:~] export PATH=/bin:/sbin:/usr/bin:/usr/sbin
[root@esxi:~] USBARBITRATOR=/usr/lib/vmware/bin/vmware-usbarbitrator
[root@esxi:~]
[root@esxi:~] USBARBITRATOR_TAG=usbarbitrator
[root@esxi:~]
[root@esxi:~] USBARBITRATOR_RP="usbArbitrator"
[root@esxi:~]
[root@esxi:~] MAX_RETRIES=5
[root@esxi:~]
[root@esxi:~] PASSTHROUGH_DEV=/vmfs/devices/char/vmkdriver/usbpassthrough
[root@esxi:~] /sbin/watchdog.sh ++memreliable,group=${USBARBITRATOR_RP} -d -s "${USBARBITRATOR_TAG}" -t "${MAX_RETRIES}"
"${USBARBITRATOR}" -t "${MAXIMUM_SUPPORTED_CLIENTS_PARAM}"
[root@esxi:~] localcli hardware usb passthrough device list
UsbUtil: VmkuserCompat_PClose in UpdateDeviceNamesfailed, reason: Bad file descriptor
Bus Dev VendorId ProductId Enabled Can Connect to VM Name
-----------------------------------------------------------------------
1 2 76b 3021 true yes OmniKey AG CardMan 3121
1 3 8087 a2a true yes Intel Corp.
1 4 152d 1561 false no (passthrough disabled) JMicron Technology Corp. / JMicron USA Technology
Corp. JMS561U
[root@esxi:~]
Please go with below link how to use kickstart and requirement to install ESXi.
Thanks for the reply. I noticed that VMware has updated that page to indicate that it's not only HP hardware, and I have verified we do have the old driver on the hosts (not sure if it's active/loaded or not).
I'm not sure why VMware has not pushed out the updated driver into the normal update repositories. I did add it to a new host extension baseline and applied that baseline to our hosts, so I should be able to just apply the update easily, when I get the maintenance window to do so.
HP Blade BIOS Policy
The following BIOS settings are recommended for HP Blades running ESXi:
Enable Turbo Boost
Enable Hyper-threading
Verify that all ESXi hosts have NUMA enabled in the system BIOS. In some systems (for example, HP Servers), NUMA is enabled by disabling node interleaving. Please consult your server hardware vendor for the applicable BIOS settings for this feature.
Enable advanced CPU features, such as VT-x/AMD-V, EPT, and RVI.
It is a good practice to disable any devices that are not used as serial ports.
Set Power Management settings from the default Balanced to Custom.
In Advanced Power settings, change Memory Performance from Balanced to Maximum Performance.
http://jamesdelaney.co.uk/blog/2018/09/03/bios-settings-for-esxi-on-hp-hpe-servers/
______________________
installing HP NMI driver to , ESXi automatically halts the server when an NMI occurs and show PSOD with this massage :
Panic requested by 3rd party NMI handlers ________________________
Enabling 44-bit Address mode for >1 TB memory support in VMware ESXi
I might investigate further at some point in the future, but for now I'm happy.
I had tried restarting the host and simply re-enabling the USB arbitrator service
/etc/init.d/usbarbitrator start
Output:
UsbUtil: Attempting to reserve for VMkernel USB adapter(s): vmhba33
Errors:
Rescan complete, however some dead paths were not removed because they were in use by the system. Please use the 'storage core device world list' command to see the VMkernel worlds still using these paths.
usbarbitrator started
Hostd must be restarted to enable USB passthrough functionality on any VM. After hostd is restarted, to enable USB passthrough functionality on a powered on VM, the VM must be powered off and powered on again.
and it broke the USB Datastores, I restarted the host and the USB Datastores were back up.
I also tried to enable the USB Arbitrator after entering your commands, it then outputs:
usbarbitrator already running
no change
On each reboot of my host, the USB device's Dev number changes, so I would need to check on reboot and adjust the enable/disable commands accordingly.
I would like to write a batch script that runs on ESXi host startup, to pass through all USB devices except for specific devices used for USB Datastores. I have no idea where to start with this though.
Even We had the same issue and below is my scenario
1. My Servers running on Windows 2012 R2 Standard
2. WFCS with SQL AG cluster with no shared disks
3. Node 1 is active and Node 2 is passive
4. All my cluster core resources and Cluster group is on Node 1 which is active and running fine with no issues from past several days
5. Both my nodes are running on outdated VMware tools.
6. As my Node 2 is passive, we have updated the VMware tools on Node 2.
7. Post successful completion of Vmware tools on Node 2, Cluster service on Node 1 is down which resulted in fail over of resources to Node 2
Please help me to understand, why updating VMware tools on passive node is impacting the cluster service on the active node and making the fail over. The same never happens if we reboot the passive node.
Any help is much appreciated.
Regards,
Srinivas
The macOS license seems pretty clear that running under ESXi is not permitted (emphasis mine):
§2.B.iii: ... you are granted a limited, non-transferable, non-exclusive license ... to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software ...
Seeing as how in the very same sentence they distinguish between the acts of installing and running, I can interpret this no other way than macOS has to actually be in memory and executing before you start any VM. Not sure how you're going to do that and run ESXi at the same time.
Fresh install of ESX 7 on SuperMicro X11SCA
Two onboard NICs seen out of the box, but I added an I340-T4, that is not seen. It is listed here, so I guess it should be supported:
VMware Compatibility Guide - I/O Device Search
>esxcli software vib list|grep igb
igbn 0.1.1.0-6vmw.700.1.0.15843807 VMW VMwareCertified 2020-04-17
It seems like the onboard nic1 uses this driver as well.
Is this a known bug?
Regards, Lars.
I'm not sure if I'm missing anything, but this happens on both systems I've tested. Both are running Debian testing. One has Workstation Pro 15.5.2 and the other has player. Both system fail to install esxi 7 because the network device is not detected. I have 6.7 working on the Pro system. 6.7 will install on the Player system. I've searched and can't find any special steps that I could be missing. Everything should be updated to the latest patches including host OS.
What types of virtual NIC are you using for the ESXi VM?
ESXi 7 no longer supports vmklinux drivers, so just because 6.7 worked does not mean a 7.0 VM will with the same virtual hardware.
Have you tried the various virtual NIC types to see if others work?
Are there other types of virtual network devices? I'll admit I've never added a new network device type before and I don't see any options to change it. I see add a new network device which doesn't provide any options. I also don't see any options in the network device to change the driver type. I don't see where I can even add a new device type. Is there an article that covers this?
Not in the UI in Workstation, see this article for Fusion which should also apply to Workstation: Re: How do I specify Network Adapter to be vmxnet3 in Fusion?
Thank you. I updated the following
ethernet2.virtualDev = "e1000" to ethernet2.virtualDev = "vmxnet3"
And now the installer is working on Player.
Would you please say what does your mean from
1:1 to 3:1
3:1 to 5:1
would you give an example ? how can calculate this ?