1 Reply Latest reply on Mar 9, 2012 4:19 PM by asharpe

    vApp build with "invalid literal for int() with base 10: '' error

    e1a198 Lurker

      We would like to use VMware Studio 2.5 to bundle two VMs (both are Redhat 6.2 64-bit VMs) into a vApp. We have successfully imported these two VMs from ESX 4.1 into VMware Studio using "studiocli -I --name vm_name -vv" command. Howvere, when we start building a vApp from Studio based on these two imported VMs, we kept getting errors below.  Please help.

       

      Best regards,

      Evan

       

       

      24/02/2012 13:11:27 [info] Using build instance name: tcpgdev002.1
      24/02/2012 13:11:27 [info] Validating vApp profile: /opt/vmware/var/lib/build/vapp_profiles/tcpgdev002.xml
      24/02/2012 13:11:27 [info] Validating vApp profile against schema
      24/02/2012 13:11:27 [info] Validating that build profiles will generate OVF descriptors
      24/02/2012 13:11:27 [info] Validating build profile: /opt/vmware/var/lib/build/profiles/CentOS62Tomcat7023002.xml
      24/02/2012 13:11:27 [info] Using queued instance name: CentOS62Tomcat7023002.1
      24/02/2012 13:11:28 [info] Using build instance name: CentOS62Tomcat7023002.1
      24/02/2012 13:11:28 [info] VMware Studio Version - 2.5.0.0 Build 387333
      24/02/2012 13:11:28 [info] Description - VMware Studio 2.5.0.0
      24/02/2012 13:11:28 [info]
      24/02/2012 13:11:28 [info] Validating profile schema...
      24/02/2012 13:11:28 [info] Validating VM configuration and build settings.
      24/02/2012 13:11:28 [info] Connecting to <ESX> at <elai-hyperv.copyright.com> as <root>.
      24/02/2012 13:11:31 [info] Validating build profile's version...
      24/02/2012 13:11:31 [info] Validating the VM's version formatting...
      24/02/2012 13:11:31 [info] Validating the VM's basic memory requirements...
      24/02/2012 13:11:31 [info] Validating all file/directory names in profile...
      24/02/2012 13:11:31 [info] Validating the VM's usernames and passwords...
      24/02/2012 13:11:31 [info] Validating the VM's logo path...
      24/02/2012 13:11:31 [info] Validating the VM's disk configurations...
      24/02/2012  13:11:31 [info] Warning: The size of the disk named  "CentOS-Tomcat-64-B2-000001" is not large enough to accommodate the  partition sizes specified: only 40960MB are available, but based on the  partition sizes specified, 40971MB (40.02GB) are required to align these  partitions on cylinder boundaries.
      24/02/2012 13:11:31 [info] Validating provisioning host's entry...
      24/02/2012 13:11:31 [info] Validating provisioning timers...
      24/02/2012 13:11:31 [info] Validating ApplicationPackages URL...
      24/02/2012 13:11:31 [info] Validating management services' availability...
      24/02/2012 13:11:31 [info] Validating provisioning engine restrictions...
      24/02/2012 13:11:31 [info] Validating provisioning engine connection...
      24/02/2012 13:11:31 [info] Scanning for conflicting VM on provisioning host.
      24/02/2012 13:11:31 [info] Validating the basic capabilities of provisioning engine...
      24/02/2012 13:11:35 [info] Validating network address' availability for provisioning...
      24/02/2012 13:11:35 [info] Validating packages to be removed...
      24/02/2012 13:11:35 [info] Validating VAMI package source directory...
      24/02/2012 13:11:35 [info] Validating OS ISO path...
      24/02/2012 13:11:35 [info] The configuration and build settings passed all validation tests.
      24/02/2012 13:11:35 [info] Validation complete. All profiles validated successfully.
      24/02/2012 13:11:35 [info] Building child VM tcpgdev002.1_1 from /opt/vmware/var/lib/build/profiles/CentOS62Tomcat7023002.xml
      24/02/2012 13:11:37 [info] tcpgdev002.1_1: Warning: An operation is apparently already in progress, process ID: 17479
      24/02/2012 13:11:37 [info] tcpgdev002.1_1: Warning: The process owning the lock file does not seem to be running anymore.
      24/02/2012 13:11:37 [info] tcpgdev002.1_1: Warning: Attempting to remove stale lock file, and continue.
      24/02/2012 13:11:37 [info] tcpgdev002.1_1: Failure: invalid literal for int() with base 10: ''
      24/02/2012 13:11:37 [info] Failure: Build of child instance tcpgdev002.1_1 failed


        • 1. Re: vApp build with "invalid literal for int() with base 10: '' error
          asharpe Hot Shot
          VMware Employees

          The EVM feature of Studio (where you import a VM and Studio gainly tries to figure out the OS, the hardware, the architecture, the packages and various other things before trying to add more stuff to it) is rather problematic. Studio does the best it can, but you will have far more success if you can have Studio build the original VMs for you, instead of trying to point Studio at random VMs built somewhere else.