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.
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
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
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
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
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
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.
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