VMware Cloud Community
kbhasin
Contributor
Contributor

OVFTOOL --numberOfCpus Option

1)OVA is created by 4 CPUs

2) Now, to deploy OVA using for creating VM having CPUs then --numberOfCpus:VM1=2.

3) Still VM gets created with "4" CPU.

Note : I Observed similar behaviour in memory, VMName option as well.

Can anyone confirm if option is OK ?

Tags (1)
0 Kudos
3 Replies
AishR
VMware Employee
VMware Employee

0 Kudos
kbhasin
Contributor
Contributor

I had already checked this option form manual (regarding Syntax), but issue still not resolved.

I found a workaround to modify .vmx file (after OVA gets deploy) and then reload .vmx file for making it in effect.

However, thanks for your help anyway !

0 Kudos
Marakai1
Contributor
Contributor

Encountered the same issue;

As per the OVFTOOL documentation, parameters like

--numberOfCpus

or

--memorySize

take the VM ID, which can be found in the .ovf file in the

<ovf:VirtualSystem ovf:id="vm1">

element (disregarding that this isn't exactly an easy and convenient way to extract it so you can pass it to ovftool).

Having checked my OVF/OVA files, in all case the default of "vm" is set in that element.

However --numberOfCpus:vm=2 does absolutely nothing! The number set in the base OVF of 1 remains.

This is with OVFTOOL 4.2.0.

0 Kudos