does anybody have any clue what is the meaning of "receive throttle" for vmx net 3 nic ?
is it used in order to limit packets handled in each DPC in order to avoid BSOD ?
↧
Re: what is the meaning of "Receive Throttle" setting for vmxnet3 nic ?
↧
Re: Latest Windows 10 update won't install over VMWare Workstation 12
↧
↧
Re: Retrieving AD policy from business group?
To get the AD Policy name from the business group you can do the following against the vCACCAFEBusinessGroup object. I haven't found a way to get the DN value from the business group yet.
//get the vCACCAFEBusinessGroup object(shown under Business Group (Deprecated) in the vRO inventory viewer)
var businessGroup = vCACCAFEEntitesFinder.getBusinessGroup(cafeHost, subTenantId);
//get the custom properties of the business group object
var properties = businessGroup.customProperties;
for each (var prop in properties){
if(prop.name == 'ext.policy.activedirectory.system.id'){ //the custom property name matches the AD Policy property name var adPolicyName = prop.value; System.log('Found AD Policy assigned to BG with name: ' + adPolicyName); }
}
Add in some error handling in case it can't find the policy or if for some strange reason it finds more than one.
↧
Re: what is the meaning of "Receive Throttle" setting for vmxnet3 nic ?
Receive throttle limits the number of packets processed in a single DPC (Deferred Procedure Call). Without the limit vCPU thread can be over-allocated and lead to hang issues.
↧
Re: Error "A fault has occurred causing a virtual CPU to enter the shutdown state..." when run "Browser_In_The_Box.5.2.2-r711.firefox.Archive.exe" in Vmware workstation 15 Pro.
Thanks asajm
I try add monitor.suspend_on_triplefault to .vmx file before i post this.
The result is the same error .
↧
↧
Performance Feedback and Advice
Hello Community!
I am hoping to get some feedback and/or advice to help make some VDI performance related decisions. Below is some information about what our current setup looks like:
- ESXi hosts have - Intel 2 socket 12 cores/socket HT enabled. 2.6GHZ CPU / 512GB RAM
- All Flash Storage SAN using 16Gb storage switches etc...
- Horizon View 7 / vCenter 6.5
- Windows 10 1809/1709 virtual desktops. (running VMware tools/Horizon View desktop agent)
- Linked Clone desktop pools
Currently we are running 2vCPU + 6GB RAM. This is under-provisioned as I see our CPU Load AVG is usually between .5-.6, and RAM is way under-provisioned. We are noticing that with all our security and Office 2016, Google Chrome etc...that our performance is starting to suffer. By this I mean that we are seeing, at the end user, CPU staying at 100% longer when launching browsers/apps (it comes down but not a fast as it used to), higher page file access, and just general "latency." Currently we are running 3:1 vCPU to pCPU consolidation ratio. Our storage metrics show that we in no way suffering (IOPS, Service Time, etc...).
We are recomposing this weekend to 8GB RAM (and reserving 4GB) as we have enough RAM per host to handle this easily. I expect this will help certain workloads, but I doubt it will help handle all the additional security and such that have been added to the environment. I have been able to get Endpoint Security to follow the vendors best practices for scanning and exclusions, but it is still taking a toll. I am currently planning on testing 3 different virtual machine configurations, but I am wondering what others may be running, or if anyone has some additional feedback on settings that I can try to adjust for better overall performance.
Test 1: (Running on 1 host separate cluster/storage LUN for testing)
4 vCPUs (2 socket/2core) + 8GB RAM (4GB reservation)
- This configuration is showing "spikes" of high CPU RDY and CO-STOP. By spikes I mean that when I have ESXTOP refreshing at 2 second intervals, I will see this spike occur for an interval and then "recover" when the next refresh cycles. The CPU Load AVG is usually around .90-1.09. I changed out the LSI scsi adapater to a PVSCSI adapter to see if I could save some CPU cycles. Using this setup it takes my vCPU:pCPU ratio to 6:1 @ 40 VMs per host. I also see pretty bad NUMA numbers (like 8-14 of the 40 VMs will be below 70% of the N%L metric..with some of those down below 20%). I can not go below 40 VMs per host or I will not have enough hardware to support my environment.
Test 2: (going to start next week)
3vCPU (1 socket/3 core) + 8GB RAM (4GB reservation)
- Has anyone run 3vCPU with Win10 1709/1809? Any thoughts on this configuration? It would allow me to go to, at worst I hope, a 5:1 vCPU to pCPU ratio at 40 VMs per host. I am considering using a PVSCSI adapter for this as well just to see if I can save any CPU cycles at all. Thoughts?
Test 3:
4vCPUs (1socket/4 core) + 8GB RAM (4GB reservation)
- I know that cores per socket etc...doesn't make much difference anymore. This will use the 6:1 vCPU to pCPU ratio again as I need at least 40VMs/host. Undecided on the SCSI adapter type. I don't expect this one to show any better results than Test 1 honestly. Thoughts?
Bottom line is that in my simple mind, 2vCPU + 6GB RAM is under-provisioned, and based on ESXTOP reviews, 4vCPU is over-subscribing our CPU resources and impacting NUMA. Customers have reported that 4vCPU does appear more responsive, and Stratusphere shows that CPU queues, logon times, and overall CPU performance on average are better. Again ESXTOP is showing that 4vCPU results in spikes of high RDY and CO-STOP occurring at fairly regular intervals, so I am concerned that this will start to show up at the end user side sooner than later. This is why I am thinking that 3vCPU may provide close the same performance gain as 4vCPU with a slightly lower impact to the back-end resources. Still it is hard to use 3vCPU as my binary mind wants to stick with 1-2-4-8 etc...
Any advice, feedback, or any crazy ideas/thoughts that I can try?
EDIT:
We disabled View Storage Accelerator when we switched over to the flash based SAN. I am thinking about turning it back on to see if it will help reduce the CPU utilization, of the hosts, during customer logon. I don't like the idea of slowing down Refresh/Recompose operations, but the flash SAN should make it more tolerable. Does anyone have any metrics on the amount of CPU utilization is reduced by using VSA? I am not worried about logon times as they are well within our expected baseline, it just looks like the majority of stress is during customer logon...for CPU.
↧
Re: what is the meaning of "Receive Throttle" setting for vmxnet3 nic ?
↧
automating vRealize Operations Multi-node analytics cluster failover
first off i should say I'm new to working with SRM, I'm currently in the process of configuring an SRM recovery plan for a 4 node (master, replicate and two data node) vROPS analytics cluster.
I am currently using the below to automate the changes to the IP config on each of the appliances / nodes
/opt/vmware/share/vami/vami_set_network eth0 STATICV4 xx.xx.xx.xx 255.255.255.240 xx.xx.xx.xx && reboot
Then using the details in https://docs.vmware.com/en/vRealize-Suite/7.0/com.vmware.vrsuite.srm.doc/GUID-F3CC4642-4F89-4249-8C56-D676B1015DED.html
I know i then need to make the following changes on the vm once its started to be recovered on the dr site:
$VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsConfigureRoles.py --action bringSliceOffline --offlineReason "SRM Failover" service vmware-casa stop ##Need to automate changes to $VCOPS_BASE/user/conf/cassandra/cassandra.yaml service vmware-casa start $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsConfigureRoles.py --adminCS xx.xx.xx.xx, xx.xx.xx.xx $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/sliceConfiguration/bin/vcopsConfigureRoles.py --action bringSliceOnline
What i am struggling with is how to pass these commands through to the vm from SRM itself and in particular how best to deal with the cassandara yaml updates.
i am hoping this has been dealt with plenty of times previously and that someone can point me in the right direct.
↧
Re: After Software Updates Via SCCM Some Persistent Desktops Go Agent Unreachable
Hi,
Try to check which updates have been applied on the computers you lose reachability. It happens that some security updates make computers unreachable.
Alessandro Romeo
↧
↧
Re: Error "A fault has occurred causing a virtual CPU to enter the shutdown state..." when run "Browser_In_The_Box.5.2.2-r711.firefox.Archive.exe" in Vmware workstation 15 Pro.
Try to add the following to the virtual machine VMX file
monitor_control.disable_longmode = TRUE
↧
Re: After Software Updates Via SCCM Some Persistent Desktops Go Agent Unreachable
It's happened to a small number of random computers a few months in a row now. It isn't a particular update that is causing the issue.
↧
Re: run shell script in ESXi
Hi. Thank you everyone! Thanks,,,
↧
Re: ESXi GUI not opening while ping and ssh are fine
I'm seeing the below errors in the /var/log/hostd.log. Can someone tell me what do these errors mean?
Below are the errors I got in /var/log/rhttpproxy.log
↧
↧
Re: After Firmware Upgrade, , VMware ESXI 6.7 failed to detect datastore.
We are already working on it - right now we extract the most important VM to an NFS datastore using a sh-script with 62000 lines
Ulli
↧
Various Syslog Questions - vSphere 6.7 & LogInsight
Greetings all! Hoping for some guidance on this? We noticed "gaps" in our LogInsight data from our VCSA appliances and seems it has at-least something to do with which protocol we selected (TLS, TCP, UDP, RELP) in the VAMI setup. Curious on which one (and port) we should be using to send syslog data from VCSA/PSCs to loginsight? I understand, generically, the differences between TCP/TLS/UDP/RELP-- I'm just curious what folks are using when considering it's a fairly large environment (1000+ hosts)
Also, in digging in further, we see there's two different syslog options in vCenter itself. Can someone tell us the difference?
Just curious what the difference here is and if both should be checked/enabled/true?
Thanks in advance!
↧
Re: epyc v3000
It's not oficially supported yet, but there are people on internet reporting it works.
Personal opinion: I believe not to support it is nonsense. EPYC V3000 is a direct competitor of Xeon D Series. Supermicro already released a small server with EPYC 3251, called AS-E301. It looks like much better than SYS-E200, which is supported, by the way.
↧
Re: Unable to create a VSS snapshot of the source volume(s). Error code: 259 (0x00000103).
Hi,
Sorry, I saw an Exchange-related error VSS error in the evet log and assumed that this was related to the problem. I see that the Converter job continued past that point so I guess that the the xchange-related error VSS error is not the root cause.
Does anyone know what Error code: 259 (0x00000103) is \what its cause is?
Thank you.
↧
↧
Re: Various Syslog Questions - vSphere 6.7 & LogInsight
Hi,
When selecting protocols, you could take a look at how a VMware Validated Design is configured:
Decision ID | Design Decision | Design Justification | Design Implication |
SDDC-OPS-LOG-028 | Communicate with the syslog clients, such as ESXi, vCenter Server, NSX for vSphere, using the default syslog UDP protocol. |
|
|
Source: Collecting Logs in vRealize Log Insight
You can of course use TCP or TLS instead.
config.log.outputToSyslog is for sending vpxd.log to your syslog.
↧
Re: Unable to create a VSS snapshot of the source volume(s). Error code: 259 (0x00000103).
Hi,
It's a bit old and the version isn't the same thing, but I think it might be useful.
[SOLVED] VMWare converter failed - Spiceworks
[SOLVED] VSS causes image push to fail - VMware Forum - Spiceworks - Page 2
Alessandro Romeo
↧
vCenter SSO 400 error
Hello all,
I am running vCenter 6.7 and I've been getting the following error when trying to log into my vCenter: [400] An error occurred while sending an authentication request to the vCenter Single Sign-On server - An error occurred when processing the metadata during vCenter Single Sign-On setup - null
I've tried restarting the vCenter appliance and one thing I noticed is the vAPI endpoint service was not starting. Looking at the endpoint.log, I see the following error:
2019-08-13T14:58:22.278-04:00 | INFO | state-manager1 | DefaultStateManager | Invoking sts-builder
2019-08-13T14:58:22.376-04:00 | ERROR | state-manager1 | SoapBindingImpl | SOAP fault
com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Invalid credentials Please see the server log to find more detail regarding exact cause of the failure.
at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178)
at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)
at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:259)
at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289)
at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:161)
at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:114)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:927)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:856)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:477)
at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:179)
at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)
at com.vmware.vapi.endpoint.cis.StsBuilder.buildInitial(StsBuilder.java:54)
at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)
at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)
at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-08-13T14:58:22.376-04:00 | ERROR | state-manager1 | StsBuilder | Failed to acquire token for the solution user.
com.vmware.vim.sso.client.exception.AuthenticationFailedException: Provided credentials are not valid.
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.handleFaultCondition(SecurityTokenServiceImpl.java:996)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:932)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:856)
at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireTokenByCertificate(SecurityTokenServiceImpl.java:477)
at com.vmware.vapi.endpoint.cis.StsBuilder.createToken(StsBuilder.java:179)
at com.vmware.vapi.endpoint.cis.StsBuilder.rebuild(StsBuilder.java:77)
at com.vmware.vapi.endpoint.cis.StsBuilder.buildInitial(StsBuilder.java:54)
at com.vmware.vapi.state.impl.DefaultStateManager.build(DefaultStateManager.java:354)
at com.vmware.vapi.state.impl.DefaultStateManager$1.doInitialConfig(DefaultStateManager.java:168)
at com.vmware.vapi.state.impl.DefaultStateManager$1.run(DefaultStateManager.java:151)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
This line caught my attention: com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: Invalid credentials Please see the server log to find more detail regarding exact cause of the failure.
I am not sure what credentials vAPI is attempting to use but I don't see anything in the logs that points to what credentials are being tried.
Would anyone have any insight into this problem? I've been working on this for a few days with no success.
Many thanks
↧