Hi there,
We switched to the internal SD Card slot. No more latency spikes and seems to do the job - the dual MicroSD seemed to be a good idea (and it probably is) but the dependency on the USB slot seemed to remove the advantage you were meant to be gaining.
I haven’t searched extensively but a server will external facing SD card slots that are mirrored seems to be a great idea but not something HPE does.
Kind regards.
Thank you for your assessment, actullay our primary vcenter and hosts in addtition to being in different subnets also physically are in different countries becasue we have many hosts accross the europe and USA and Middle East we didn't want to dedicate a vcenter for every country. our primary vCenter is in germany and those problematic hosts are in Iran (Middle East) where it has lower internet quality and network against Europe, and as you mentioned that the most possible cause is latency in network ends, it make sense to me but my Boss says if this is the problem, why our other hosts in Iran in same subnet and same datancenter which are connected to Europe's vCenter, don't have this issue? we have 8 hosts in Iran, which only one of them has this issue and the other one sometimes become not respondig but will come back by itself and the other 6 host haven't had this problem ever until now. do you think there must be another underlying cause? or we must setup a dedicated vCenter in Iran for those host?
a
I got this problem when upgrading from 6.7u1 to 6.7u2 and solved it with the manual vib installation as well. Thanks so much for that tip - saved me lots!
[user@host:~] cd /tmp
[user@host:/tmp] wget http://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vib20/tools-light/VMware_locker_tools-light_10.3.5.10430147-12986307.vib
[user@host:/tmp] esxcli software vib install -f -v /tmp/VMware_locker_tools-light_10.3.5.10430147-12986307.vib
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: VMware_locker_tools-light_10.3.5.10430147-12986307
VIBs Removed: VMware_locker_tools-light_10.3.2.9925305-10176879
VIBs Skipped:
I have not bought the server yet, I have either for Lenovo server with m.2 enablement kit technology, or for HPE with HPE dual microSD flash USB stick. According to my research, the first variant is more stable and secure, but the second is cheaper.
I have same problem with NUC8i3BEH. Please advice.
Hi,
I have just started to use ESXi and are having some problems with my VM.
Im going to create an AP on a Debian machine (like this for RPi). But Im not getting it to work with my wifi-dongle TP-Link WN722N.
Is this even possible? I have been trying with few different alternatives but without success.
My wifi-adapter is there when i run "lsusb" on host.
Bus 001 Device 003: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
For my VM I have given access to the USB-device. In the VM the interface is called "wlx6470022dc209" (why not wlan0?).
Installed the firmware with: apt-get install firmware-atheros
Using ESXi 6.7
What information do you need to help me solve this?
Thanks in advance!
WiFi is not supported (and never has been) either as a device directly managed by ESXi or to be passed through to guests. That just isn't what this platform is intended to do.
I faced the same issue while installing esxi 6.7 on hp dl380g10 server ,following steps done and solved my issue. 1.Update the firmware using HP SPP (2019-03 version) 2.Divide the Array into two logical drive (100GB and 3 TB),install ESXi on 100GB 3.HPE custom ISO 6.7 Update1(April Release 2019) 4.Install VMware ESXi without intelligent provision. If anybody faced the issue please try the above steps.
Hi everyone,
Need help.
Scenario: Need to create 1000 virtual machines using HP proliant 360P G8 hardware using ESXi 6.7.
I can provide you required answers according to your question.
Can anyone help me ?
Ah OK.
Another thing that may be relevant is that when there are less than four hosts in a VSAN cluster, data cannot be maintained in compliance with the FTT policy, so care must be taken if any host maintenance is required.
Also I don't believe VSAN will auto-recover from a host failure with less than four hosts. Once a failed host is repaired or replaced, the recover process might be manual.
Hi,
Seeing a bit of a strange one - we have 3PAR LUNs presented to a 6.5 HPE blade cluster via FC and each datastore is presented too all hosts.
They all work fine however on a host reboot some of the datastores are shown as 'Not Consumed' as their operational state in Configure > Storage > Storage Devices. This hasn't had an effect on operations thus far as most of them show up connected after reboot and DRS must only migrate workloads back to that are housed on connected storage..
We only noticed it after bringing hosts back into use and a storage re-scan brings any datastores back instantly.
Has anyone seen 'Not consumed' before or have any pointers?
I will try re-create the behaviour in dev today.
Thank you
Hi all! OP here, a few more notes that I don't think I included above--
pciPassthru0.msiEnabled (where 0 is replaced with whichever device is your GPU) must be set to FALSE in advanced vm settings for the GPU closest to the CPU, otherwise you get constant crashing of the video driver (often with immediate restart and no bluescreen, looks like a slow computer with a screen that occasionally blinks). Beware, because if you change or delete the device and then re-add, you need to redo this.
Very important post on changing the esxi host configuration to prevent random core memory hopping. This was on reddit and made a substantial difference, reducing or eliminating microstutter on all the VM's. I also no longer needed to pin them to specific ccx's. This is in the reddit post titled AMD EPYC on ESXi 6.5-6.7 NUMA issues: Mostly Resolved
Using 6.7 U1 now, can use EFI in VM's instead of BIOS (used to hang if USB passhtru).
Ran into a problem where any VM would slam to 100% disk usage under heavy load (like say a file download) and become almost unresponsive for > 10 minutes after download stopped. Eventually tracked it down to meta corruption on the underlying VMFS. VOMA doesn't like vmfs 6 (didn't last week) so I migrated to a new vmfs, problem solved.
Other notes:
The motherboard appears to retrain its BIOS (and renumber PCI devices ) if you take any out or put any in, potentially breaking more vm's until you re-activate for passthru. You also need to reset lots of bios settings.
Very interestingly, I discovered my system overheating from a dying Enermax Liqtech TR4 AIO. This caused really "interesting" features like the system abruptly (failing to POST) after changing memory settings, even though it had been working fine a minute before. Even worse, if it DID memory training when hot, it would set to super low speeds. This sounds easy, but with not way to check CPU temps outside of BIOS, it was slightly less straightforward (anyone know another way to check CPU temp under esxi with a threadripper? or any of the vm's?)
You can try Virtualization Calculator to estimate your compute requirements.
Same problem.
2x E5-2603 v4
One thing to watch out for if you use Nimble Storage. If you attempt to install Nimble Connection Manager (NCM) for VMWare on an HPE server that boots from an 8GB USB drive, it will lose connection to storage. This is a known bug in NCM that should be fixed in version 6.1 but will not be released for months
Update command:
# esxcli software profile update -p ESXi-6.7.0-20190402001-standard -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
[OSError]
[Errno 28] No space left on device
Please refer to the log file for more details.
Swap config:
All swap is on, datastore use datastore1 and more than 100G space.
Please see the /var/log/esxupdata.log below:
2019-04-16T00:41:48Z esxupdate: 2099451: Ramdisk: INFO: Unmounting manual tardisk /tardisks.noauto/esxupdt-2099451^@
2019-04-16T00:41:48Z esxupdate: 2099451: Ramdisk: INFO: Unmounting manual tardisk /tardisks.noauto/weaselin-2099451^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: Traceback (most recent call last):^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/usr/lib/vmware/esxcli-software", line 470, in <module>^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: main()^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/usr/lib/vmware/esxcli-software", line 461, in main^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: ret = CMDTABLE[command](options)^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/usr/lib/vmware/esxcli-software", line 213, in ProfileUpdateCmd^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: nohwwarning=opts.nohwwarning)^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esx
image/Transaction.py", line 375, in UpdateProfileFromDepot^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/tmp/esx-update-2099451/usr/lib/vmware/weasel/util/upgrade_precheck.py", line 2161, in cliUpgradeAction^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/tmp/esx-update-2099451/usr/lib/vmware/weasel/util/upgrade_precheck.py", line 997, in _parseVmwareVersion^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 514,
in getoutput^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 495,
in getstatusoutput^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 316,
in check_output^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 383,
in run^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 676,
in __init__^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: File "/build/mts/release/bora-10764712/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/subprocess.py", line 1228
, in _execute_child^@
2019-04-16T00:41:48Z esxupdate: 2099451: root: ERROR: OSError: [Errno 28] No space left on device
My GTX 1660Ti doesn't like reboot on 6.7u1 either.
It works like a charm on 6.5u2.
Tried all reset methods but no lucky.
See my post at Deep investigation on GPU Passthrough not working anymore after upgraded from 6.5 to 6.7, what's different on PCIe resetting?
Hi All,
We also faced same issue (hanging VMs, slow startup) and were able to fix issue with this:
Windows 10 1809 VDI may become "Agent Unreachable" state if the High Precision Event Timer (HPET) is disabled. (67175)