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

Re: VMmark Run Tiles Target and Source Datastorages are the same

RebeccaG — Thu, 02 Nov 2023 21:56:35 GMT

Thank you Oporras for uploading your results files.

These are the VMmark storage infrastructure operations VMs: (quoted from VMmark3.properties file)

// SVmotion/Workloads = Standby

// XVmotion/Workloads = DS3WebA

Please make sure that these VMs for every tile are located on a different datastore from ones you specified in VMmark3.properties:

SVmotion/SVMotionLUNs = datastore1,datastore1

XVmotion/XVMotionLUNs = datastore1,datastore1

You can actually use the same datastore for all infrastructure operations as shown above, but they can also all be different.

The error you are seeing is because the workload VM in question is present on the same datastore as specified in SVMotionLUNs or XVMotionLUNs. It needs to be on a different datastore. This is why VMmark 3 requires at least 2 shared datastores across the SUT cluster.

In file Results_20231029035855_tile0, you have

SVmotion/SVMotionLUNs = DS_CLIPTEST01,DS_CLIPTEST02

You stated:

DS_CLIPTEST01 >
Standby0

Standby0 is on DS_CLIPTEST01, that is the source of the problem. Please migrate Standby0 to a different datastore or specify a different datastore in SVmotion/SVMotionLUNs.

In Results_20231029031758,

SVmotion/SVMotionLUNs = DS_AMSA_QA_DEV,DS_BASESWIN_QA_01

You stated:

DS_AMSA_QA_DEV >
Standby0

Same problem.

Also, I did not do a comprehensive review of your setup but I wanted to mention a couple of things I noticed:

1. Make sure you do not run VMmark on a production environment. There were many other VMs on your VMmark cluster. From the VMmark 3 User's Guide, "NOTE VMmark, and the benchmark hardware and software components (vCenter, ESXi, and the VMmark template, clients, workload virtual machines, systems under test, storage, etc.) must be used only in an isolated test environment. None of the benchmark hardware or software components should ever be connected to a production network or transitioned to a production environment." Among other things, when you run VMmark it will create terrible performance for any production applications and produce invalid VMmark 3 results.

2. You have specified the same cluster for both the VMmark 3 Client cluster and SUT cluster. These need to be separate clusters and physical machines. You can still run VMmark with this configuration, for example, for functional testing, but it will produce invalid performance results.

Thank you,

Rebecca

topic VMmark Run Tiles Target and Source Datastorages are the same in VMware VMmark™ Discussions

VMmark Run Tiles Target and Source Datastorages are the same

Re: VMmark Run Tiles Target and Source Datastorages are the same