Hi,

How can we fix this issue?

2023-05-30 20:05:55 +0000: Deployment Started.
2023-05-30 20:06:03 +0000: [ERROR] VM Deployment Failed...
2023-05-30 20:06:03 +0000: VMs Preserved for Debugging Purpose, You Can Run /opt/automation/cleanup-vm.sh to Delete VMs Manually
2023-05-30 20:06:03 +0000: Testing Failed, For Details Please Find Logs in /opt/automation/logs
2023-05-30 20:06:03 +0000: Please Cancel And Re-Run The Testing

were you able to pass the pre-validation? please do so and it would help you to find out the root cause of this problem.

Hi Chen,

Stuck during

Validating the configuration...

We just stood up our first HCI stretched cluster. vSphere 8 OSA vSan on vxRail.

We have used HCIbench in the past but not for stretched. After testing, we plan on migrating a production stretched cluster to this new VxRail streched cluster.

Will HCIbench work with stretched design?

If HCIbench can be used for stretched testing, should we create a separate VM vlan network for testing and not use an existing vlan VM network in use on the other source production cluster?

Yes, HCIBench works on stretched cluster design.

i think it's best practice to have a dedicated vlan, but its ok to use existing vlan.

Same "save config" issue all others have. I really thought I would give 2.8.1 a shot, but it's easier and faster to run my own benchmark than this buggy fling.

Nice disaster this version 2.8.1
When it will be fixed ?
same issues like others
1. Cant save config
2. validate config ends with error - probably OS 32 bit
This host supports Intel VT-x, but Intel VT-x is disabled. Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting. (1) Verify that the BIOS/firmware settings enable Intel VT-x and disable 'trusted execution.' (2) Power-cycle the host if either of these BIOS/firmware settings have been changed. (3) Power-cycle the host if you have not done so since installing VMware ESX. (4) Update the host's BIOS/firmware to the latest version.
3. Easy run do not deploy vm evenly on each host . IE should be 4 hosts , 4 vms per host. DRS manual
4. Error updating options: InfluxDB Error: database not found: telegraf
5. Test on old version 2.6.1. vs 2.8.1
All of those workload above is configured with 50% compressible and 50% dedupable data for write operations.
fio-8vmdk-100ws-256k-0rdpct-0randompct-1threads
2.6.1
IOPS 7 415 Throughput(MB) 1853
2.8.1
IOPS 15551 Throughput(MB) 3887

Guys what version is most stable ? 2.6.1 ?

we will get them fixed
1. this can be resolved by the workaround provided below.
2. could you redo pre-validation and send all logs to vsanperformance@vmware.com?
3. are you testing against vSAN ESA or OSA? could you also send logs over?
4. where did you see this msg?
5. we dont see significant perf diff for OSA, for ESA, since the design is diff, we do see huge benefit while running testing with 50% comp ratio.

feel free to drop me email at vsanperformance@vmware.com, we will do our best to help.