Absolutely agree with André. On no account should this be done for anything other than a lab or testing.
Re: can I install an ESXi hypervisor under windows as a type 2 hypervisor and manage it with VCenter Server
Re: Host cannot communicate with one or more other nodes in the vSAN enabled cluster
Tom, you really need to spend some time in reading the documentation before starting with this product. This isn't something you just "wing." That said, you have a networking issue. Have you created vmkernel ports explicitly for vSAN and tagged them for this service? This is most likely a basic issue that could be understood when studying this product before attempting to implement it.
Re: VM is not Starting
Go to your proxy VM if you have one and release the VMDK files that correspond to the VM in question or Go to the VM directory and hit this command:- lsof | grep -i <VM-name>
Re: Error: "invalid Server Address is specified" with VMware Horizon Version 5.4.0
I was able to Google and find the 5.3 apk. Website looked a bit sketchy but I was able to install after allowing unknown sources. Until there's a fix this was the only option I could think of for my phone.
https://vmware-inc-horizon.en.aptoide.com/?app_id=50281900&store_name=storeareus
Re: VMware Workstation 15.5.2 update will not install on Ubuntu 19.10
Thank you for the reply. Is there a way to back out of the update, regardless of the version of Ubuntu?
Re: NUMA node confusion
Hi
I was interested in your scenario, so I tried to check on my own LAB and I found out some interesting things that I want to share with you. I hope this could be helpful:
There are 4 different columns in ESXTOP command when you check the memory that we should consider, NHN, NMIG, NRMEM, NLMEM.
- NHN or NUMA Home Node is the NUMA node that your VM has been put by NUMA Scheduler.
- NMIG or the number of migration is related to the number of migration made by the NUMA scheduler because of its nature and also Action Affinity.
- NRMEM or NUMA remote memory is the amount of remote memory accessed by VM
- NLMEM or NUMA local memory is the amount of local memory accessed by VM
The behavior of NUMA Scheduler:
As soon as a VM power-up, the NUMA scheduler will put the VM into a single or multi NUMA node (it depends on VM configuration). but this is not the end of the story, every time that a NUMA node is a better place for that specific VM (because of free memory or CPU metrics), the NUMA scheduler will migrate that VM to that NUMA node. it happens all the time. but the speed of vCPU migration is far more than the speed of memory migration. in this case, you will see the amount of remote memory accessed by that VM, under the NRMEM counter, is much more than the amount of memory in NLMEM. as you said, for example, 80% NRMEM and suddenly it changes to 20%
The behavior of Memory Scheduler:
When memory scheduler tries to access the remote memory (it can happen because of the lack of memory on local node or other reasons) NUMA scheduler will decide to migrate the whole VM to that NUMA node or NOT. so in this case, despite the fact that your VM was fitted into a single NUMA node, you will see some amount of remote memory access and local memory access. for example 20% of remote memory access and 80% of local memory access.
What is Action Affinity feature:
In your virtualization environment, you have 2 different places that data can be accessed by vCPUs, CPU L3 Cache and Memory. because of the different latency time between these two places, VMware always considers CPU L3 Cache as a better place to access data for vCPUs. so when there are two different vCPUs (for example one for VM1 and another for VM2) shared the same data or they are communicating with each other, NUMA scheduler will decide to place them closely, so they both can have access to the same L3 Cache data but the memory data for one of them is in another NUMA node, and this means remote memory access (Despite the fact that your VM is fittable into one NUMA node). this may cause CPU contention but as VMware says, the contention can be handled by NUMA scheduler (you can check KB 2097369).
You can check this with the NMIG counter, but it happens fast so you should put your eyes on the screen!
By Action Affinity, you may see the NHN of most of your VMs is the same, that doesn't mean one of your NUMA nodes is overloaded and another one is all free. it is expected behavior and generally improves performance even if such a concentrated placement causes non-negligible ready time.
If the increased contention is negatively affecting performance, you can turn off that by changing the value of NUMA.LocalityWeightActionAffinity to 0 in your host advanced configuration. Be aware that it means all of your workloads will be affected, so be careful.
Conclusion:
Accessing remote memory is a normal behavior of NUMA scheduler, I attempted to run different scenarios and saw the same behavior. NUMA scheduler will try to fit your VM into the best NUMA node, which means VM migration between NUMA nodes. as I said before, the speed of vCPUs migration is much more than memory, so you see a big amount of remote memory access at the moment.
You can check out my different scenarios screenshots in this link.
Re: PowerCLI - List All View Connected Users and VM HostNames
The limit of 1000 seems to be a resultsize issue with the query. I see that all the time with AD but don't see how to override in VMware.
More info here:
https://www.retouw.nl/powercli/get-hvmachine-only-finds-1000-desktops/
Re: Kickstart unattended install with vendor supplied ISO
nothing will broken. you can use any vendor supplied ISO.
please mark correct or helpful if get the answer.
Re: NSX-T - Tier-0 Gateway - Public
I did do the Active/Standby after reading that the Active/Active deployment has some limitations in features.
I still haven't gotten to far, but the single VLAN certainly makes since in my scenario.
I'm thinking it'll look like such to kind of mimic my current environment:
Tier-0 -> Tier-1 -> VLAN backed Segment where Management/Monitoring and other services reside and then the Overlay off Tier-1 for all the GENEVE networks.
So that kind of looks like NSX-v Perimeter ESG -> Distributed Router -> VLAN/VXLAN and then a bunch of OneArm Load-Balancers.
Now in NSX-T those OneArm Load-Balancers are comprised of a Segment, standalone Tier-1 and LB, I found some good blogs about building the same design out but using NSX-T and I have to say once I got my head around it, it was pretty easy.
For DMZs would you connect those to Tier-0, that's how I do it now with the Perimeter ESG.
Thanks
Re: Host cannot communicate with one or more other nodes in the vSAN enabled cluster
sorry I did not get back so soon the site keeps telling me it is in maintenance mode.
I have a network setup just for VSAN
I ran this on host 1
[root@TGCSESXI-15:~] esxcli vsan cluster get
Cluster Information
Enabled: true
Current Local Time: 2020-03-18T22:34:20Z
Local Node UUID: 5d38d9dd-590c-374e-20f8-001018f421ec
Local Node Type: NORMAL
Local Node State: MASTER
Local Node Health State: HEALTHY
Sub-Cluster Master UUID: 5d38d9dd-590c-374e-20f8-001018f421ec
Sub-Cluster Backup UUID: 5d3bf7da-6354-159a-dbb8-000af7a054c8
Sub-Cluster UUID: 52be451c-96dc-7a62-3e6f-9adf883c5415
Sub-Cluster Membership Entry Revision: 4
Sub-Cluster Member Count: 3
Sub-Cluster Member UUIDs: 5d38d9dd-590c-374e-20f8-001018f421ec, 5d3bf7da-6354-159a-dbb8-000af7a054c8, 5d3e54c3-dad7-0f94-1d59-001018f511a0
Sub-Cluster Member HostNames: TGCSESXI-15.our.network.tgcsnet.com, TGCSESXI-17.our.network.tgcsnet.com, TGCSESXI-18.our.network.tgcsnet.com
Sub-Cluster Membership UUID: 4b74725e-7982-fae5-9e54-001018f421ec
Unicast Mode Enabled: true
Maintenance Mode State: OFF
Config Generation: 4d3e48f2-e56c-4f5f-bb29-c3b16c0be4dd 3 2020-03-18T20:39:00.353
Then on Host 2 which is the host that froze
[root@TGCSESXI-16:~] esxcli vsan cluster get
vSAN Clustering is not enabled on this host
How can I enable vsan on one of my hosts? The other three look ok
Once the Node 2 gets configured I believe the vsan will config everything
Or will I need to run a command to start the process again?
Thank you
Tom
Re: VMware Workstation 15.5.2 update will not install on Ubuntu 19.10
Found this and was able to finish the install, so sharing with the community again.
https://askubuntu.com/questions/1041912/installing-vmware-on-18-04-failed-to-build-vmmon
I ran all of the commands from /etc/vmware-installer/components/vmware-installer/3.0.0
Follow along with the "script" detailed in the replies.
#!/bin/bash
VMWARE_VERSION=workstation-15.5.2
TMP_FOLDER=/tmp/patch-vmware
rm -fdr $TMP_FOLDER
mkdir -p $TMP_FOLDER
cd $TMP_FOLDER
git clone https://github.com/mkubecek/vmware-host-modules.git
cd $TMP_FOLDER/vmware-host-modules
git checkout $VMWARE_VERSION
git fetch
make
sudo make install
----I didn't need these next four lines. I was able to just start VMware Workstation as normal and complete the upgrade!
sudo rm /usr/lib/vmware/lib/libz.so.1/libz.so.1
sudo ln -s /lib/x86_64-linux-gnu/libz.so.1
/usr/lib/vmware/lib/libz.so.1/libz.so.1
sudo /etc/init.d/vmware restart
Re: vRO 8.X - Server.getConfigurationElementCategoryWithPath()
My first advice is to always create abstract wrappers of 1st party calls. So for example you should have your own toolbox.configElements module with a getElementByPath action.
You would then update that action to call a separate action or update its actual code to now support getting elements by tags instead of by calling Server.getConfigurationElementCategoryWithPath.
Moving from vRO 7 to vRO 8 I had to update only the one action and everything worked as before. Here is a basic implementation of findByTags
// action findByTags(names[]) if (!names || names.length === 0) { throw new InternalError('names cannot be empty'); } // ':' character prefix indicates global tag, all vRA 8 tags are global const tags = names.map(function newTag(name) { return { tag: ':' + name }; }); return Server.queryByTags(tags, 'ConfigurationElement');
All I did was update getElementByPath to do
const names = path.split('/'); const elements = findByTags(names);
With the return of tree view for 8.1, and without knowing if it applies only to workflows, this logic may require an update.
Re: VRA 8 - Is there a way to move a virtual machine to a different deployment.
Unfortunately it's not possible at this time with vRA 8.
Re: Prepare VM win 2019 template vRA
If it's not you can just update the logic in the prepare script, or not use the script at all.
Obviously if its not "officially supported" then you may still run into odd issues.
Re: VM desktop got black screen
When you receive the blackscreen, can you hit ctl, alt delete to open the task manager? i receive blackscreen from time to time and i have to manually start the explorer task
Re: Host cannot communicate with one or more other nodes in the vSAN enabled cluster
host 16 is part of same vsan cluster.? If yes, please remove from it and re-add host back to the cluster. Previous my answer was based on your first question.
please mark helpful or correct if issue resolve.
Re: Windows 10 slow login
i quite redirecting appdata as well and i shaved 20 seconds. have by chance tested 1909 with dual monitors? in my environment im seeing 30+ seconds added to my logins when a user has two monitors on 1909
Re: 2x Display increases login time Windows 10 1909
Any luck Graham? i have vmware technical support reviewing logs however so far they have not reported any indications within the agent and connection server logs.
Im experiencing that same exact symptoms. 3d rendering slightly helps with logins but i see a slight lag when users are logged in
WS1 Access Connector Questions
I want to activate WS1 Access Connector (Identity Manager Connector ver19.03) to WS1 Access (SaaS).
However, the activation code for WS1 Access Connector cannot be generated.
Is version 19.03 not supported for WS1 Access (SaaS) version?
I am trying to use an older version because the version supporting Horizon is 19.03
Installing VMware Workspace ONE Access Connector 20.01
Note:The Workspace ONE Access 20.01 connector does not support Virtual Apps (Citrix, Horizon, Horizon Cloud, and ThinApps integrations). To integrate Horizon, Horizon Cloud, or Citrix applications and desktops, use VMware Identity Manager connector (Windows) version 19.03. To integrate ThinApp packaged applications, use VMware Identity Manager connector (Linux) version 2018.8.1.0.
Unable to assign IP to 2016 / 2019 servers using vRA8 Blueprint Deployment
I have the following setup:
1. vRA8
2. vSphere 6.7
I have several windows server 2016 templates. I have customization spec files that can assign an IP and add server to the domain.
I am using this template in a vRA8 Blueprint. The code is as such:
formatVersion: 1
inputs: {}
resources:
Cloud_vSphere_Machine_1:
type: Cloud.vSphere.Machine
properties:
image: W2K16DCE
flavor: Large
customizationSpec: W2K16 Standard
networks:
- network: '${resource.Cloud_vSphere_Network_1.id}'
Cloud_vSphere_Network_1:
type: Cloud.vSphere.Network
properties:
networkType: existing
constraints:
- tag: network:clientname
The machine gets deployed. Gets the right sizing. Connects to the correct port group. Then the customization begins. It reboots and takes 20 minutes and comes back with a 169.254.x.x IP and failed customization (name is changed but not added to domain).
I have created network profiles and assigned the tag network:clientname. I have assigned an IP range that is free and available. I can also deploy a VM from template using the same custom spec file and it works.
I am attaching customization spec log files from one of the VMs.
Any thoughts?