VMware VMmark™ Discussions topics

VMmark Run Tiles Target and Source Datastorages are the same

oporras — Sun, 29 Oct 2023 15:48:11 GMT

I'm having trouble completing the "VMmark Run Tiles" phase for VMmark 3.1.1
All this occurs in the phase of executing the tiles. (VMmark Run Tiles Fase)
In the properties file I have tried different definitions:

Case 1 - Results_20231029031758_tile0.zip
Settings:
SVmotion/SVMotionLUNs = datastorage1,datastorage2
XVmotion/XVMotionLUNs = datastorage3,datastorage4
Deploy/DeployLUNs = datastorage5
------------- All different data storage -------------
File configuration:
SVmotion/SVMotionLUNs = DS_AMSA_QA_DEV,DS_BASESWIN_QA_01
XVmotion/XVMotionLUNs = DS_CLIPTEST02,DS_AMSADEV_01
Deploy/DeployLUNs = DS_CLIPTEST01

VM location on Tile0 for each data storage
DS_AMSA_QA_DEV >
Standby0
DS_CLIPTEST02 >
DS3WebA
DS_CLIPTEST01 >
vmmark3.1.1-template-031420 (VM status off)
Rest of the Tiles0 (DS3DB0, AuctionLB0, DS3WebB0, etc.)

Case 2 - Results_20231029035855_tile0.zip
Settings:
SVmotion/SVMotionLUNs = datastorage1,datastorage2
XVmotion/XVMotionLUNs = datastorage2,datastorage1
Deploy/DeployLUNs = datastorage1
--------- Using two different data storages ---------
--------- This is the expected configuration --------
File configuration:
SVmotion/SVMotionLUNs = DS_CLIPTEST01,DS_CLIPTEST02
XVmotion/XVMotionLUNs = DS_CLIPTEST02,DS_CLIPTEST01
Deploy/DeployLUNs = DS_CLIPTEST01

VM location on Tile0 for each data storage
DS_CLIPTEST01 >
Standby0
DS_CLIPTEST02 >
DS3WebA
DS_CLIPTEST01 >
vmmark3.1.1-template-031420 (VM status off)
Rest of the Tiles0 (DS3DB0, AuctionLB0, DS3WebB0, etc.)

The error persists for any of the cases.
The VMmark-STAX_Job_2_User-Parsed log shows at the end of the line that the source data storage is the same as the target

Info: DS3 Tile0 Starting with 100GB DB for 10800 secs
InfraOps: Request sVMotion0 #1 : VM Standby0
InfraOps: Request Deploy0 #0 : DeployVM0 onto SUT Host04.XXX.local in LUN DS_CLIPTEST01 using 11.11.11.11
Service Requested Stop: ExceptionFound: SVMotion TargetDatastore Exception : Review Log and Configuration : :Target and Source Datastores are the same
VMmark3: Service Requested Stop: ExceptionFound: SVMotion TargetDatastore Exception : Review Log and Configuration : :Target and Source Datastores are the same : 90.04 (secs)

Additionally, the VMmark3-RunService log shows an error in an attempt to execute the SVMotion

INFO ST20 : Relocation Storage VMotion VM: DS3WebA0 : HostsList Host01.XXX.local;Host04.XXX.local;Host05.XXX.local;Host03.XXX.local;Host02.XXX.local: SourceHost Host01.XXX.local
INFO ST20 : Relocation Storage VMotion VM HostsList Size: 5
INFO ST20 : Info: Relocation Storage VMotion VM : CurrentHostIndex 0 WantedHostIndex 0 AltHostIndex 1)
INFO ST20 : RelocateStorageVM VMotion Unecessary
INFO ST20 : Relocation Storage VMotion VM: Standby0 : HostsList Host01.XXX.local;Host04.XXX.local;Host05.XXX.local;Host03.XXX.local;Host02.XXX.local: SourceHost Host01.XXX.local
INFO ST20 : Relocation Storage VMotion VM HostsList Size: 5
INFO ST20 : Info: Relocation Storage VMotion VM : CurrentHostIndex 0 WantedHostIndex 0 AltHostIndex 1)
INFO ST20 : RelocateStorageVM VMotion Unecessary
ERROR MAIN : Exception Caught: SVMotion TargetDatastore Exception : Review Log and Configuration : Target and Source Datastores are the same : exitSetting true
INFO MAIN : Email Disabled
INFO MAIN : Starting StopFile Creation
INFO MAIN : Ending Early

how many Tiles can I run?

oporras — Thu, 26 Oct 2023 23:42:22 GMT

With 240 cpu, 7.5TB of ram and 16TB of storage, how many Tiles can I run?

thank

VMmark3 tiles do I run for 150VM?

oporras — Thu, 26 Oct 2023 19:52:20 GMT

If I want to run 150VM how many tiles do I run?

VMmark3 Properties

oporras — Sun, 22 Oct 2023 20:04:48 GMT

Good afternoon. I am trying to run VMmark3 in a VMware vsphere environment with 5 clustered hosts. However, when I do the provisioning, I get an error that the Data Center is not recognized. Does someone know how to solve this problem? Thank you in advance for your help.

two questions in vmmark test

xiaolei_xue — Wed, 04 Oct 2023 14:59:56 GMT

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

Run failure due to Guest Info gathering on 2 VMs

BhojaRavi — Thu, 20 Jul 2023 17:19:41 GMT

Seeing failure during Run with Tile0.

20230720-07:35:18 Info Guest Info failures for the following machines: 2 machines : DS3DB0 ElasticWebB0 Error Messages DS3DB0= :ElasticWebB0= :

The user guide advices to reboot the VMs reporting issues. I have followed the same rebooting all VMs of the Tile including PrimeClient with no success.

Attaching the results output. Please help to get through the run.

Testing CPU and memory performance with vmmark

jansykoracp — Wed, 19 Jul 2023 06:42:57 GMT

Is it possible to test only CPU and memory performance with vmmark? I don't want to test storage,web,db - none of that type of systems.

Thank you Jan

VMmark test failing with Trust level 5 required for the PROCESS service's START request

nimo1983 — Tue, 04 Jul 2023 15:52:48 GMT

Hello Team,

Running VMMark 3.1.1 against a 4 host setup.

Num of hosts: 4
ESXi version: VMware ESXi, 8.0.1, 21495797
Processor Type: Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz
Logical Processors: 64 (per host)
Prime client running with a single NIC. The client VMs and VMmark VMs are running on the same cluster.
No of tiles: 2
Storage : vSAN

When running the test, it fails with the below error:

The process failed to start. RC: 25, STAFResult: Trust level 5 required for the PROCESS service's START request

The host file is updated correctly and VMs are reachable. Trust level is 5 on all VMs.

Attachments: Results folder including the VMMark properties files.

Looking forward for expert inputs to get over this and complete the testing.

Regards,

Niyaz

vmmark 3.1.1 error in element type "process"

mashimarowei — Tue, 27 Jun 2023 02:47:29 GMT

Hi Sir

Run STAX vmmark3_main.xml , get these error messages

may you provide me how to deal with this problem?

Deploy tile0 VMMark 3.1.1 fail

mashimarowei — Fri, 16 Jun 2023 17:39:00 GMT

how to fix with this problem , please

[root@primeclient VMmark3]# java -jar tools/VMmark3Service.jar -c VMmark3.properties

VMmark3Service_v1.0.17
Reading VMmark3 Properties File
ConfigFile = VMmark3.properties
2023-06-16T18:17:29.247 [main] INFO MAIN : VMmark3Service_v1.0.17
2023-06-16T18:17:29.250 [main] INFO MAIN : ConfigFile: VMmark3.properties Loaded
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: AllowRunOverwrite: true
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: EmailNotifications: true
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: EmailList: []
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: EmailSMTP:
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: EmailFrom:
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: EmailPort:
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: RunName: vmmark3-1tiles
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: PrimeClient: 192.168.1.251
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: vCServer: 192.168.1.250
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: vCServerUsername: administrator@vsphere.local
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: vCServerPassword: ********
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: vCServerDatacenter: Datacenter
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: Tiles: 1
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningIPstaticStart: 192.168.1.1
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningIPmode: static
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningSource: tile0
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningNumTiles: 1
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningDatastores: Client:datastore1,DS3WebA:datastore2,DS3WebB:datastore2,DS3WebC:datastore2,DS3DB:datastore2,AuctionLB:datastore2,AuctionMSQ:datastore2,AuctionWebA:datastore2,AuctionWebB:datastore2,AuctionAppA:datastore2,AuctionAppB:datastore2,AuctionNoSQL:datastore2,AuctionDB:datastore2,ElasticLB:datastore2,ElasticWebA:datastore2,ElasticWebB:datastore2,ElasticAppA:datastore2,ElasticAppB:datastore2,ElasticDB:datastore2,Standby:datastore2
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningTimeZone: UTC
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningGateway: 192.168.1.254
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningSubnetMask: 255.255.255.0
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningNetworkLabel: VM Network
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisioningNetworkType: standard
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: ProvisionPingIpSeconds: 600
2023-06-16T18:17:29.251 [main] INFO MAIN : DeployVMinfo: DeployVM0:192.168.1.245,DeployVM1:192.168.1.246
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: vCServerVMmark3Cluster: ClientCluster
2023-06-16T18:17:29.251 [main] INFO MAIN : Config:: vCServerClientCluster: ClientCluster
2023-06-16T18:17:29.251 [main] INFO MAIN : Initializing Env
2023-06-16T18:17:29.251 [main] INFO MAIN : AllowRunOverwrite Enabled, overwriting directory
2023-06-16T18:17:29.252 [main] INFO MAIN : Hosts file Stub Output: hosts-stub.txt
2023-06-16T18:17:29.252 [main] INFO MAIN : ConfigFileName: VMmark3.properties
2023-06-16T18:17:29.252 [main] INFO MAIN : Copy File: /root/VMmark3/VMmark3.properties : /root/VMmark3/provisioning-output/vmmark3-1tiles/VMmark3.properties
2023-06-16T18:17:29.281 [main] ERROR MAIN : Email Notifications Disabled due to Email Settings Errors
2023-06-16T18:17:29.281 [main] INFO MAIN : Initializing Static VMmapping Info
2023-06-16T18:17:29.283 [main] INFO COMM : BuildingStaticIps with Static Start: 192.168.1.1 and 1 Tiles
2023-06-16T18:17:29.283 [main] INFO COMM : Working with User Defined DeployVMinfo: DeployVM0:192.168.1.245,DeployVM1:192.168.1.246
2023-06-16T18:17:29.283 [main] INFO MAIN : Initialization Completed Successfully
2023-06-16T18:17:29.283 [main] INFO MAIN : Starting VMmark3 Provisioning Service
2023-06-16T18:17:29.283 [main] INFO MAIN : Logging Into vCServer: 192.168.1.250
2023-06-16T18:17:29.503 [main] INFO MAIN : Validating Setup Parameters
2023-06-16T18:17:29.503 [main] INFO MAIN : Provisioning DS3DB is Not Active
2023-06-16T18:17:29.503 [main] INFO MAIN : Setup Completed Successfully
2023-06-16T18:17:29.513 [main] INFO vCSc : Validating Provisioning Parameters
2023-06-16T18:17:29.516 [main] INFO vCSc : vCServerDatacenter: Datacenter Found
2023-06-16T18:17:29.516 [main] INFO vCSc : vCServerDatacenter: Datacenter Found
2023-06-16T18:17:29.516 [main] INFO vCSc : Scanning Client Cluster ClientCluster for Host Systems
2023-06-16T18:17:29.552 [main] INFO vCSc : Host[0] : 192.168.1.253 : Connection connected : Power poweredOn : MaintenanceMode false : Active
2023-06-16T18:17:29.555 [main] INFO vCSc : 1 Active VMmark3 Hosts
2023-06-16T18:17:29.555 [main] INFO vCSc : 1 Client Hosts Under Test
2023-06-16T18:17:29.555 [main] INFO vCSc : Scanning Cluster ClientCluster for Host Systems
2023-06-16T18:17:29.583 [main] INFO vCSc : Host[0] : 192.168.1.253 : Connection connected : Power poweredOn : MaintenanceMode false : Active
2023-06-16T18:17:29.585 [main] INFO vCSc : 1 Active VMmark3 Hosts
2023-06-16T18:17:29.585 [main] INFO vCSc : 1 Hosts Under Test
2023-06-16T18:17:29.585 [main] INFO vCSc : Scanning for Provisioning Source VMs:
2023-06-16T18:17:29.595 [main] INFO vCSc : VM: ElasticDB0 Present
2023-06-16T18:17:29.604 [main] INFO vCSc : VM: ElasticAppB0 Present
2023-06-16T18:17:29.612 [main] INFO vCSc : VM: ElasticAppA0 Present
2023-06-16T18:17:29.621 [main] INFO vCSc : VM: Standby0 Present
2023-06-16T18:17:29.629 [main] INFO vCSc : VM: DS3DB0 Present
2023-06-16T18:17:29.636 [main] INFO vCSc : VM: AuctionWebB0 Present
2023-06-16T18:17:29.643 [main] INFO vCSc : VM: AuctionWebA0 Present
2023-06-16T18:17:29.652 [main] INFO vCSc : VM: ElasticWebB0 Present
2023-06-16T18:17:29.660 [main] INFO vCSc : VM: ElasticWebA0 Present
2023-06-16T18:17:29.668 [main] INFO vCSc : VM: AuctionMSQ0 Present
2023-06-16T18:17:29.676 [main] INFO vCSc : VM: Client0 Present
2023-06-16T18:17:29.687 [main] INFO vCSc : VM: AuctionLB0 Present
2023-06-16T18:17:29.696 [main] INFO vCSc : VM: AuctionNoSQL0 Present
2023-06-16T18:17:29.703 [main] INFO vCSc : VM: AuctionAppB0 Present
2023-06-16T18:17:29.710 [main] INFO vCSc : VM: DS3WebC0 Present
2023-06-16T18:17:29.718 [main] INFO vCSc : VM: AuctionAppA0 Present
2023-06-16T18:17:29.726 [main] INFO vCSc : VM: DS3WebB0 Present
2023-06-16T18:17:29.734 [main] INFO vCSc : VM: ElasticLB0 Present
2023-06-16T18:17:29.741 [main] INFO vCSc : VM: DS3WebA0 Present
2023-06-16T18:17:29.751 [main] INFO vCSc : VM: AuctionDB0 Present
2023-06-16T18:17:29.751 [main] INFO vCSc : Provision Source VMs Present : Environment Ready for Scale Out of VMs
2023-06-16T18:17:29.751 [main] INFO vCSc : Identifying Cluster Hosts' Networking: Provisioning NetworkLabel 'VM Network' Type standard
2023-06-16T18:17:29.770 [main] INFO vCSc : Reviewing host portgroups : 192.168.1.253
2023-06-16T18:17:29.770 [main] INFO vCSc : 192.168.1.253: 'VM Network' NetworkLabel : 'vSwitch0' vSwitch: Target NetworkLabel
2023-06-16T18:17:29.770 [main] INFO vCSc : 192.168.1.253: 'Management Network' NetworkLabel : 'vSwitch0' vSwitch
2023-06-16T18:17:29.770 [main] INFO vCSc : Provisioning NetworkLabel VM Network Found on All Hosts
2023-06-16T18:17:29.770 [main] WARN vCSc : Skipping Network tests as TemplateVM is null
2023-06-16T18:17:29.770 [main] INFO MAIN : Provisioning Validation Passed
2023-06-16T18:17:29.771 [main] INFO RMQ : Starting RabbitMQ DeleteQueue
2023-06-16T18:17:29.809 [main] INFO RMQ : Deleted Queue vmmark
2023-06-16T18:17:29.812 [main] INFO vCSc : Cataloging Deployed VMs (1 Tiles)
2023-06-16T18:17:29.830 [main] INFO vCSc : IP:Name :: 192.168.1.11 ElasticDB0
2023-06-16T18:17:29.845 [main] INFO vCSc : IP:Name :: 192.168.1.10 ElasticAppB0
2023-06-16T18:17:29.860 [main] INFO vCSc : IP:Name :: 192.168.1.9 ElasticAppA0
2023-06-16T18:17:29.874 [main] INFO vCSc : IP:Name :: 192.168.1.20 Standby0
2023-06-16T18:17:29.889 [main] INFO vCSc : IP:Name :: 192.168.1.5 DS3DB0
2023-06-16T18:17:29.905 [main] INFO vCSc : IP:Name :: 192.168.1.15 AuctionWebB0
2023-06-16T18:17:29.919 [main] INFO vCSc : IP:Name :: 192.168.1.14 AuctionWebA0
2023-06-16T18:17:29.933 [main] INFO vCSc : IP:Name :: 192.168.1.8 ElasticWebB0
2023-06-16T18:17:29.946 [main] INFO vCSc : IP:Name :: 192.168.1.7 ElasticWebA0
2023-06-16T18:17:29.960 [main] INFO vCSc : IP:Name :: 192.168.1.13 AuctionMSQ0
2023-06-16T18:17:29.974 [main] INFO vCSc : IP:Name :: 192.168.1.1 Client0
2023-06-16T18:17:29.988 [main] INFO vCSc : IP:Name :: 192.168.1.12 AuctionLB0
2023-06-16T18:17:30.003 [main] INFO vCSc : IP:Name :: 192.168.1.18 AuctionNoSQL0
2023-06-16T18:17:30.017 [main] INFO vCSc : IP:Name :: 192.168.1.17 AuctionAppB0
2023-06-16T18:17:30.030 [main] INFO vCSc : IP:Name :: 192.168.1.4 DS3WebC0
2023-06-16T18:17:30.043 [main] INFO vCSc : IP:Name :: 192.168.1.16 AuctionAppA0
2023-06-16T18:17:30.058 [main] INFO vCSc : IP:Name :: 192.168.1.3 DS3WebB0
2023-06-16T18:17:30.071 [main] INFO vCSc : IP:Name :: 192.168.1.6 ElasticLB0
2023-06-16T18:17:30.084 [main] INFO vCSc : IP:Name :: 192.168.1.2 DS3WebA0
2023-06-16T18:17:30.104 [main] INFO vCSc : IP:Name :: 192.168.1.19 AuctionDB0
2023-06-16T18:17:30.106 [main] INFO vCSc : All 20 VMs Cataloged Successfully
2023-06-16T18:17:30.107 [main] INFO MAIN : Scanning for Starting Tile: 20 VMsPerTile
2023-06-16T18:17:30.107 [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-16T18:17:30.111 [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-16T18:17:30.111 [main] INFO MAIN : Email Disabled
2023-06-16T18:17:30.111 [main] INFO MAIN : Ending Early

NS/EW traffic performance on Dimension product

john72 — Fri, 09 Jun 2023 21:44:47 GMT

I wonder this is right channel to ask this

Do we have VMC Dimension performance of NS/EW traffic announsed to customers?

THx

Is this to be concerned about. DAVG figures. Storage latency?

Virtualboy1 — Thu, 08 Jun 2023 03:31:46 GMT

So I have been suspecting storage latency issues in our VMware environment for a while. So been working on ways to find solution to the problem. Core issue has been ESXi host disconnecting from vCenter server and getting greyed out. When this happens we can't do much with the host or VM's on it except for shutting them down and starting them on different ESXi host.

As a result I've been monitoring things using ESXTOP while I work on remediation and understand bottlenecks. Before DAVG figures were spiking above 25. So apparently anything above 25 is bad and indicates storage latency.

However today when I was monitoring one of the host I came across these crazy figures for DAVG. And to me those looks bad.

Now I understand I can't just look at DAVG and need to look at bigger picture.

Can someone please look at attached and let me know how bad this is? Are spikes like this in DAVG normal? Or should it ideally not got this high even for a spike?

More about environment below.

VMware ESXi, 7.0.3, 20842708

vCenter 7.0.3 21477706

Dell PowerEdge hardware

Dell Storage Center SCSI storage array

iSCSI protocol being used to connect to storage array using software iSCSI adapter

Backup runs mostly through the day so there is no definite time when backup runs or doesn't run

Also have Zerto which is used for replication purpose

Finally we also have live volumes at storage array layer

We're looking at things like queue depth at iSCSI vmk port, making sure round robin is used for path selection etc. I must mention all firmware and drivers are updated recently already. This has been double checked already including compatibitlity

Kernel panic -not syning: Fatal exception

Avaakaford — Wed, 24 May 2023 16:20:34 GMT

Hi Team,

I'm facing Kernel panic error on vmmark & it's cloned VM's on following hardware .

Hypervisor: VMware ESXi, 7.0.3, 20842708
Model: ProLiant DL365 Gen11
Processor Type: AMD EPYC 9354 32-Core Processor

same environment is working fine on Following hardware

Hypervisor: VMware ESXi, 7.0.3, 20842708
Model: ProLiant DL360 Gen11
Processor Type: Intel(R) Xeon(R) Gold 6430

Can you please suggest for resolution for this

Thanks & Regards

Ajay Vaaka

vmmark3.1.1-template-031420 missing ISO

Avaakaford — Tue, 23 May 2023 23:37:55 GMT

Hi Team,

vmmark3.1.1-template-031420 is missing in VMware website . May i know , new version is coming ?

Thanks & Regards

Ajay Vaaka

iMac on VMware Horizon Client Bluetooth and Blurry Video Issues

fkhan11 — Mon, 17 Apr 2023 14:30:09 GMT

Hi All,

I have a customer who is using an iMac (Retina 5K, 27-inch, 2019). I will attach the full specs.

VMware Horizon Client 8.9.0

Issue:

1) Video on Zoom and Teams application is blurry

2) Bluetooth keyboard and mouse keeps disconnecting

These both issues don't happen locally on users iMac but happen on virtual desktop. Any suggestions will be helpful.

Kind Regards,

Farrah

Failed Test Runs

browney595 — Thu, 16 Feb 2023 09:21:15 GMT

I have all tiles deployed with no issues however when trying to run the test im getting the following errors at the Guestinfo collection stage.

Client SSL handshake timeout: 22 Endpoint: ssl:DS3DB0

This is happening for

Standby0, DS3WebA0, DS3WebB0, DS3WebC0 and DS3DB0

All other machines in the tile come back with results other than these machines. I have removed and redeployed the tile and still face the same issue

Kind Regards

Martin Brown

Failing to deploy tile0

browney595 — Tue, 14 Feb 2023 15:01:55 GMT

Hi When trying to run VMmark to provision tile0 I am getting the following issue

The environment is vSphere 7.0 U3

2023-02-14T14:43:18.852 [main] INFO vCSc : Reviewing host portgroups : <hostname removed>
Exception in thread "main" java.lang.NullPointerException
at com.vmware.vmmark.VcsComm.ValidateProvisioningConfiguration(VcsComm.java:682)
at com.vmware.vmmark.VMmark3.main(VMmark3.java:1779)

The process simply fails here any ideas?

Thanks

Martin

VMware ESXi 7.0.2 U on-prem disk performances issue on VM

SullivanDr — Wed, 30 Nov 2022 09:05:42 GMT

Hello guys,

I have an issue with a VM on a VMware ESXi 7.0.2 platform on prem

A VM has been generated to me so I can install a software but I have disk performances prerequisites to respect (SSD, 250Mb/s throughput and over 7500 IOPS).

The VM provided doesn't match those prerequisite :

IOPS are below 500 and throughput is around 20-30 Mb/s.

The on-prem environment should be using SSD disks but based on the performances it doesn't look like SSD.

When we create the VM, we don't have much option when we select the disk, it's just "Parallel SCSI".

Is there anything we can do to enhance performances of the disk and reach my target ?

Thank you for your help.

Best Regards,

Sullivan Drouard

VMmark3-ParsePowerData failed to start/complete. Returned: RC = 3, STAFResult = None

schris14 — Mon, 14 Nov 2022 21:31:34 GMT

I am attempting to run a test with 1 tile and including the collection of ESXtop data. All tests complete with no errors but I don't see a Score file and I see the error in the subject line when the program is collecting results.

Cancellation of submission cycle for December 27, 2022

jamesz08 — Fri, 11 Nov 2022 00:05:23 GMT

Due to end-of-the-year holidays, VMware will extend the VMmark review cycle that starts Dec 13, 2022 to four weeks (instead of the usual two weeks) and will cancel the review cycle that would normally have started Dec 27, 2022.

Here's are details of these changes:

Dec 13, 2022: Start of last VMmark review cycle for 2022. No change from usual schedule, but this cycle has an extended review period; results submitted during this cycle would not be published before Jan 10, 2023.
Dec 20, 2022: Last VMmark Review Panel meeting for 2022. Although this cycle's submissions have an extended review period, we encourage initial review comments to be completed before this meeting. (Effectively, the extended review period is intended to give submitters more time to address issues reported for this meeting.)
Dec 27, 2022: This VMmark review cycle cancelled.
Jan 03, 2023: This VMmark Review Panel meeting will occur as scheduled, if needed.
Jan 10. 2023: Earliest publication date for benchmark submissions received for the Dec 13, 2022 review cycle. All submissions received after the start of the Dec 13, 2022 review cycle will begin their review cycle on Jan 10, 2023.