Hi,
Does anyone know as to whether there will be a patch/fix for the Meltdown/Spectre bugs for ESXi 5.1
Only appears to be patches for 5.5 and upwards.
Thanka
↧
Intel Bug (Meltdown/Spectre)
↧
Re: Intel Bug (Meltdown/Spectre)
Hi,
I have not seen any official website for esxi 5.1 patch for the Meltdown/Spectre bugs. I will let know , If i come to know any things about it
Regards,
Randhir
↧
↧
Re: Intel Bug (Meltdown/Spectre)
ESXi 5.1 is End of life. So I dont think patch will be released for 5.1.
If you have extended support for 5.1 , then you may approach VMware support for patches.
↧
Re: ESXI 6.5U1 + Convergent Intel Ethernet X550-T2
Then you either haven't enabled the iSCSI engine in the BIOS, you don't have a license to use that functionality (if applicable), or that card doesn't actually support that function. It usually comes down to one of those three.
↧
Re: Intel CPU bug - VMware fix on the way?
My understanding is that VMware are working on a patch for ESXi 5.5 for CVE-2017-5753
↧
↧
Determine Change Rate for ESXi Logs
Hello, we need to determine the daily change rate on our ESXi Logs. Just trying to figure out how best to achieve this
/var/log/hostd.log
/var/log/auth.log
/var/log/syslog.log
| -rw------- | 1 | root | root | 4.5K | Jan | 4 | 21:26 | auth.log |
| -rwx------ | 1 | root | root | 73.8K | Jan | 4 | 21:25 | hostd-probe.log |
| -rwx------ | 1 | root | root | 56.6K | Jan | 4 | 15:20 | hostd-probe.0.gz |
| -rwx------ | 1 | root | root | 56.5K | Jan | 1 | 2:20 | hostd-probe.1.gz |
| -rwx------ | 1 | root | root | 56.4K | Dec | 28 | 13:20 | hostd-probe.2.gz |
| -rwx------ | 1 | root | root | 56.4K | Dec | 25 | 0:20 | hostd-probe.3.gz |
| -rwx------ | 1 | root | root | 56.6K | Dec | 21 | 11:20 | hostd-probe.4.gz |
| -rwx------ | 1 | root | root | 56.5K | Dec | 17 | 22:15 | hostd-probe.5.gz |
| -rwx------ | 1 | root | root | 56.5K | Dec | 14 | 9:15 | hostd-probe.6.gz |
| -rwx------ | 1 | root | root | 56.4K | Dec | 10 | 20:15 | hostd-probe.7.gz |
| -rw------- | 1 | root | root | 177.9K | Jan | 4 | 21:29 | hostd.log |
| -rwx------ | 1 | root | root | 527.9K | Jan | 4 | 20:19 | hostd.0.gz |
| -rwx------ | 1 | root | root | 510.8K | Dec | 31 | 7:10 | hostd.1.gz |
| -rwx------ | 1 | root | root | 561.4K | Dec | 26 | 20:28 | hostd.2.gz |
| -rwx------ | 1 | root | root | 588.6K | Dec | 22 | 9:54 | hostd.3.gz |
| -rwx------ | 1 | root | root | 539.7K | Dec | 17 | 22:56 | hostd.4.gz |
| -rwx------ | 1 | root | root | 531.4K | Dec | 13 | 14:10 | hostd.5.gz |
| -rwx------ | 1 | root | root | 530.7K | Dec | 9 | 11:08 | hostd.6.gz |
| -rwx------ | 1 | root | root | 541.9K | Dec | 5 | 10:50 | hostd.7.gz |
| -rwx------ | 1 | root | root | 638.0K | Dec | 1 | 9:48 | hostd.8.gz |
| -rwx------ | 1 | root | root | 574.5K | Nov | 28 | 13:44 | hostd.9.gz |
| -rwx------ | 1 | root | root | 350.7K | Jan | 4 | 21:29 | syslog.log |
| -rwx------ | 1 | root | root | 17.8K | Jan | 4 | 20:26 | syslog.0.gz |
| -rwx------ | 1 | root | root | 20.1K | Jan | 4 | 17:41 | syslog.1.gz |
| -rwx------ | 1 | root | root | 19.0K | Jan | 4 | 14:57 | syslog.2.gz |
| -rwx------ | 1 | root | root | 18.8K | Jan | 4 | 11:26 | syslog.3.gz |
| -rwx------ | 1 | root | root | 19.2K | Jan | 4 | 7:51 | syslog.4.gz |
| -rwx------ | 1 | root | root | 19.0K | Jan | 4 | 4:19 | syslog.5.gz |
| -rwx------ | 1 | root | root | 18.9K | Jan | 4 | 0:41 | syslog.6.gz |
| -rwx------ | 1 | root | root | 19.1K | Jan | 3 | 21:02 | syslog.7.gz |
| -rwx------ | 1 | root | root | 913.8K | Jan | 4 | 16:35 | vmauthd.log |
| -rwx------ | 1 | root | root | 60.4K | Nov | 6 | 8:06 | vmauthd.0.gz |
| -rwx------ | 1 | root | root | 63.0K | Sep | 15 | 20:51 | vmauthd.1.gz |
| -rwx------ | 1 | root | root | 49.6K | Aug | 16 | 19:28 | vmauthd.2.gz |
| -rwx------ | 1 | root | root | 48.8K | Aug | 16 | 7:53 | vmauthd.3.gz |
| -rwx------ | 1 | root | root | 49.0K | Aug | 15 | 20:24 | vmauthd.4.gz |
| -rwx------ | 1 | root | root | 49.2K | Aug | 15 | 9:00 | vmauthd.5.gz |
| -rwx------ | 1 | root | root | 0 | Aug | 1 | 17:32 | vmsyslogd-dropped.log |
↧
Re: storagerm logs: Some host is down, need to reset the slot allocation
Ever find out any additional info on this?
↧
Re: Cannot Login to WebAccess but to ESXi console
Cause :- Root account is locked and some time monitoring system will not unlock automatically.
1. Try to login through SSH/WinScp/VI-Client/host UI on host after checked "lock-down mode"
2. If step #1 fail; Login on vCenter >>> Select Host >>> Security Profile >> Restart SSH service
3. Try to login through SSH/WinScp/VI-Client/host UI on host and root password would be working.
Note:- Starting with vSphere 6.x, account locking is supported for access through SSH and through the vSphere Web Services SDK. The Direct Console Interface (DCUI) and the ESXi Shell do not support account lockout.
A maximum failed attempts is allowed before the account is locked (login on host UI - https://hostname/ui>>>System>>>Advanced settings>>>Check "SecurityLockFailures" and "SecurityAccountUnlockTime")
↧
VM is not getting IP form DHCP server
Ip is not getting for Windows 10 VM from DHCP server
↧
↧
Correct VSphere Client for Windows 10?
Hi. I'm trying to install the VSphere Client on my new Windows 10 computer so I can connect to my ESXi server.
vsphereclient.vmware.com/vsphereclient/5/1/1/2/5/0/8/VMware-viclient-all-6.0.0-5112508.exe
I downloaded the above which I believe is the 6.0 client update 3.
When I finish the install on Windows 10 and load up the client as soon as I enter the IP of my ESXi server I'm prompted to download and install additional support files, which I do.
Then, I run the client again and get a message that VM VSphere Client ***4.1*** is preparing the setup files. It ends with a message that says "4.1 - The Product can only be installed on Windows XP SP2 and later."
I may have accidentally attempted to install an earlier version of the client here which has munged things up.
How can I get the 6.1 VSphere client going?
Thank you for any help. - Mike Gallery
↧
Re: Correct VSphere Client for Windows 10?
To what version of ESXi are you attempting to connect?
↧
Re: VM is not getting IP form DHCP server
You're going to have to provide a lot more information than this.
↧
Re: Correct VSphere Client for Windows 10?
I'm trying to connect to ESXi 4.1.0.
I can do it from my Windows 7 workstation using the 4.1 client.
Is that the problem? The newer client can't connect to an older ESXi?
Thank you.
Mike
↧
↧
Re: Correct VSphere Client for Windows 10?
You must be using the 4.1 client to connect to an ESXi 4.1 host. You may also face issues getting such an old client to run on Windows 10 as I know others have reported problems.
↧
Re: Correct VSphere Client for Windows 10?
Thank you.
I'll get everything updated.
I appreciate your help.
Mike Gallery
↧
Dell Customized VMware ESXi 5.1.0 update VMware ESXi 6.5?
I have a Dell PowerEdge R620
Vsphere states that "You are running Dell Customized VMWare ESXi 5.1.0 (VMKernel Release Build 799733)"
However, it also states that my Vmware ESXI is Version:6.0.0 Update 3 (Build 5572656)
I tried to update to the latest VMWare 6.5 version, but I receive errors during the install.
Question 1; How can I be running both a Dell ESXi and a VMWare ESXi?
Question 2: What do I need to do to get the latest 6.5 version installed?
↧
Re: stateless error: lost connectivity backing the boot filesystem
Just an update.
I backed up the config, ensured I had screen shots of particular network settings and the liscence key, just to know which mac address I was to use to get it on the network in order to restore a config. I had the VMWare iso freshly burned and verified to disk. Migrated VM's, maintenance mode, rebooted it. Guess what? It came back fine. It did think some VM's were on it that I migrated away, so I canceld the original reconnect operation, removed it from vcenter and then re-added it. I just had to bind my dv switch uplinks, which was easy. Then I was able to update it to the latest patch level, reboot again and everything is working without an issue.
Not sure what caused it, but it was benign.
↧
↧
Re: Dell Customized VMware ESXi 5.1.0 update VMware ESXi 6.5?
You're currently running ESXi 6.0, but this host was originally installed via a Dell-customized ESXi 5.1 image.
As for the errors you encountered, we need more information about what messages were displayed, how you attempted the upgrade, what commands you used, etc.
↧
Re: Dell Customized VMware ESXi 5.1.0 update VMware ESXi 6.5?
[root@lej07esx:~] esxcli software profile update -d /vmfs/volumes/datastore1/ESXUpdates/ESXi650-201712001.zip -p ESXi-6.5.0-20171204001-standard
[DependencyError]
VIB Emulex_bootbank_scsi-be2iscsi_4.2.324.12-1OEM.500.0.0.472629 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLogic_bootbank_net-qlcnic_5.0.750-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB Emulex_bootbank_scsi-be2iscsi_4.2.324.12-1OEM.500.0.0.472629 requires com.vmware.iscsi_linux-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB Brocade_bootbank_net-bna_3.1.0.1-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB Emulex_bootbank_scsi-be2iscsi_4.2.324.12-1OEM.500.0.0.472629 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLogic_bootbank_scsi-qla4xxx_624.01.43-1OEM.500.0.0.472560 requires com.vmware.iscsi_linux-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_net-qlge_2.0.0.54-1vmw.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLogic_bootbank_net-qlcnic_5.0.750-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_net-qlge_2.0.0.54-1vmw.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLogic_bootbank_scsi-qla4xxx_624.01.43-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB Brocade_bootbank_net-bna_3.1.0.1-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
VIB Brocade_bootbank_scsi-bfa_3.1.0.1-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB QLogic_bootbank_scsi-qla4xxx_624.01.43-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.
VIB Brocade_bootbank_scsi-bfa_3.1.0.1-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
This exact same command and ESXi650-201712001.zip worked perfectly on all my non-Dell-customized Dell PowerEdge R610's
↧
Re: Dell Customized VMware ESXi 5.1.0 update VMware ESXi 6.5?
What is the output of the following command.
esxcli software sources profile list -d /vmfs/volumes/datastore1/ESXUpdates/ESXi650-201712001.zip
↧