VMware Cloud Community
dalo
Hot Shot
Hot Shot
Jump to solution

command works on windows, but fails on linux powercli (version issue)

I try to create a VM from a Linux Powercli and get a error. Same Powercli version on a Windows OS works.

If the user has Admin rights it works on Linux too.

I also tried it with the newest Powercli Version, same Issue.

Could someone help me with this?

Linux:

new-vm -name myvm -ResourcePool mypool -Location myfolder

new-vm : 2/8/19 2:02:18 PM      New-VM

At line:1 char:1

+ new-vm -name myvm  -ResourcePool mypool -Location myfolder...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [New-VM], VimException

+ FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.NewVM

Win10:

new-vm -name myvm -ResourcePool mypool -Location myfolder

Name                 PowerState Num CPUs MemoryGB

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

myvm         PoweredOff 1        0.250

PowerCLI Version

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

   VMware PowerCLI 10.1.0 build 8346946

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

Component Versions

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

   VMware Cis Core PowerCLI Component PowerCLI Component 10.1 build 8377811

   VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 10.1 build 8344055

Update: seems to be a issue with different versions, engineering is working on it

Reply
0 Kudos
44 Replies
LucD
Leadership
Leadership
Jump to solution

No, I'm on VC 6.7U1.
But I did test with the same privileges.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
dalo
Hot Shot
Hot Shot
Jump to solution

That's interesting, I tried now on a VC 6.7 too, and I get a exception too.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

I just checked again, and my test account had the System.Read privilege on the rootfolder, through a group membership.

So no, without System.Read on the rootfolder, it doesn't work.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
dalo
Hot Shot
Hot Shot
Jump to solution

Thank you for re-checking, so I'm not completly wrong with this.

I will update if I get some news from the SR.

Reply
0 Kudos
dalo
Hot Shot
Hot Shot
Jump to solution

Finally I got an answer from VMware Engineering, they will fix this Issue in 11.5:

"[SR]  Running new-vm cmdlet throws Core_BaseCmdlet_UnknownError after update to Powercli Version  11.1.0.

This happens because encryption feature has been added in 11.1. Now while preparing VmConfigSpec it tries to initialize CryptoManager which fails if user doesn't have appropriate permission to view CryptoManager. To fix this we will initialize CryptoManager on need basis."

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

Was it helpful? Let us know by completing this short survey here.

Reply
0 Kudos