All Posts

Hi Jan, No, since VMmark deploys it's workloads via VMs, there's no way to isolate specific subsystems like CPU or memory.  Typically, you would want to look for a micro-benchmark like (CPU-Z, Geekbench, SPEC CPU, Memtest86, Stream, etc)

I believe the issue is because of that second network on the prime client that I mentioned: 20230710-17:32:17 Info Info: FS Copy Staf.cfg File : Standby0 Returned: RC = 0, STAFResult = Trust level 4 required for the FS service's COPY request Requester has trust level 3 on machineStandby0.hmcdc.local Requesting machine: ssl://172.21.169.225 (ssl://172.21.169.225) Requesting user : none://anonymous   Your prime client has both 172.21.166.225 and 172.21.169.225 IP addresses but Standby's Staf.cfg doesn't have an appropriate trust machine line for 172.21.169.225.  As you can see above, the requestor is listed as 172.21.169.225 so that would seem to be the issue.  You either need to have the workload VMs trust 172.21.169.225 or you need to have the prime client communicate to the workload VMs via 172.21.166.225 since that IP is trusted.

Thanks Joshua for your help reviewing this issue. Reboot all VMs (including your prime client and client0) and try again. Reboot done on all VMs including PrimeClient & Client0 If you are still seeing an issue: Although you said you only have one NIC on your primeclient I see two IP addresses. You may want to review your networking configuration. Additionally, it would help if you went ahead and posted your Standby0's /etc/hosts file and it's /usr/local/staf/bin/STAF.cfg file for us to review. PrimeClient has 2 NICs. One of them on the networks connected to the subnet hosting all the VMmark VMs. Here is the STAF.cfg file(standby0): [root@primeclient ~]# ssh standby0 "cat /usr/local/staf/bin/STAF.cfg" # Turn on tracing of internal errors and deprecated options trace enable tracepoints "error deprecated" # Enable TCP/IP connections interface ssl library STAFTCP option Secure=Yes option Port=6550 interface tcp library STAFTCP option Secure=No option Port=6500 # Set default local trust trust machine local://local level 5 trust machine primeclient level 5 # Add default service loader serviceloader library STAFDSLS trust machine 172.21.169.22 level 5 trust machine 172.21.169.17 level 5 trust machine 172.21.169.11 level 5 trust machine 172.21.169.21 level 5 trust machine 172.21.169.12 level 5 trust machine 172.21.169.26 level 5 trust machine 172.21.169.24 level 5 trust machine 172.21.169.18 level 5 trust machine 172.21.169.19 level 5 trust machine 172.21.169.28 level 5 trust machine 172.21.169.23 level 5 trust machine 172.21.169.16 level 5 trust machine 172.21.169.13 level 5 trust machine 172.21.169.27 level 5 trust machine 172.21.169.15 level 5 trust machine 172.21.169.29 level 5 trust machine 172.21.169.25 level 5 trust machine 172.21.169.20 level 5 trust machine 172.21.169.14 level 5 trust machine 172.21.169.30 level 5 trust machine 172.21.166.* level 5 You could also add the alias "primeclient" to the primeclient's /etc/hosts file (with IP 127.0.0.1) This is done as well.  

I'm not really seeing a lot in the results you uploaded.  Here are a few suggestions to see if we can make some progress. Reboot all VMs (including your prime client and client0) and try again. If you are still seeing an issue: Although you said you only have one NIC on your primeclient I see two IP addresses.  You may want to review your networking configuration.  Additionally, it would help if you went ahead and posted your Standby0's /etc/hosts file and it's /usr/local/staf/bin/STAF.cfg file for us to review. You could also add the alias "primeclient" to the primeclient's /etc/hosts file (with IP 127.0.0.1)

Hi @dmorse  i have a situation problem is that the PrimeClient cannot be found for TestVM (For example VM : Standby , ActionWebA .....etc) under constant test ,finally I modify /etc/hosts Added line primeclient 192.168.1.251 (My test environment does not use DNS Server)  It's Normal after testing

The problem is the same: ProvisioningSource = tile0 and ProvisioningNumTiles = 1 are incompatible (even though you commented out ProvisioningNumTiles, 1 is the default value).  You have already provisioned 1 tile. //   For provisioning Tile 1 - N, Tile0 is used as the source and this should be the keyword 'tile0' : Ex 'ProvisioningSource = tile0' ProvisioningSource = tile0 // int ProvisioningNumTiles : 1 or more tiles : Default 1 : If ProvisioningSource is a template this is automatically set to 1 tile. //  ProvisioningNumTiles = 1   You can either try a benchmark run with 1 tile, or change ProvisioningNumTiles to 2 or higher to create more tiles.  If you do decide to create/provision more tiles, be aware you will need to change these lines from Standby/Servers = Standby0 AuctionWebA/Servers = AuctionWebA0 AuctionWebB/Servers = AuctionWebB0 etc.   to (for example): Standby/Servers = Standby0,Standby1 AuctionWebA/Servers = AuctionWebA0,AuctionWebA1 AuctionWebB/Servers = AuctionWebB0,AuctionWebB1  

Hi @dmorse    two separate clusters, and the SUT cluster have two ESXi hosts with shared storage. I still same issue , may you help me ?  if you need any information , please let me know. vCServerVMmark3Cluster = ClientCluster // String vCServerClientCluster : Default empty : Ex vCServerClientCluster = ClientCluster1 : This is the cluster of hosts running your // Client VMs and is where provisioning will place new client VMs. vCServerClientCluster = Client   // String SVmotion/SVMotionLUNs : Specifies which LUNs to use for Storage VMotions. Must be shared storage. : Default empty SVmotion/SVMotionLUNs = san // String XVmotion/XVMotionLUNs : Specifies which LUNs to use for XVMotions. Must be shared storage. : Default empty XVmotion/XVMotionLUNs = san // String Deploy/DeployLUNs : Specifies which LUNs to use for Deploys. Must be shared storage. : Default empty Deploy/DeployLUNs = san AllowRunOverwrite = true // String runName : Name of provisioning output, stored in ~/VMmark3/provisioning-output/<name> : Default vmmark3-output : Ex VMmark3-BuildOut1 RunName = vmmark3-1tiles // String ProvisioningSource : default empty: This is the mechanism for users to specify which tile is being created. // For provisioning Tile 0 this should be a valid VMmark3 template : Ex: 'ProvisioningSource = vmmark3-template-103016' // For provisioning Tile 1 - N, Tile0 is used as the source and this should be the keyword 'tile0' : Ex 'ProvisioningSource = tile0' // Default empty // ProvisioningSource = vmmark3.1.1-template-031420 ProvisioningSource = tile0   2023-06-21T10:26:03.401 [main] WARN vCSc : Skipping Network tests as TemplateVM is null 2023-06-21T10:26:03.401 [main] INFO MAIN : Provisioning Validation Passed 2023-06-21T10:26:03.403 [main] INFO RMQ : Starting RabbitMQ DeleteQueue 2023-06-21T10:26:03.450 [main] INFO RMQ : Deleted Queue vmmark 2023-06-21T10:26:03.454 [main] INFO vCSc : Cataloging Deployed VMs (1 Tiles) 2023-06-21T10:26:03.545 [main] INFO vCSc : IP:Name :: 192.168.1.11 ElasticDB0 2023-06-21T10:26:03.621 [main] INFO vCSc : IP:Name :: 192.168.1.10 ElasticAppB0 2023-06-21T10:26:03.687 [main] INFO vCSc : IP:Name :: 192.168.1.9 ElasticAppA0 2023-06-21T10:26:03.712 [main] INFO vCSc : IP:Name :: 192.168.1.20 Standby0 2023-06-21T10:26:03.728 [main] INFO vCSc : IP:Name :: 192.168.1.5 DS3DB0 2023-06-21T10:26:03.756 [main] INFO vCSc : IP:Name :: 192.168.1.15 AuctionWebB0 2023-06-21T10:26:03.772 [main] INFO vCSc : IP:Name :: 192.168.1.14 AuctionWebA0 2023-06-21T10:26:03.790 [main] INFO vCSc : IP:Name :: 192.168.1.8 ElasticWebB0 2023-06-21T10:26:03.807 [main] INFO vCSc : IP:Name :: 192.168.1.7 ElasticWebA0 2023-06-21T10:26:03.823 [main] INFO vCSc : IP:Name :: 192.168.1.13 AuctionMSQ0 2023-06-21T10:26:03.842 [main] INFO vCSc : IP:Name :: 192.168.1.1 Client0 2023-06-21T10:26:03.859 [main] INFO vCSc : IP:Name :: 192.168.1.12 AuctionLB0 2023-06-21T10:26:03.875 [main] INFO vCSc : IP:Name :: 192.168.1.18 AuctionNoSQL0 2023-06-21T10:26:03.893 [main] INFO vCSc : IP:Name :: 192.168.1.17 AuctionAppB0 2023-06-21T10:26:03.911 [main] INFO vCSc : IP:Name :: 192.168.1.4 DS3WebC0 2023-06-21T10:26:03.930 [main] INFO vCSc : IP:Name :: 192.168.1.16 AuctionAppA0 2023-06-21T10:26:03.947 [main] INFO vCSc : IP:Name :: 192.168.1.3 DS3WebB0 2023-06-21T10:26:03.961 [main] INFO vCSc : IP:Name :: 192.168.1.6 ElasticLB0 2023-06-21T10:26:03.977 [main] INFO vCSc : IP:Name :: 192.168.1.2 DS3WebA0 2023-06-21T10:26:03.993 [main] INFO vCSc : IP:Name :: 192.168.1.19 AuctionDB0 2023-06-21T10:26:03.995 [main] INFO vCSc : All 20 VMs Cataloged Successfully 2023-06-21T10:26:03.996 [main] INFO MAIN : Scanning for Starting Tile: 20 VMsPerTile 2023-06-21T10:26:03.996 [main] ERROR MAIN : Starting Tile 1 : ProvisioningNumTiles 1 : No work to be done, delete VMs if you wish to recreate them or increase the ProvisionNumTiles value 2023-06-21T10:26:04.001 [main] ERROR MAIN : Exception Caught: Exiting Early: No work to be done, delete VMs if you wish to recreate them or increase the ProvisionNumTiles value : See Log for details : exitSetting true 2023-06-21T10:26:04.001 [main] INFO MAIN : Email Disabled 2023-06-21T10:26:04.002 [main] INFO MAIN : Ending Early