two questions in vmmark test

[xiaolei_xue]

1、’20231003-13:54:43 Info Process: ElasticLB0 : Get Guest Info failed to start/complete. Returned: RC = 1, STAFResult = vmmark3.1.1-template-031420 20231003-13:54:43 Info ElasticLB0 : Get Guest Info did not run correctly 20231003-13:54:44 Info GuestInfo Results : ElasticLB0 :: Failed : Errors 0 : ErrorMsgs : Warnings 0 : WarningMsgs’ I don't know what cause the queston and how to slove it,please help me to slove it 2、‘20231001-06:45:10 Info errors:2023-10-01 06:44:35,084 WARNING vmtar.py:123 Failed to run cmd: esxcfg-fcoe -l: [Errno 2] No such fileor directory: 'esxcfg-fcoe'’ my esxi8.01 doesn't have this command,how to provide the command,thanks Thanks & Regards Wen

[Rebecca Yo]

Hi Wen,

Problem #1 There are many things that can cause this error. Please zip your VMmark 3 results file and upload it to a reply on this post, thank you. This will help me see the problem.

Problem #2 This is not a problem, you can ignore this warning. It is a warning that occurs when running on vSphere 8.0 and later.

[xiaolei_xue]

Hi RebeccaG, Thank you for your reply. It failed to upload the zip log here. Is there any other ways to upload the log. Thanks Wen

[xiaolei_xue]

Hi RebeccaG, About the second question,I find the error message: Unhandled Exception: System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. Parameter name: startIndex at System.String.Substring (System.Int32 startIndex, System.Int32 length) [0x00037] in :0 at System.String.Substring (System.Int32 startIndex) [0x00008] in :0 at ds2xdriver.ds2Interface.ds2purchase (System.Int32 cart_items, System.Int32[] prod_id_in, System.Int32[] qty_in, System.Int32 customerid_out, System.Int32& neworderid_out, System.Boolean& IsRollback, System.Double& rt) [0x00252] in :0 at ds2xdriver.User.Emulate () [0x00fc8] in :0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in :0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in :0 at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in :0 [ERROR] FATAL UNHANDLED EXCEPTION: System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. Parameter name: startIndex at System.String.Substring (System.Int32 startIndex, System.Int32 length) [0x00037] in :0 at System.String.Substring (System.Int32 startIndex) [0x00008] in :0 at ds2xdriver.ds2Interface.ds2purchase (System.Int32 cart_items, System.Int32[] prod_id_in, System.Int32[] qty_in, System.Int32 customerid_out, System.Int32& neworderid_out, System.Boolean& IsRollback, System.Double& rt) [0x00252] in :0 at ds2xdriver.User.Emulate () [0x00fc8] in :0 at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in :0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in :0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in :0 at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in :0 How to slove it Thanks Wen

[xiaolei_xue]

Hi RebeccaG， The log is too big as below,please show me which logs you need,and I'll zip them to upload here Thanks Wen [root@primeclient Results_20231007093821_tiles11]# ll total 481240 -rw-r--r--. 1 root root 146669597 Oct 7 15:07 198.168.55.110-20231007-145352.tgz -rw-r--r--. 1 root root 137364251 Oct 7 15:06 198.168.55.111-20231007-145396.tgz -rw-r--r--. 1 root root 1144440 Oct 7 14:53 198.168.55.66-20231007-145201.tgz -rw-r--r--. 1 root root 1053758 Oct 7 14:53 198.168.55.67-20231007-145241.tgz -rw-rw-rw-. 1 root root 33 Oct 7 09:38 CheckSSH-198.168.55.110.txt -rw-rw-rw-. 1 root root 33 Oct 7 09:38 CheckSSH-198.168.55.111.txt -rw-rw-rw-. 1 root root 33 Oct 7 09:38 CheckSSH-198.168.55.66.txt -rw-rw-rw-. 1 root root 33 Oct 7 09:38 CheckSSH-198.168.55.67.txt drwxrwxrwx. 2 root root 20480 Oct 7 09:38 configfiles -rw-rw-rw-. 1 root root 401328 Oct 7 14:52 dat.eif -rw-rw-rw-. 1 root root 1064 Oct 7 14:16 deploy-automation-output.txt -rw-rw-rw-. 1 root root 5411 Oct 7 14:16 Deploy-t0.wrf -rw-rw-rw-. 1 root root 990805 Oct 7 14:49 DS3WebA0.wrf -rw-rw-rw-. 1 root root 952792 Oct 7 14:49 DS3WebA10.wrf -rw-rw-rw-. 1 root root 107426 Oct 7 14:49 DS3WebA1.wrf -rw-rw-rw-. 1 root root 969799 Oct 7 14:49 DS3WebA2.wrf -rw-rw-rw-. 1 root root 353795 Oct 7 14:49 DS3WebA3.wrf -rw-rw-rw-. 1 root root 324546 Oct 7 14:49 DS3WebA4.wrf -rw-rw-rw-. 1 root root 369403 Oct 7 14:49 DS3WebA5.wrf -rw-rw-rw-. 1 root root 955439 Oct 7 14:49 DS3WebA6.wrf -rw-rw-rw-. 1 root root 303531 Oct 7 14:49 DS3WebA7.wrf -rw-rw-rw-. 1 root root 939096 Oct 7 14:49 DS3WebA8.wrf -rw-rw-rw-. 1 root root 773582 Oct 7 14:49 DS3WebA9.wrf -rw-rw-rw-. 1 root root 330219 Oct 7 14:49 DS3WebB0.wrf -rw-rw-rw-. 1 root root 656326 Oct 7 14:49 DS3WebB10.wrf -rw-rw-rw-. 1 root root 269760 Oct 7 14:49 DS3WebB1.wrf -rw-rw-rw-. 1 root root 340162 Oct 7 14:49 DS3WebB2.wrf -rw-rw-rw-. 1 root root 309227 Oct 7 14:49 DS3WebB3.wrf -rw-rw-rw-. 1 root root 376847 Oct 7 14:49 DS3WebB4.wrf -rw-rw-rw-. 1 root root 334936 Oct 7 14:49 DS3WebB5.wrf -rw-rw-rw-. 1 root root 585529 Oct 7 14:49 DS3WebB6.wrf -rw-rw-rw-. 1 root root 356890 Oct 7 14:49 DS3WebB7.wrf -rw-rw-rw-. 1 root root 401981 Oct 7 14:49 DS3WebB8.wrf -rw-rw-rw-. 1 root root 361237 Oct 7 14:49 DS3WebB9.wrf -rw-rw-rw-. 1 root root 240933 Oct 7 14:49 DS3WebC0.wrf -rw-rw-rw-. 1 root root 371035 Oct 7 14:49 DS3WebC10.wrf -rw-rw-rw-. 1 root root 239737 Oct 7 14:49 DS3WebC1.wrf -rw-rw-rw-. 1 root root 312090 Oct 7 14:49 DS3WebC2.wrf -rw-rw-rw-. 1 root root 253297 Oct 7 14:49 DS3WebC3.wrf -rw-rw-rw-. 1 root root 342144 Oct 7 14:49 DS3WebC4.wrf -rw-rw-rw-. 1 root root 285742 Oct 7 14:49 DS3WebC5.wrf -rw-rw-rw-. 1 root root 630979 Oct 7 14:49 DS3WebC6.wrf -rw-rw-rw-. 1 root root 293296 Oct 7 14:49 DS3WebC7.wrf -rw-rw-rw-. 1 root root 357562 Oct 7 14:49 DS3WebC8.wrf -rw-rw-rw-. 1 root root 319925 Oct 7 14:49 DS3WebC9.wrf -rw-rw-rw-. 1 root root 401314 Oct 7 14:52 EnvInfo.txt -rw-rw-rw-. 1 root root 871 Oct 7 15:07 ExeReporterScript-198.168.55.110.out -rw-rw-rw-. 1 root root 871 Oct 7 15:06 ExeReporterScript-198.168.55.111.out -rw-rw-rw-. 1 root root 868 Oct 7 14:53 ExeReporterScript-198.168.55.66.out -rw-rw-rw-. 1 root root 868 Oct 7 14:53 ExeReporterScript-198.168.55.67.out drwxrwxrwx. 2 root root 12288 Oct 8 06:43 guestinfofiles -rw-rw-rw-. 1 root root 28580 Oct 7 14:16 ProdDeploy-t0.txt -rw-rw-rw-. 1 root root 31812 Oct 7 14:09 ProdsVMotion-t0.txt -rw-rw-rw-. 1 root root 85166 Oct 7 14:19 ProdVMotion-t0.txt -rw-rw-rw-. 1 root root 28896 Oct 7 14:07 ProdxVMotion-t0.txt -rw-rw-rw-. 1 root root 0 Oct 7 15:07 Reporter-deldir-198.168.55.110.txt -rw-rw-rw-. 1 root root 0 Oct 7 15:07 Reporter-deldir-198.168.55.111.txt -rw-rw-rw-. 1 root root 0 Oct 7 15:07 Reporter-deldir-198.168.55.66.txt -rw-rw-rw-. 1 root root 0 Oct 7 15:07 Reporter-deldir-198.168.55.67.txt -rw-rw-rw-. 1 root root 518 Oct 7 15:07 ReporterResult-198.168.55.110.txt -rw-rw-rw-. 1 root root 518 Oct 7 15:06 ReporterResult-198.168.55.111.txt -rw-rw-rw-. 1 root root 516 Oct 7 14:53 ReporterResult-198.168.55.66.txt -rw-rw-rw-. 1 root root 516 Oct 7 14:53 ReporterResult-198.168.55.67.txt drwxrwxrwx. 2 root root 12288 Oct 7 11:11 restorefiles -rw-rw-rw-. 1 root root 145 Oct 7 14:52 Score_11_Tile_Test.txt drwxrwxrwx. 2 root root 4096 Oct 7 15:07 setupfiles -rw-rw-rw-. 1 root root 7253 Oct 7 14:49 Standby0.wrf -rw-rw-rw-. 1 root root 6873 Oct 7 14:49 Standby10.wrf -rw-rw-rw-. 1 root root 7215 Oct 7 14:49 Standby1.wrf -rw-rw-rw-. 1 root root 7177 Oct 7 14:49 Standby2.wrf -rw-rw-rw-. 1 root root 7139 Oct 7 14:49 Standby3.wrf -rw-rw-rw-. 1 root root 7101 Oct 7 14:49 Standby4.wrf -rw-rw-rw-. 1 root root 7063 Oct 7 14:49 Standby5.wrf -rw-rw-rw-. 1 root root 7025 Oct 7 14:49 Standby6.wrf -rw-rw-rw-. 1 root root 6987 Oct 7 14:49 Standby7.wrf -rw-rw-rw-. 1 root root 6949 Oct 7 14:49 Standby8.wrf -rw-rw-rw-. 1 root root 6911 Oct 7 14:49 Standby9.wrf -rw-rw-rw-. 1 root root 1379 Oct 7 15:07 STAX_Job_2.log -rw-rw-rw-. 1 root root 193767 Oct 7 15:07 STAX_Job_2_User.log -rw-rw-rw-. 1 root root 3556 Oct 7 14:09 SVMotion-t0.wrf -rw-rw-rw-. 1 root root 256 Oct 7 14:52 sykdat.eif -rw-rw-rw-. 1 root root 1175 Oct 7 14:49 TimeChecks.txt -rw-rw-rw-. 1 root root 590 Oct 7 14:49 VC-CheckTime.txt -rw-rw-rw-. 1 root root 62610 Oct 7 10:05 VC-ClusterMapping.txt -rw-rw-rw-. 1 root root 68026 Oct 7 14:52 VC-ClusterReport.txt -rw-rw-rw-. 1 root root 262073 Oct 7 14:52 VC-CollectEvents.csv -rw-rw-rw-. 1 root root 562 Oct 7 10:06 VC-DeploySetup.txt -rw-rw-rw-. 1 root root 334 Oct 7 10:05 VC-DRSsettings.txt -rw-rw-rw-. 1 root root 251 Oct 7 09:38 VC-ListClientHosts.txt -rw-rw-rw-. 1 root root 253 Oct 7 09:38 VC-ListHosts.txt -rw-rw-rw-. 1 root root 415 Oct 7 10:04 VC-ListLUNs.txt -rw-rw-rw-. 1 root root 22818 Oct 7 10:04 VC-ListVMs.txt -rw-rw-rw-. 1 root root 579 Oct 7 10:05 VC-StorageVMotionSetup.txt -rw-rw-rw-. 1 root root 94145271 Oct 7 15:01 vcsupport-20231007-150160.tgz -rw-rw-rw-. 1 root root 3087 Oct 7 15:00 VC-Support-output-198.168.55.178.txt -rw-rw-rw-. 1 root root 1319 Oct 7 15:01 VCsupportScript-198.168.55.178.out -rw-rw-rw-. 1 root root 566 Oct 7 10:05 VC-XVMotionSetup.txt -rw-rw-rw-. 1 root root 31721 Oct 7 09:38 VMmark3.properties -rw-rw-rw-. 1 root root 1010 Oct 7 14:19 VMmark3-RMQsend.log -rw-rw-rw-. 1 root root 566919 Oct 7 14:22 VMmark3-RunService.log -rw-rw-rw-. 1 root root 98 Oct 7 09:38 VMmark3-ServicePreCheck.txt -rw-rw-rw-. 1 root root 192 Oct 7 14:49 VMmark3-ServiceShutdown.txt -rw-rw-rw-. 1 root root 138546 Oct 7 15:07 VMmark3-STAX_Job_2_User-Parsed.log -rw-rw-rw-. 1 root root 26 Oct 7 14:49 VMmark3Stop.stop -rw-rw-rw-. 1 root root 7468 Oct 7 14:19 VMotion-t0.wrf -rw-rw-rw-. 1 root root 36410391 Oct 7 14:49 WeathervaneAuction0.wrf -rw-rw-rw-. 1 root root 942399 Oct 7 14:49 WeathervaneAuction10.wrf -rw-r--r--. 1 root root 36410391 Oct 8 06:24 WeathervaneAuction1.wrf -rw-r--r--. 1 root root 984520 Oct 8 06:25 WeathervaneAuction2.wrf -rw-rw-rw-. 1 root root 984520 Oct 7 14:49 WeathervaneAuction3.wrf -rw-r--r--. 1 root root 984520 Oct 8 06:25 WeathervaneAuction4.wrf -rw-r--r--. 1 root root 984520 Oct 8 06:25 WeathervaneAuction5.wrf -rw-r--r--. 1 root root 984520 Oct 8 06:25 WeathervaneAuction6.wrf -rw-rw-rw-. 1 root root 997188 Oct 7 14:49 WeathervaneAuction7.wrf -rw-r--r--. 1 root root 984520 Oct 8 06:25 WeathervaneAuction8.wrf -rw-r--r--. 1 root root 984520 Oct 8 06:25 WeathervaneAuction9.wrf -rw-rw-rw-. 1 root root 1175123 Oct 7 14:49 WeathervaneElastic0.wrf -rw-rw-rw-. 1 root root 1106017 Oct 7 14:49 WeathervaneElastic10.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:24 WeathervaneElastic1.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:26 WeathervaneElastic2.wrf -rw-rw-rw-. 1 root root 1183749 Oct 7 14:49 WeathervaneElastic3.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:26 WeathervaneElastic4.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:26 WeathervaneElastic5.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:26 WeathervaneElastic6.wrf -rw-rw-rw-. 1 root root 1269129 Oct 7 14:49 WeathervaneElastic7.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:26 WeathervaneElastic8.wrf -rw-r--r--. 1 root root 1175123 Oct 8 06:26 WeathervaneElastic9.wrf drwxrwxrwx. 2 root root 4096 Oct 7 14:52 workloadfiles -rw-rw-rw-. 1 root root 3274 Oct 7 14:07 XVMotion-t0.wrf

[Rebecca Yo]

Hi Wen,

I apologize I didn't get to this October 5, and VMware had a company holiday October 6.

Yes, I see from your directory, you have a completed VMmark run which is too large to upload to the forum.

Here is how to send me the results.

Zip the results folder (e.g. .zip, .tgz, .rar), and please visit

http://ftpsite.vmware.com

user: inbound

password: inbound

Click New Directory - F7 and choose a new directory name. Click OK.

Click Change Directory and input your new directory name. Click Change.

Click Upload to select your zipped files.

Finally, send me the directory name and filenames.

Thank you,

Rebecca

[xiaolei_xue]

Hi RebeccaG, Thank you for your reply. Please help me to reslove the problem as below. ===== XML Information ===== File: /root/VMmark3/xml/generic_functions.xml, Machine: local Line 141: Error in element type "script". ===== Python Error Information ===== com.ibm.staf.service.stax.STAXPythonEvaluationException: Traceback (most recent call last): File "", line 2, in NameError: name 'ErrorMsgs' is not defined ===== Call Stack for STAX Thread 64 ===== Thanks, Wen

[xiaolei_xue]

HI RebeccaG， The vmmark test failed in the last test ,and I upload the log on the ftp. the the directory name is 'Wen',and the filenames are Results_20231011065120_test1_2.zip.001,Results_20231011065120_test1_2.zip.002,Results_20231011065120_test1_2.zip.003. I can upload them together while it always fails for Authentication Thans， Wen

[Rebecca Yo]

Hi Wen, I received three files from you: 

Results_20231011065120_test1_2.zip.001,Results_20231011065120_test1_2.zip.002,Results_20231011065120_test1_2.zip.003.

I'm having difficulty extracting the files. Can you please use a command like this on the Prime Client to zip your VMmark results files? 

zip -r Results_20190326174141.zip Results_20190326174141

Thank you,

Rebecca

[xiaolei_xue]

Hi RebeccaG， Because I failed to upload the package “Results_20231011065120_test1_2.zip”directly for Authentication fails,so I compressed the package again by volume. Can you use 7-zip to decompress the three packages together? Thanks, Wen

[Rebecca Yo]

Hi Wen, yes I successfully unzipped your file using 7-zip, thank you.

There are errors causing Weathervane to not run and all infrastructure operations (vmotion, svmotion, xvmotion, deploy) are failing.

I think you have some issues with your shared storage and possibly vCenter Server.

The log VC-CollectEvents.csv shows many storage connectivity errors on hosts 198.168.55.112 and .113, 198.168.55.68 and .69, and these hosts are in SUTCluster and ClientCluster respectively. However, VC-ListHosts.txt shows only .111 and 110 in your SUTCluster and .67 and .66 in ClientCluster. Were these other hosts maybe in maintenance mode? Either way these storage errors could be affecting your vmmark run. 

I would recommend you remove any unused hosts / hosts with errors from your VMmark clusters.

Your file VC-ListLUNs.txt also shows an error with the vmotion LUN:

Name : Free Space : Capacity : Uncommitted : Type : Multiple Host Access : Maintenance Mode
VMotion : 7819GB : 7821GB : ERROR : VMFS : true : normal

Second, all infrastructure operations (vmotion, xvmotion, svmotion, deploy) .wrf files show the response "FAIL". This error from vCenter Server means the operation cannot complete. To troubleshoot this, replicate the activity manually:

Using the vCenter UI, manually vmotion, storage vmotion or combined vmotion and storage vmotion a VMmark VM from one host to the other host in the SUT cluster.

Does it complete successfully? If not, watch the error that vCenter Server returns. You will need to fix this before you can run VMmark.

Thank you and please let me know if you have any further questions,

Rebecca

 

[xiaolei_xue]

Hi RebeccaG

The vCenter has two datacenter for two tests.

hosts 198.168.55.112 and .113,are the first test suts, 198.168.55.68 and .69,are the first suts' clients.

.111 and 110 are the second test suts and .67 and .66 are the suts' cliemts.

The two tests use different storage but the same vCenter.

If it affects the test.

Thank you ,

Wen

[xiaolei_xue]

Hi RebeccaG, Here is another problem as below.Why the test runs too short. 20231013-02:00:50 Info Error: tile 1 DS3WebA run too short, elapsed time = 50,expected time = 189 20231013-02:00:50 Info Error: tile 1 AuctionLB run too short, elapsed time = 50, expected time = 11220 20231013-02:01:50 Info Error: tile 2 AuctionLB run too short, elapsed time = 50, expected time = 11160 20231013-02:01:51 Info Error: tile 2 DS3WebA run too short, elapsed time = 51,expected time = 188 20231013-02:02:50 Info Error: tile 3 DS3WebA run too short, elapsed time = 50,expected time = 187 20231013-02:02:50 Info Error: tile 3 AuctionLB run too short, elapsed time = 50, expected time = 11100 20231013-02:03:50 Info Error: tile 4 DS3WebA run too short, elapsed time = 50,expected time = 186 20231013-02:03:50 Info Error: tile 4 AuctionLB run too short, elapsed time = 50, expected time = 11040 20231013-02:04:50 Info Error: tile 5 AuctionLB run too short, elapsed time = 50, expected time = 10980 20231013-02:04:51 Info Error: tile 5 DS3WebA run too short, elapsed time = 51,expected time = 185 20231013-02:05:50 Info Error: tile 6 AuctionLB run too short, elapsed time = 50, expected time = 10920 20231013-02:05:51 Info Error: tile 6 DS3WebA run too short, elapsed time = 51,expected time = 184 20231013-02:06:50 Info Error: tile 7 DS3WebA run too short, elapsed time = 50,expected time = 183 20231013-02:06:50 Info Error: tile 7 AuctionLB run too short, elapsed time = 50, expected time = 10860 20231013-02:07:50 Info Error: tile 8 AuctionLB run too short, elapsed time = 50, expected time = 10800 20231013-02:07:51 Info Error: tile 8 DS3WebA run too short, elapsed time = 51,expected time = 182 20231013-02:08:50 Info Error: tile 9 DS3WebA run too short, elapsed time = 50,expected time = 181 20231013-02:08:50 Info Error: tile 9 AuctionLB run too short, elapsed time = 50, expected time = 10740 20231013-02:09:50 Info Error: tile 10 AuctionLB run too short, elapsed time =50, expected time = 10680 20231013-02:09:51 Info Error: tile 10 DS3WebA run too short, elapsed time = 51, expected time = 180 20231013-05:25:06 Info Tile 0 : Prime Client Time 1697174705 UTC : Client0 Time 1697174702 UTC :: TimeErrors : 0 :: Clock Skew 3 20231013-05:25:08 Info Tile 1 : Prime Client Time 1697174707 UTC : Client1 Time 1697174705 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:10 Info Tile 2 : Prime Client Time 1697174709 UTC : Client2 Time 1697174707 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:13 Info Tile 3 : Prime Client Time 1697174711 UTC : Client3 Time 1697174709 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:15 Info Tile 4 : Prime Client Time 1697174714 UTC : Client4 Time 1697174711 UTC :: TimeErrors : 0 :: Clock Skew 3 20231013-05:25:17 Info Tile 5 : Prime Client Time 1697174716 UTC : Client5 Time 1697174714 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:19 Info Tile 6 : Prime Client Time 1697174718 UTC : Client6 Time 1697174716 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:22 Info Tile 7 : Prime Client Time 1697174720 UTC : Client7 Time 1697174718 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:24 Info Tile 8 : Prime Client Time 1697174723 UTC : Client8 Time 1697174721 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:26 Info Tile 9 : Prime Client Time 1697174725 UTC : Client9 Time 1697174723 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:28 Info Tile 10 : Prime Client Time 1697174727 UTC : Client10 Time 1697174725 UTC :: TimeErrors : 0 :: Clock Skew 2 20231013-05:25:32 Info Error: Tile 2 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 3 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 1 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 6 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 7 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 4 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 8 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 5 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 9 Weathervane results number not correctlyidentified 20231013-05:25:32 Info Error: Tile 10 Weathervane results number not correctlyidentified Thanks, Wen

[Rebecca Yo]

Hi Wen,

It should be ok if those hosts are in a different datacenter with same vCenter Server.

For the new error, please zip your VMmark results file and if small enough, attach to this forum thread. If the zip file is too large please put it on ftpsite like last time.

Also please try to manually vmotion or storage vmotion your VMmark VMs as it is failing in your environment. Also please check why your vMotion LUN shows error from my last post, it is the column 'uncommitted' which shows the error.

Your file VC-ListLUNs.txt also shows an error with the vmotion LUN:

Name : Free Space : Capacity : Uncommitted : Type : Multiple Host Access : Maintenance Mode
VMotion : 7819GB : 7821GB : ERROR : VMFS : true : normal

Second, all infrastructure operations (vmotion, xvmotion, svmotion, deploy) .wrf files show the response "FAIL". This error from vCenter Server means the operation cannot complete. To troubleshoot this, replicate the activity manually:

Using the vCenter UI, manually vmotion, storage vmotion or combined vmotion and storage vmotion a VMmark VM from one host to the other host in the SUT cluster.

Does it complete successfully? If not, watch the error that vCenter Server returns. You will need to fix this before you can run VMmark.

[xiaolei_xue]

Hi RebeccaG I have a issue in the Score.txt . Number_of_Compliance_Issues (identified by '*' or '+') : 1 Issues Found : Tile4-weathervaneauction-p1 Median_Phase : p1 I have uploaded the zip log on the ftp, the the directory name is 'Wen',and the filenames are Results_20231023072053_10tiles_2.zip.00*. Please use 7-zip to decompress the six packages together. Thank You Wen

[Rebecca Yo]

Hi Wen, this is great. I see you resolved your earlier problems and are running 10 tiles with no setup issues.

Number_of_Compliance_Issues (identified by '*' or '+') : 1 Issues Found : Tile4-weathervaneauction-p1 Median_Phase : p1

This is a Quality of Service (QoS) compliance issue. It means that the VMmark run failed to meet quality of service (i.e. Application Latency) requirements due to resource contention.

This is normal when you are running a large number of tiles as eventually the QoS will fail due to storage contention, CPU contention, or other resource constraints.

The failing tile, tile 4 is just barely failing. A passing score is less than 1.

In VMmark3-graphs.html, it shows WeathervaneAuction has two spikes in QoS during the middle of the run. This is why the QoS failed. If you can resolve the cause of this poor performance, you might be able to pass a VMmark run at 10 tiles or more. You could also run VMmark again, and might be able to pass if you get lucky (slightly better performance from your environment).

Thank you,

Rebecca