Hi All,
I'm working on brand new ESXi 7.0.0 deployment and have run into an issue when deploying vCenter 7.
When browsing to the vCenter UI I receive a "no healthy upstream" error.
I can access vCenter Server Management without issue.
I've done some googling and have been pointed towards certificate issues however my Leaf and Root certs are showing as valid.
All of the services which are set to Automatic start are running without any errors or warnings.
Is there a documented fix for this issue?
Hi,
I imported a workflow from vRO 7.5 to my new environment vRO 8.1
This workflow writes some files in the following path: /data-vra-scripts/folder (in vro appliance).
According to this VMWare article I need to edit js-io-rights.conf
Rules in the js-io-rights.conf File Permitting Write Access to the vRealize Orchestrator System
However in the path mentioned in the article the file does not exist (/data/vco/var/run/vco/js-io-rights.conf)
However I found it in the following path: /data/vco/usr/lib/vco/app-server/conf/js-io-rights.conf
I try to edit the file from /data/vco/usr/lib/vco/app-server/conf/js-io-rights.conf - but still my workflow fails on creating my file.
I also try to copy js-io-rights.conf to the path mentioned in the article, but the errors still occur.
By the way, in past, in my old environment I edited this file, and eventually it allows me to create and edit files.
Any idea?
Hello,
My VMWare workstation 15 frequently freezes.
According to task manager vmware-vmx process is working but vmware.exe is not responding.
VMWare stops with any VMs.
I found Event viewer shows a warning.
>CnxWin32_FindSocket: ReadFile failed (code 258 timeout 3000)
I cannot see which file caused reading error,
any ideas?
-<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
</System>
</Event>
My Guest VM is currently running extremely slow. It's constantly as CPU Utilization: 100%, Speed: 2.90 GHz and Memory Utilization: ~50%. At the same time, the host CPU is showing Utilization: 15%, Speed: ~1.5 GHz AND Memory Utilization ~48%.
How would I go about allowing the Guest VM to uitilise more of the host CPU? I've tried modifying the Number of processors and Number of cores per processor though I haven't been able to notice any difference.
**** HOST DETAILS:****
CPU
Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Base speed: 2.90 GHz
Sockets: 1
Cores: 6
Logical processors: 12
Virtualisation: Enabled
L1 cache: 384 KB
L2 cache: 1.5 MB
L3 cache: 12.0 MB
Utilisation 12%
Speed 1.65 GHz
Up time 0:05:42:52
Processes 233
Threads 2571
Handles 99367
**** VM DETAILS ****
CPU
Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Base speed: 2.90 GHz
Sockets: 2
Virtual processors: 2
Virtual machine: Yes
L1 cache: N/A
Utilization 100%
Speed 2.90 GHz
Up time 0:00:16:15
Processes 185
Threads 2390
Handles 85077
Hoping someone can help me here. Doing a new deploy on a single ESXi 6.7 host (build 16316930) using VMWare-VCSA-all-6.7.0-15132721. All DNS is setup locally and both ESXi host and VCSA resolve/ping using FQDN and short name. OVF log reports teh following lines...
2020-08-19T14:32:58.270-04:00 verbose OVFTool[10032] [Originator@6876 sub=Default] Initializing new curl session
2020-08-19T14:32:58.274-04:00 warning OVFTool[10032] [Originator@6876 sub=Default] No Proxy Certificate specified.
2020-08-19T14:32:58.274-04:00 verbose OVFTool[10032] [Originator@6876 sub=Default] Parsing URL...
2020-08-19T14:32:58.274-04:00 verbose OVFTool[10032] [Originator@6876 sub=Default] https://10.0.0.41:443/ha-nfc/520242ad-fdf2-7358-0579-f7d0def54b76/vca-1-0.vmdk is redirected to https://10.0.0.41/ha-nfc/520242ad-fdf2-7358-0579-f7d0def54b76/vca-1-0.vmdk
2020-08-19T14:32:58.274-04:00 verbose OVFTool[10032] [Originator@6876 sub=Default] Changing HttpWriterFactory path to https://10.102.0.41/ha-nfc/520242ad-fdf2-7358-0579-f7d0def54b76
2020-08-19T14:32:58.291-04:00 verbose OVFTool[10032] [Originator@6876 sub=Default] Closing image source and targets
2020-08-19T14:32:58.291-04:00 verbose OVFTool[10032] [Originator@6876 sub=Default] Bad return code from POST request: 404
2020-08-19T14:32:58.291-04:00 error OVFTool[10032] [Originator@6876 sub=Default] Error closing image-target
Packet capture shows the installer closing the connection with a RST (reset) after the "Bad return code" event.
Any help here would be appreciated.... I have tried both GUI and CLI install
installer log displays the following...
2020-08-19 18:32:56,418 - vCSACliInstallLogger - INFO - OVF Tool: Opening OVA source: H:\vcsa-cli-installer\win32\..\..\vcsa\VMware-vCenter-Server-Appliance-6.7.0.42000-15132721_OVF10.ova
2020-08-19 18:32:56,446 - vCSACliInstallLogger - INFO - OVF Tool:
The manifest does not validate
2020-08-19 18:32:56,583 - vCSACliInstallLogger - INFO - OVF Tool:
Opening VI target: vi://root@10.0.0.41:443/
2020-08-19 18:32:57,432 - vCSACliInstallLogger - INFO - OVF Tool:
Deploying to VI: vi://root@10.0.0.41:443/
2020-08-19 18:33:03,293 - vCSACliInstallLogger - INFO - OVF Tool: Transfer Failed
2020-08-19 18:33:03,320 - vCSACliInstallLogger - INFO - OVF Tool: Transfer Failed
2020-08-19 18:33:03,346 - vCSACliInstallLogger - INFO - OVF Tool:
Error: Failed to send http data
2020-08-19 18:33:05,471 - vCSACliInstallLogger - INFO - OVF Tool:
Completed with errors
2020-08-19 18:33:05,499 - vCSACliInstallLogger - ERROR - Deployment failed. OVF Tool return error code: 1
Any help would be appreciated.... Thank you in advance.
Hello,
On vRA 8.1 patch 2 we can't delete an empty project :
Anyone have this error ?
Thx for your feedback
Hello,
I'm starting the learning process on the VMWare platform with a home lab setup. ESXI 6.5 is installed on my server and I am able to successfully manage the system via the web interface. However, I'd like to explore some of the options present in the vCenter Server application. However, I'm unable to locate the correct download for this product.
Pressing the "Get vCenter Server" button from the ESXI web interface does not direct to the correct link.
Browsing through the downloads page seems to be the correct location but I do not have permissions to download: https://my.vmware.com/en/group/vmware/downloads/details?downloadGroup=VC65U3K&productId=614&rPId=50173
Message: You either are not entitled or do not have permissions to download this product. Check with your My VMware Super User, Procurement Contact or Administrator. If you recently purchased this product thorugh VMware Store or through a third party, try downloading later.
I'm looking for help in 1 of 2 ways:
1. Describe how to obtain permissions required for downloading the product from the link below
2. If the link below is not the right approach, please redirect me to a download location for the client interface that I install on my desktop PC.
Download Link I tried:
Version of ESXi
ESXi 6.5 A03 (based on ESXi VMKernel Release Build 5310538)
Hi all,
I am planning to move our ESXI 6.5 hosts to new Servers (7.0). Can you please advise me of the best practice?
I had done migration previously which was with the same version, no issues.
Wondering, am I able to backup the ESXI 6.5 config and restore it on the new server (Esxi 7.0)?
I tried it in my dev lab, it didn't work even after changing UUID. I would appreciate your suggestions/comments.
Vcenter version is 6.5
Cheers
Hello,
Could you help me with a creation date of VM?
I need to add to the report date when VM was created. I have found that VM in vROPS has a metric called Configuration|Creation Date but probably it is not human readable.
How can I convert it to a readable date? My license allows me to use a super metric if it can help.
Una consulta
cuando un servidor se apaga por x o y razón y él HA subes esas VMs en otro nodo.
cuando el nodo que se apagado vuelve a estar disponible hay alguna configuración que no sea DRS que devuelva esa vm al host que se apagó?
when a server goes down for anyy reason and the HA move the VMs to another node.
when the node that was shut down becomes available again is there any non-DRS setting that returns that vm to the host that was shut down?
Working on procedure to follow when we have any power outage.
Last power outage, we tried shutting down all VMs, but some vhosts died before others when UPS battery ran out and HA started booting up those hosts on remaining vhosts, which is the last thing we wanted to have happen while trying to shut everything down.
My question is whether putting all vhosts into maintenance mode will prevent that from happening?
I know putting vhosts into maintenance mode only completes once the last running VM is migrated off it, but if, before that, another vhost dies, can HA still power up VMs on the host for which "Enter maintenance mode" has been initiated, but not completed?
Hi all,
I got an issue on accessing Virtual WLC's GUI in my home LAB network and I have been trying to figure out why for a few days.
vWLC is installed on ESXi which is installed on VMware Workstation on Windows 10. vWLC's management interface is assigned an IP 172.16.10.5 (with default getway 172.16.10.1/24) which on VLan 10. I have set these up during vWLC installation process via Console interface.
On ESXi switch, I created a Trunk & assigned VM vWLC into it. The uplink of the switch is attached VMnic2 which is bridged to my physical network 172.16.10.0/24 via a USB to Ethernet adapter. The adapter is set an IP 172.16.10.100/24.
My question is why I'm not able to access vWLC's GUI via its IP 172.16.10.5 from another computer which I directly connect to the USB to Ethernet adapter on the same network???
I will be connecting a physical switch into the USB to Ethernet adapter and a attach the router into it.
At the moment, I just test if vWLC's GUI can be accessed from a computer which I connect directly to the adapter as I have mentioned. Btw, ping from the computer to vWLC fails.
Do you think because vWLC doesn't understand untagged packets sent to the adapter from the PC? as I set the vWLC's management interface on Vlan 10.
I will upload a layout image of virtual switch that I set on ESXi and hope it'll make my explanation clearer.
Any ideas or suggestions would be much appreciated.
Hi
I've just moved from an Intel i7-6700K to an AMD Ryzen Threadripper 3960X and have noticed that the initial startup process is extremely slow (5-10min) once it's started everything works fine and a reboot is as quick as before.
The same slow initialization happens when the VM is turned off or suspended, it takes 5-10min (extremely random) for the VM to get to the "Windows 10"-load screen.
Anyone having the same or similar issues or know a reason for this?
I'm running VMWare Workstation 15.5.1 and have attached the log.
2019-11-29T09:29:56.345+01:00| vmx| I125: vmm64-vcpus: 8
2019-11-29T09:36:35.583+01:00| vmx| I125: KHZEstimate 3792875
Best Regards,
Erik
Hi Team,
Just wanted to confirm on how we can delete disconnected syslog hosts and agents from vRLI UI.
The syslog hosts and agents were reporting properly and if we decommission the source machines then we are left with stale disconnected entries of those machines under syslog hosts and agents tab of vRLI UI. How can we deal with this problem?
Is there a specific period that vRLI will keep these stale entries and will delete them automatically once that period is over? or is there anything we can do at the appliance level to deal with it.
Dear all,
we have 2 serperate vm enviroments, and we try to migrate hosts with vm`s from the old 6.0 enviroment to the new 6.7 enviroment.
this works , i remove a host ( with running vm`s ) from the old 6.0 and add it to the 6.7 enviroment.
when i try to migrate ( vmotion ) in the new enviroment from one host to the other host, vmotion fails at 21%
the only way it works is to shut down the vm and then migrate, this works.
only we would like to keep the vm`s running, is there a option to keep the vm`s running and migrate ( vmotion )
the old host is 6.0 and the new is 6.7 ESXI
thanks for all your reply
best regards
jeff
Hey folks,
I am trying to deploy a new Blueprint using an existing Load Balancer that was created in NSX-T. After dealing with a lot of issues i figured out that vRA was not able to modify the LB as it was created using Policy Mode. After recreating all the objects involved (Logical Router and Load Balancer) using Manager Mode it was able to do the modifications.
Is this a limitation or is there a way of creating objects using Policy Mode and made them modifiable?
By the way i am usign NSX-T 3.0
Hi everyone.
I have my MacBook pro with macOS Catalina (10.15.4) . I have installed VMware Fusion, Professional Version 11.5.5 on it. Now I have installed the Windows 10 Enterprise version as a guest on this Mac. I have installed the VMware tools on the Windows guest through "Virtual Machine --> Install Vmware tools" and the features such as shared Folders are working completely fine there.
However, the shared clipboard functionality is not working and when I click on "Edit" on the vm instance all the copy/paste/delete buttons are greyed out. I can't copy any text from my host Mac to the guest Windows or vice versa.
I tried removing and installing the VMware tools inside the windows couple of times and it didn't help. Even I check the "vmware instance settings --> isolation ---> Enable Copy and Paste" and it has been checked correctly.
Could someone please help me out here? Is it a bug or I am missing any steps?
This issues has been hugely impacted my speed for working with the windows instance.
Thanks
Error message in the web page :
Some appliance components are not functioning properly.
Component health: SEARCH:UP, POLICY:UP, MANAGER:UNKNOWN, UI:UP, NODE_MGMT:UP.
Error code: 101
any idea to fix this ?
Hi guys
We are trying to install the Windows & Linux agent in vRealize Operation Manager, but keep failing. I verified the vCenter credentials and clock time is correct. but also install agent failed.
ref:
vRealize Operation Manager 8.1.1 (16522874) & arc811
agent : Windwos 2019 & windwos 2016 ( disabled UAC and FW )
IdeaS?
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