New-VM cmdlet task stay at 38% for several minutes

[PavelV9]

Hi,

We have a problem with New-VM cmdlet.

The created Clone-VM task stay at 38% for several minutes. Than the task is finished.

Sometimes it is more than five minutes and PowerCLI Timeout Error appears.

Used version:

PowerCLI 11.1

vCenter/vSphere 6.7 or 6.5

Anyone have same experience?

Pavel

[PavelV9]

When I start same task from vSphere Web Client it continues without 38% "timeout".

[LucD]

You provide minimal information, which makes it hard to determine what could happen.
Are you cloning from a running VM?
Are you using guest OS customisation?

What kind of storage is the new VM being created on?

Did you try using the Verbose switch?
What are the related events saying?

Did you check the vpxd log?

Btw, you can eliminate the default timeout of 300 seconds, by using

Set-PowerCLIConfiguration -WebOperationTimeoutSeconds -1 -Confirm:$false

[LucD]

Did you already stop/start your PS/PowerCLI session?

[PavelV9]

The Cloning is from powered off VM.

No guest OS customization is used.

New VM is created on same VMFS datastore as source.

There are no usefull events or vpxd log records.

I will try Verbose switch.

[PavelV9]

Yes the problem persists for several weeks and also different users.

[LucD]

Sorry, haven't seen that before.
I would suggest you open a SR.

[PavelV9]

There is nothing interesting when I run the command with Verbose switch.

New-VM -VM $sourceVM -Name $newVM -Server $vCenter -ResourcePool $newResourcePool -Datastore $newDatastore -Location $newFolder -Confirm:$false -ErrorAction Stop -Verbose

Creates a new virtual machine with the specified parameters.

6/20/2019 10:01:59 AM     New-VM Finished execution

Name PowerState Num CPUs MemoryGB      

---- ---------- -------- --------      

test-12345... PoweredOff 4        8.000    

[LucD]

Indeed, the verbosity of most PowerCLI cmdlet is unfortunately rather sparse.