These are all supported (ie. have a "native" driver): VMware Compatibility Guide - I/O Device Search
↧
Re: ESXi 7.0 HomeLab Network Card
↧
Re: ESXi hosts CPU over commitment resoultions
Those are definitely recommendations to follow - over-sized VMs just waste resources.
↧
↧
Re: Esxi 6.7u3 on Clevo W110ER.
Dude, it's a laptop. ESXi is designed for enterprise hardware, not this stuff. Get different hardware for crying out loud.
↧
Re: Esxi 6.7u3 on Clevo W110ER.
I would be very very surprised if you could get ESXi to install on a Laptop. the Realtek network card is a consumer level product and as such NOT supported by VMmware. it is highly unlikley there would be a VIB for manual installation.
ESXi is NOT Linux, so standard Linux drivers will not work.
↧
Re: Esxi 6.7u3 on Clevo W110ER.
i got 5.5 running fine, network, sata and gpu.
↧
↧
Re: Esxi 6.7u3 on Clevo W110ER.
5.5 ≠ 6.7 and just because it managed to work on a now-ancient version doesn't mean it'll work today.
↧
Re: Esxi 6.7u3 on Clevo W110ER.
really? i don't know it was a laptop! thank you!
↧
Re: Esxi 6.7u3 on Clevo W110ER.
again thank you for stating the obvious! 5.5 was changed for 6.0 and up, but they still use the same drivers. all i have to do is downgrade the network and sata drivers of 6.7 to 5.5, why is that so hard?
↧
ESXi 6.7 How to check enabled SSL/TLS protocols?
I'm trying to check the enabled SSL/TLS protocols on our ESXi 6.7 hosts.
I'm aware of the TLS Configurator utillity, but that only allows you to query the protocols on vCenter rather than the individual ESXi hosts.
I found an advanced setting called "UserVars.ESXiVPsDisabledProtocols" but I can't find an explanation of what this. Is this what I want?
Or is there another/better way to check this?
↧
↧
Intel 82574L with esxi 7.0
Looking to get this for my desktop:
https://www.amazon.com/10Gtek-Gigabit-Desktop-Network-EXPI9301CT/dp/B01M28WJ00
Appears to be supported in esxi7.0:
VMware Compatibility Guide - I/O Device Search
but just because the driver exists on the HCL doesn't necessarily mean that it will be included in the esxi GA bits, correct?
Not interested in building a customer ISO.
Just don't know if there are any caveats.
↧
Re: Intel 82574L with esxi 7.0
but just because the driver exists on the HCL doesn't necessarily mean that it will be included in the esxi GA bits, correct?
Correct. Also, keep in mind that because 7.0 is so new, some entries on the HCL are not fully accurate. You should take that into consideration before buying, and if possible wait for a while.
↧
Error: Connection timed out
I am attempting to create a datastore on a USB Drive (Lab environment(, however is recieve a time out error at the last step of the process. Is there work around for this?
mkfstools -C vmfs6 -S USBDisk-ISO-Datastore /dev/disks/mpx.vmhba33:C0:T0:L0:1
create fs deviceName:'/dev/disks/mpx.vmhba33:C0:T0:L0:1', fsShortName:'vmfs6', fsName:'USBDisk-ISO-Datastore'
deviceFullPath:/dev/disks/mpx.vmhba33:C0:T0:L0:1 deviceFile:mpx.vmhba33:C0:T0:L0:1
ATS on device /dev/disks/mpx.vmhba33:C0:T0:L0:1: not supported
.
Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Creating vmfs6 file system on "mpx.vmhba33:C0:T0:L0:1" with blockSize 1048576, unmapGranularity 1048576, unmapPriority default and volume label "USBDisk-ISO-Datastore".
Failed to create VMFS on device mpx.vmhba33:C0:T0:L0:1
Usage: vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/vml... or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/naa... or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: Connection timed out
[root@localhost:/var/log]
thank you in advance.
↧
ESXi670-202004001.zip - [StatelessError] - The transaction is not supported: VIB VMware_bootbank_esx-base_6.7.0-3.94.15820472 cannot be live installed
Hi!
I am trying to install the patch ESXi670-202004001.zip. Current version:
esxcli system version get
Product: VMware ESXi
Version: 6.7.0
Build: Releasebuild-15160138
Update: 3
Patch: 89
esxcli software vib update -d "/vmfs/volumes/DS-SHARED-01/01-ESXi-Patches/ESXi670-202004001.zip"
[StatelessError]
The transaction is not supported: VIB VMware_bootbank_esx-base_6.7.0-3.94.15820472 cannot be live installed. VIB VMware_bootbank_vsan_6.7.0-3.94.15736744 cannot be live installed. VIB VMware_bootbank_esx-update_6.7.0-3.94.15820472 cannot be live installed. VIB VMware_bootbank_esx-base_6.7.0-3.89.15160138 cannot be removed live. VIB VMware_bootbank_vsan_6.7.0-3.89.14840357 cannot be removed live. VIB VMware_bootbank_esx-update_6.7.0-3.89.15160138 cannot be removed live.
Please refer to the log file for more details.
Yes, the host is in maintenance mode. I rebooted it as well like all people say. And put it out and back in maintenance mode. No change. ESXi ist installed on a 8 GB Fibre Channel volume. The file is fine, checked MD5. Path is good.
Not sure about the size required. Does not seem to be much free space on certain mounts. However, the main one has 3.9 GB free. When I installed ESXi, there was as well some datastore created, which I have deleted. The patch is in a remote datastore (via FC). If I do copy it to a local directory, same issue.
Filesystem Size Used Available Use% Mounted on
VMFS-6 3.6T 3.4T 206.3G 94% /vmfs/volumes/SHARED
vfat 4.0G 51.1M 3.9G 1% /vmfs/volumes/5c83e940-194e4730-deac-0025b5aa0000
vfat 249.7M 149.1M 100.7M 60% /vmfs/volumes/d9ed827c-8e09d1db-579e-5a41a1f021c7
vfat 249.7M 149.1M 100.7M 60% /vmfs/volumes/418f6471-ef7fdaa3-c3fd-eededdb4a122
vfat 285.8M 195.8M 90.1M 68% /vmfs/volumes/5c83e92d-351bd16e-9f9a-0025b5aa0000
After that my host is "not responding" in vCenter. It is not a network issue (this is based on the failed update?). Not sure why this happend.
I always update the hosts that way. Have done all the patches in the past like that. This time, i am getting this error. The error tells to check the log. Which log - why does it not mention the file to check right away? Checked esxupdate.log. I have attached the file.
Any ideas how to get this fixed?
Thanks!
Best regards,
Robert
↧
↧
Re: ESXi regular maintenance
> Especially procedures about disk consolidation.
Disk consolidation are only necessary if you allow your automatic backups to run out of control.
If you monitor your automatic backup tool regularly and fix issues when they appear no regular consolidation actions are necessary.
↧
Re: ESXi regular maintenance
Check all your VMs to make sure they are not left with snapshots for any longer than is necessary (snapshots are usually only needed during backup or patching/upgrade operations)
↧
Re: public/private key authentication to ESXi
looks like the problem was related to the user name
I am not prompted for the password if I supply root user name before the host name
↧
Re: Unable to create Filesystem, please see VMkernel log for more details: Failed to create VMFS on device naa.6589cfc00000022d3b9872e459f4b72c:4
Hello Cemoka,
I know it has been a while since you posted this and maybe you already moved on.
Since I was running into the same problems as you are and this search is the only thread coming up I figured I'd leave a reply.
Like my fellow vExpert daphnissov suggested is that this problem is not in VMware ESXi. Apparently (don't ask me what exactly) in 6.7 your run the latest version of VMFS6, which has had some improvements and it doesn't like the way FreeNAS is dealing with block size and the spoofing of it rendering some weird error as if there is already data on the iSCSI LUN.
As you noticed, you can create VMFS5, but VMFS6 will fail.
Simply put, FreeNAS needs to be brought up to speed to handle the latest VMFS6 requests nicely.
Now, I don't know if you are new to FreeNAS (I am), so I made a mistake of using FILE based extents for the iSCSI sharing in FreeNAS, which means it is dumped either directly on the storage pool or inside a dataset depending on what you choose.
In this File based iSCSI extent, VMFS6 fails to match the logical block size given to the extent with the physical block size of the drive (correct me if I'm wrong here anyone).
You can fix this in FreeNAS by selecting the option "
Now, make sure the logical block size is set to 512 as I've found this the only working logical block size.
Adding the VMFS6 datastore works now but, here comes the catch, the datastore errors with UNMAP not supported by device.
This got me thinking again, because FreeNAS uses VAAI and should support UNMAP. This is where I found out I was still a newbie at FreeNAS!
You are NOT supposed to be using iSCSI with file based extents on pools or datasets for VMware!
To do this the right way, create a ZVOL, which is specifically created to support VAAI and works perfectly as a DEVICE iSCSI extent, perfect for a VMware ESXi datastore.
For more info see: https://www.ixsystems.com/documentation/freenas/11.2/storage.html#adding-zvols
I created a ZVOL with 16k block size (advanced settings), added it to a device based extent with logical block size 512 and tadaa!
All nice and dandy with UNMAP support!
Hope it helps.
↧
↧
Re: public/private key authentication to ESXi
So your original issue resolved right? however, while using root not prompted for password. It may you have to look your automation script if something define or is there any changes?
↧
Re: public/private key authentication to ESXi
yes, the original issue was resolved by supplying the user name.
↧
Re: public/private key authentication to ESXi
while we are on the same topic, is there an official VMWare KB on public / private key authentication to vCenter?
The only guide I found so far is this https://www.virten.net/2015/10/vcsa6-bash-and-ssh-key-authentication/
↧