Saddly the "performance" is only inproved with the VMware tools.
What I find usefull some times is to run a silent install or using command line. (this may help) Silent Install of VMware Tools From The Command Line | BRIAN GRAF
↧
Re: VMware Remote Console Mouse speed and accuracy
↧
Simple SH script started with cron job, will not persist and settings/files are deleted after reboot.
Hello,
I created a simple little script to do a rescan of the storage adapters on the server, 60 seconds after boot.
I created a file called hbascan.sh and in that file i have this line "sleep 60s;esxcli storage core adapter rescan --all"
I placed this script in the /bin folder on the ESXi host
I edited the "/var/spool/cron/crontabs/root" in here i added "@reboot sh /bin/hbascan.sh" at the end/bottom of the file.
I then killed the Cron job after finding the correct ID
I then edited the "/etc/rc.local/" and added at the end of the file 3 rows with text.
/bin/kill $(cat /var/run/crond.pid)
/bin/echo '@reboot sh /bin/hbascan.sh' >> /var/spool/cron/crontabs/root
/bin/busybox crond
I saved the file and ran the command "sh /sbin/auto-backup.sh"
Problem is that when i reboot the server everything is gone, the script is gone and the changes to root and rc.local is also gone.
I did the edit of the files with winscp as i am not really confident in "vi"
I am not entirely sure what's wrong, it could be syntax or maybe file rights?
I followed a guide for this online and it's almost identical to the guide, only i did not provide any path to logs.
Any help would be greatly appreciated.
/Hyper-lost
↧
↧
Re: Black screen of vm in esxi
I want to try it, no problem but estimated time remaining is 2 days for this action (transfer rate is 281 kb/s)
I don't understand why it works perfectly in workstation and after I register it on esxi it won't boot windows at all (remainind that black screen with underline char in right left part of the screen).
I have no errors only it stuck on that black screen (before windows loader)
↧
Cannot log directly into an esxi host using a newly created user account
I have an esxi host running version 6.0. I logged directly into the host as root through the web client, added a new local user from the Security & Users tab, and assigned that user the Read-Only role from the permissions section. When I attempt to log in to the web client as the new user, it spins for a few seconds and says that the connection timed out. If I try through the desktop client, it hangs on loading inventory for a few minutes and gives a similar timeout message. If I log in as root from the exact same computer, it works. Am I missing something?
↧
Driver needed for ATTO ExpressSAS H644
I am trying to find the VMWare driver for ESXi 6.7 to support an ATTO ExpressSAS H644 SAS controller.
ATTO directs me to the VMWare compatible site where I find the following driver recommended:
If you select the link it just takes you to the Download VSphere where I can select Drivers and tools
but I cannot find the above listed driver. I have performed a Google search for this but only get a
hit on and ISO for ESXi 6.0.
Can anyone tell me where I can find the vib for the above driver?
↧
↧
ESXi installation
Hello,
I'm a beginner in VMware products and I'm using a course to try and install a lab on ESXi. I'm trying to export an image and I keep getting this Error:
Export-EsxImageProfile : Error retrieving file for VIB
'VMW_bootbank_net-libfcoe-92_1.0.24.9.4-8vmw.670.0.0.8169922': ('https://hostupd
ate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/net-libfcoe-92/VMW_boo
tbank_net-libfcoe-92_1.0.24.9.4-8vmw.670.0.0.8169922.vib', '', 'file not
found').
At line:1 char:1
+ Export-EsxImageProfile -ImageProfile "ESXi-6.7.0-Omer"-NoSignatureChe ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Export-EsxImageProfile], SoapE
xception
+ FullyQualifiedErrorId : System.Web.Services.Protocols.SoapException,VMwar
e.ImageBuilder.Commands.ExportProfile
Help will be much appreciated.
↧
Re: ESXi installation
↧
Re: ESXi installation
Thank you very much!
Sorry to bother you with this when the answer was here all along.
↧
Re: Driver needed for ATTO ExpressSAS H644
Hi,
It should be found at this address:
VMware Compatibility Guide - I/O Device Search
Which then refers to this address:
VMware vSphere 5: Private Cloud Computing, Server and Data Center Virtualization
But that hijacks to version 5.5
If you download the Notes, it says that it is compatible only for Esxi 5.5 and 6.0
Even if you initially selected Esxi 6.7
Release notes for ATTO esas2hba driver version 1.70
1. Driver name: esas4hba, Driver version: 1.70
2. Compatible ESXVersions: 5.5, 6.0
3. Dependencies: None
4. Bugs Fixed:
- Added support for ESXi 5.5 and 6.0.
5. New hardware supported: None
6. Known Issues and Workarounds: None
7. Additional configuration options supported by the driver: None
Seems like a problem with the download, I immediately report it to vmware. (LucD) scott28ttLucD
ARomeo
↧
↧
Re: Driver needed for ATTO ExpressSAS H644
Hi,
as I said in the previous answer, I wrote to ask for confirmation and it seems that something is wrong. A verification will be opened. It will take some time. However, I suggest you try to download the version that I have indicated before, because there could be an error only in the file of the Notes that have not also included Esxi 6.7
If so, the driver should work.
ARomeo
↧
Re: virtual nic issue
we just got a call from VMware and below is the article they found on our logs
And as per VMware, the only way this will occur if either the vmnic was removed either from the Guest VM or inside the vsphere > edit the vm settings
Jeff
↧
ESXi 6.5 - hot plugging a USB device works on one VM but fails on another
Hi all,
I have some USB devices that are connected to my ESXi 6.5.0 host. At times, I need to hot plug them into VMs. When I edit one VM, add a USB device, assign the physical device and save, all works well and the device is plugged into the VM. When I do the same with the second VM, saving fails, saying "The attempted operation cannot be performed in the current state (Powered on)."
Both VMs run flavors of Linux x64 and both have tools installed and running (if that matters).
I checked the configs and "devices.hotplug" is not configured for either. I even tried setting "devices.hotplug" to TRUE but that didn't make a difference.
What could be the reason for one machine accepting USB hotplug and the other rejecting it?
Thanks in advance for any insight!
↧
Re: ESXi 6.5 - hot plugging a USB device works on one VM but fails on another
did you check the vm hardware version? USB hot plug is only supported from HW 13 and up.
↧
↧
Re: ESXi 6.5 - hot plugging a USB device works on one VM but fails on another
Thanks for your response.
I have virtualHW.version = "8" in both vmx files, if that's what you were referring to?
↧
Intel IRIS766 passthru - ESXi6.5
Hi All,
I can't seem to get the pass through for a intel iris 655 to work on ESXi 6.5, this is on an Intel NUC.
Interestingly the PCI device is showing as "Intel(R) VGA compatible controller" rather than Intel IRIS 655. On a Windows 10 installation it does detect Intel IRIS 655 but give the exclamation mark saying the device isn't working.
I've also tried an Ubuntu install that just doesn't seem to start up.
I've set the SVGA setting to FALSE and the console is no longer displayed.
Any pointers what to try next?
↧
Re: ESXi 6.5 - hot plugging a USB device works on one VM but fails on another
↧
Re: ESXi 6.5 - hot plugging a USB device works on one VM but fails on another
yes. As scott mentioned.
right mouse your VM in vcenter compatibility, schedule vm compatibility upgrade.
choose 13, the latest since you are running on 6.5.
reboot the VM, the version will be changed to 13. Than your USB should work.
↧
↧
Re: Kickstart File Not Working
Hi,
I'm having the same issue.
I have a relatively simple kickstart file that works always with 6.5
and only "sometimes" with 6.7.
When it doesn't work, it hasn't executed anything at the %firstboot section.
kickstart.log file is empty in either case (success or not)
weird think is I have 2 types of install, with 10Gbit nics and with 1Gbit nics. The 10Gbit nics version works nearly always and the 1Gbit nics version works nearly never.
But in both cases it sometime works and sometimes doesn't.
I already increased the sleep value but that doesn't change anything.
↧
automated install with kickstart file and vmware 6.7 doesn't work, but sometimes it does
I have a relatively simple kickstart file that works always with 6.5
and only "sometimes" with 6.7.
When it doesn't work, it hasn't executed anything after the %firstboot section.
kickstart.log file is empty in either case (success or not)
weird thing is I have 2 types of install, with 10Gbit nics and with 1Gbit nics. The 10Gbit nics version works nearly always and the 1Gbit nics version works nearly never.
But in both cases it sometimes works and sometimes not.
I already increased the sleep value but that doesn't change anything.
it's the typical kickstart file
#THE BELOW PART ALWAYS WORKS
#=============================
vmaccepteula
clearpart --firstdisk --overwritevmfs
install --firstdisk --overwritevmfs
rootpw blablabla
network --bootproto=static ---- .... with all optoins
reboot
#THE BELOW PART "SOMETIMES" WORKS
#==================================
%firstboot --interpreter=busybox
sleep 30
#do esxcli stuff...
if only I could find some logs to search through.
↧
Trying to update from HPE ESXi 6.5 U2 to U3 - cannot be live installed error
I’m trying to update to U3 of ESXi 6.5, and am getting the following error:
[root@Gen8:~] esxcli software vib install -d "/vmfs/volumes/SSD/images/VMware-ESXi-6.5.0-Update3-14990892-HPE-preGen9-650.U3.9.6.10.1-Dec2019-depot.zip"
[StatelessError]
The transaction is not supported: VIB VMW_bootbank_vmkusb_0.1-1vmw.650.3.96.13932383 cannot be live installed. VIB HPE_bootbank_oem-build_650.U3.9.6.10-4240417 cannot be live installed. VIB VMW_bootbank_bnxtnet_20.6.101.7-23vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_ixgben_1.7.1.15-1vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_smartpqi_1.0.1.553-28vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_igbn_0.1.1.0-4vmw.650.3.96.13932383 cannot be live installed. VIB VMware_bootbank_esx-base_6.5.0-3.108.14990892 cannot be live installed. VIB VMW_bootbank_lsi-msgpt35_09.00.00.00-5vmw.650.3.96.13932383 cannot be live installed. VIB VMware_bootbank_cpu-microcode_6.5.0-3.108.14990892 cannot be live installed. VIB VMW_bootbank_nvme_1.2.2.28-1vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_ne1000_0.8.3-8vmw.650.2.75.10884925 cannot be live installed. VIB VMW_bootbank_misc-drivers_6.5.0-3.96.13932383 cannot be live installed. VIB VMW_bootbank_ntg3_4.1.3.2-1vmw.650.2.75.10884925 cannot be live installed. VIB VMW_bootbank_nenic_1.0.29.0-1vmw.650.3.96.13932383 cannot be live installed. VIB VMware_bootbank_lsu-lsi-drivers-plugin_1.0.0-1vmw.650.2.79.11925212 cannot be live installed. VIB VMware_bootbank_esx-tboot_6.5.0-3.108.14990892 cannot be live installed. VIB VMware_bootbank_lsu-lsi-lsi-msgpt3-plugin_1.0.0-8vmw.650.2.79.11925212 cannot be live installed. VIB VMware_bootbank_vsan_6.5.0-3.108.14833668 cannot be live installed. VIB VMware_bootbank_lsu-hp-hpsa-plugin_2.0.0-16vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_i40en_1.8.1.9-2vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_lsi-mr3_7.708.07.00-3vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_lsi-msgpt3_17.00.02.00-1vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_vmw-ahci_1.1.6-1vmw.650.3.96.13932383 cannot be live installed. VIB VMW_bootbank_nenic_1.0.0.2-1vmw.650.0.0.4564106 cannot be removed live. VIB VMware_bootbank_esx-base_6.5.0-2.57.9298722 cannot be removed live. VIB VMW_bootbank_ntg3_4.1.3.0-1vmw.650.1.36.7388607 cannot be removed live. VIB VMW_bootbank_lsi-msgpt3_16.00.01.00-1vmw.650.2.50.8294253 cannot be removed live. VIB VMware_bootbank_esx-tboot_6.5.0-2.57.9298722 cannot be removed live. VIB VMW_bootbank_bnxtnet_20.6.101.7-11vmw.650.2.50.8294253 cannot be removed live. VIB VMW_bootbank_i40en_1.3.1-19vmw.650.2.50.8294253 cannot be removed live. VIB VMW_bootbank_lsi-mr3_7.702.13.00-3vmw.650.2.50.8294253 cannot be removed live. VIB VMW_bootbank_vmw-ahci_1.1.1-1vmw.650.2.50.8294253 cannot be removed live. VIB VMware_bootbank_cpu-microcode_6.5.0-2.57.9298722 cannot be removed live. VIB VMW_bootbank_igbn_0.1.0.0-15vmw.650.1.36.7388607 cannot be removed live. VIB VMware_bootbank_vsan_6.5.0-2.57.9152287 cannot be removed live. VIB VMW_bootbank_ne1000_0.8.3-7vmw.650.2.50.8294253 cannot be removed live. VIB HPE_bootbank_hpe-build_650.U2.9.6.8-4240417 cannot be removed live. VIB VMW_bootbank_nvme_1.2.1.34-1vmw.650.2.50.8294253 cannot be removed live. VIB VMW_bootbank_misc-drivers_6.5.0-2.50.8294253 cannot be removed live. VIB VMW_bootbank_smartpqi_1.0.1.553-10vmw.650.2.50.8294253 cannot be removed live. VIB VMW_bootbank_lsi-msgpt35_03.00.01.00-9vmw.650.2.50.8294253 cannot be removed live. VIB VMW_bootbank_ixgben_1.4.1-12vmw.650.2.50.8294253 cannot be removed live.
The server is in maintenance mode.
ESXi is installed on a USB stick (8gb).
From my searching on this problem, the issue may be that my /bootbank or /altbootbank are corrupt.
Is there a painless way to fix this?
↧