SuperMicro E300

@User check your hosting connection

@Webster Webster changed those and doesn't help 😞

Not using PvDisk, can I have that set to 0 and leave the others as they are?

so basically I changed these and had like 1000 combinations in the past 2weeks

You are probably overwhelming your infrastructure. I did a XD project where no matter the values, the customer's infrastructure would only allow 6 VMs to be created or powered on at a time. The storage just couldn't handle the load.

It took me ~90hrs to provision 9000 full clones via MCS with a master image size of ~35GB

I'm on VSAN 6.6 AllFlash

2x 10G network (with usage at about 500-800GBps

VSAN is also bored

not sure who owns the limitation of concurrent tasks. Citrix or VMware (vSphere)

Then I have no explanation. Have you opened a support case wqith Citrix?

They're useless

First 5 tasks are sequential, the rest is in parallel

I've asked the TRM and after this thing, he'll probably get his ass kicked out

It's an MCS limitation

Ugh, the other way round

We've tested and asked with the Nutanix AHV plugin, Prism (our management interface) is distributed so in theory it's able to handle multiple streams of parallel tasks

Citrix MCS couldn't do it

But VSAN can't use VAAI right? It uses VVOLs?

https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2105091 "vSAN uses Atomic Test & Set (ATS) to communicate with physical disks. ATS is one of the vStorage APIs for Array Integration (VAAI) primitives controlled by the HardwareAcceleratedLocking setting."

That seems to say that VSAN does use VAAI

well, mcs doesn't do cloning. MCS does datastore disk copy via the vCenter sdk

Good to know @Webster Webster 🙂

The copy operation is done in a way that will Storage offload to be used by the hypervisor if the storage supports it. (VAAI/ODX)

anyhow, a bit dissapointed

and the cherry on top of it, is that the customer which agreed with the naming convention has a limitation in one of their mainframes... which has some kind of hardcoded security feature to allow just certain hostnames to access it.

...and it's checking the last 5 chars of the hostname. We have 2 sites in active-active and the char defining the location is included in the 7th char so we either accept 2 distinct VMs to access that stupid 90's mainframe, or just redeploy new VMs

I've found also this article and tested it but didn't find ANYONE smart enough at Citrix in the past day to tell me what it really does: https://support.citrix.com/article/CTX224456

#vdifun 🙂