1 Reply Latest reply on Jan 24, 2013 8:07 AM by foremanr

    vAppliance with virtual hardware version 8 and VMstudio 2.6

    abhiky Lurker

      Hi ,

       

      I am trying to build a vAppliance on RHEL6.0 with virtual hardware version 8 in VMstudio 2.6.

       

      I have editing the vmx-07 to vmx-08

       

       

      <Info>Virtual Hardware Requirements</Info>

      <System>

      <vssd:VirtualSystemType>vmx-08</vssd:VirtualSystemType>

      </System>

       

       

      The build fails with the following :

       

      root@xx194:/opt/vmware/www/ISV# studiocli -c -v -p /opt/vmware/var/lib/build/profiles/ABC_VM8.xml
      Using instance name: ABC_VM8.1
      Using build instance name: ABC_VM8.1
      VMware Studio Version - 2.6.0.0 Build 631426
      Description - VMware Studio 2.6.0.0
      Validating profile schema...
      Connecting to <vCenter> at <10.10.10.185> as <root>.
      Validating build profile's version...
      Validating the VM's version formatting...
      Validating the VM's basic memory requirements...
      Validating all file/directory names in profile...
      Validating the VM's usernames and passwords...
      Validating the VM's logo path...
      Validating the VM's disk configurations...
      Validating provisioning host's entry...
      Validating provisioning timers...
      Validating ApplicationPackages URL...
      Validating non-empty ISO path...
      Validating non-duplicate OS package elements...
      Validating provisioning engine restrictions...
      Validating provisioning engine connection...
      Scanning for conflicting VM on provisioning host.
      Validating the basic capabilities of provisioning engine...
      Use of uninitialized value in numeric ne (!=) at /opt/vmware/lib/build/VADK/Test.pm line 407.
      Use of uninitialized value in numeric ne (!=) at /opt/vmware/lib/build/VADK/Test.pm line 407.
      Use of uninitialized value in concatenation (.) or string at /opt/vmware/lib/build/VADK/Test.pm line 408.
      Warning: Unsupported Hardware Version:
      Validating network address' availability for provisioning...
      Validating available disk space...
      Preparing the OS installation files.
      Looking for /opt/vmware/www/ISV/ISO/rhel-server-6.0-x86_64-dvd.iso
      Checking application package repositories for packages to be installed...
      Creating package repositories...
      Creating the template vm.
      Use of uninitialized value in concatenation (.) or string at /opt/vmware/lib/build/VADK/Build.pm line 740.
      Transporting VM from Studio to provisioning host; this may take a few minutes...
      Warning: VM transporting failed! Error:
      Warning:
      Failure: Encountered a fatal build error!
      Cleaning up ...Cleaning up provisioning host...
      Checking if the 10.10.10.185 connection is still active...
      Checking if the 10.10.10.185 connection is still active...
      Removing transient VM from provisioning host.
      Warning: Failed to removed VM from data store
      Checking if the 10.10.10.185 connection is still active...
      Removing transient VM from provisioning host.
      Warning: Failed to removed VM from data store
      Cleaning up provisioning host...
      Removing temporary files.
      Build/Validation process has successfully aborted.

       

      adding an entry in /opt/vmware/lib/build/VADK/Test.pm for HWVER8 doesnt help

       

       

      /opt/vmware/www/ISV# studiocli -c -v -p /opt/vmware/var/lib/build/profiles/ABC_VM8.xml

      Using instance name: ABC_VM8.1

      Bareword "VADK::Constants::HWVER8" not allowed while "strict subs" in use at /opt/vmware/lib/build/VADK/Test.pm line 407.

      BEGIN not safe after errors--compilation aborted at /opt/vmware/lib/build/VADK/Test.pm line 923.

      Compilation failed in require at /opt/vmware/share/build/vabs.pl line 33.

       

       

      can anybody help me on this ?

      thanks

        • 1. Re: vAppliance with virtual hardware version 8 and VMstudio 2.6
          foremanr Novice

          I have not found any "standard" method of supporting VMware Hardware v8 ( or v9 ) with Studio 2.6.

           

          However, it is "relatively" easy to carry out the update after provisioning using a PostOutputCreation script.

           

          This is not as simple as just modifying the generated OVF, since the manifest file will also need to be udpated.  Failing to do this will cause the VMware OVF/OVA install wizard to fail due to a manifest checksum error.

           

          The code below is an example which performs the necessary changes - hope this helps:

           

                          <vadk:DistributionFormat vadk:format="ovf" vadk:enabled="true" vadk:filename="Utility_Services" vadk:directory="">
                                  <vadk:PostOutputCreation>
                                          <vadk:Script vadk:name="Virtual Hardware Fix" vadk:enabled="true">
                                          # Build specific script that will:
                                          #   Update any vmx-07 entry to vmx-08
                                          #   Rebuild the manifest
                                          # Move to the OVF directory
                                           cd `dirname $1`
                                          # Update Virtual Hardware Type
                                          sed -i -e &quot;s/vmx-07/vmx-08/&quot; $1
                                          # Rebuild the manifest file
                                          sha=`sha1sum $1 | awk &apos;{print $1}&apos;`
                                          ovf=$(basename $1)
                                          shafile=$(basename $1 .ovf).mf
                                          sed -i -e &quot;s/^SHA1($ovf)=.*/SHA1($ovf)=$sha/&quot; $shafile
                                          </vadk:Script>
                                  </vadk:PostOutputCreation>
                          </vadk:DistributionFormat>