<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities : All Content - VMware Studio</title>
    <link>http://communities.vmware.com/community/vmtn/vam/studio</link>
    <description>All Content in VMware Studio</description>
    <language>en</language>
    <pubDate>Wed, 25 Nov 2009 01:26:37 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-11-25T01:26:37Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Ubuntu 9.10 Server support on VMware Studio 2.0</title>
      <link>http://communities.vmware.com/docs/DOC-11379</link>
      <description>In order to add Ubuntu 9.10 Server to be supported under VMware Studio 2.0 you must add it to the supported OS profiles.&lt;br /&gt;
I hope this helps someone.&lt;br /&gt;
&lt;br /&gt;
#1 Copy the Ubuntu 9.10 Server CD ISO to /opt/ISO&lt;br /&gt;
&lt;br /&gt;
#2 Go to /opt/vmware/etc/build/templates/ubuntu and create directory “09” and indide "09" also create "10", so the full path now is /opt/vmware/etc/build/templates/ubuntu/09/10.&lt;br /&gt;
&lt;br /&gt;
#3 Copy the build_profile.xml from /opt/vmware/etc/build/templates/ubuntu/08/041/build_profile.xml to /opt/vmware/etc/build/templates/ubuntu/09/10/&lt;br /&gt;
&lt;br /&gt;
#4 Edit the /opt/vmware/etc/build/templates/ubuntu/09/10/build_profile.xml and change the location of the vadk:path= to match the location of your Ubuntu 9.10 Server CD ISO from step 1.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;vadk:ISO vadk:path="file:///opt/ISO/ubuntu-9.10-server-i386.iso"&lt;br /&gt;
&lt;br /&gt;
Change the line that contains md5sum="&lt;br /&gt;
&lt;br /&gt;
md5sum="55618ad5f180692f9dac20cbff352634" is the latest Ubuntu 9.10 Server ISO md5.&lt;br /&gt;
&lt;br /&gt;
Other lines to change:&lt;br /&gt;
&lt;br /&gt;
vadk:sourceDir="&lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/lib/build/include/ubuntu/09/10/"&lt;br /&gt;
&lt;br /&gt;
vadk:OSverMajor="9" vadk:OSverMinor="10"&lt;br /&gt;
&lt;p /&gt;
Regards,&lt;br /&gt;
&lt;br /&gt;
Paul Aviles&lt;br /&gt;
www.nickelnetworks.com</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">ubuntu</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">9.10</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">server</category>
      <pubDate>Wed, 25 Nov 2009 00:56:04 GMT</pubDate>
      <author>NickelNetworks</author>
      <guid>http://communities.vmware.com/docs/DOC-11379</guid>
      <dc:date>2009-11-25T00:56:04Z</dc:date>
      <clearspace:dateToText>17 hours, 11 minutes ago</clearspace:dateToText>
    </item>
    <item>
      <title>VMWare Studio 1.0 Appliance needs a reboot during firstboot script.</title>
      <link>http://communities.vmware.com/message/1422430</link>
      <description>You could just start the tomcat server from Vmware Studio provided firstboot and subsequentboot scripts. This way tomcat will run after your initialization script (if called from the firstboot script).&lt;br /&gt;
Won't that work?&lt;br /&gt;
&lt;br /&gt;
Vishwas</description>
      <pubDate>Fri, 20 Nov 2009 19:20:33 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1422430</guid>
      <dc:date>2009-11-20T19:20:33Z</dc:date>
      <clearspace:dateToText>4 days, 23 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>ERROR: Unable to parse vm customization options</title>
      <link>http://communities.vmware.com/message/1420456</link>
      <description>Probably an xml file that is needed for displaying information in the Blue Login screen is either corrupt or missing.&lt;br /&gt;
&lt;br /&gt;
Could you check if the following files are present and look like they have valid information, if they do, can you post these files: &lt;br /&gt;
/opt/vmware/share/htdocs/service/core/view-deploy.xml&lt;br /&gt;
/opt/vmware/var/lib/vami/update/data/info/manifest-installed.xml&lt;br /&gt;
&lt;br /&gt;
Also, to figure out what may cause this, &lt;br /&gt;
Did you install a special package, or modify any files during build of the VA? &lt;br /&gt;
Is the product name, application url, and version in the build profile valid strings (do they have special characters)?&lt;br /&gt;
&lt;br /&gt;
Vishwas</description>
      <pubDate>Wed, 18 Nov 2009 18:53:24 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1420456</guid>
      <dc:date>2009-11-18T18:53:24Z</dc:date>
      <clearspace:dateToText>6 days, 23 hours ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Guest type and Cannot configure the source image errors</title>
      <link>http://communities.vmware.com/message/1419166</link>
      <description>There are a set of OS names internal to the ESX product (for instance try creating a new VM using vSphere Client and specify the OS for it), some of the OSes are not present in this list Ex: Centos 5.3. As a result this OS name is mapped to the closest available OS name in that list.&lt;br /&gt;
&lt;br /&gt;
Newer releases of ESX will probably have Centos 5.3 listed.&lt;br /&gt;
&lt;br /&gt;
Vishwas</description>
      <pubDate>Tue, 17 Nov 2009 15:21:50 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1419166</guid>
      <dc:date>2009-11-17T15:21:50Z</dc:date>
      <clearspace:dateToText>1 week, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>What is the minimum licensed version of vSphere/ESX to run Studio?</title>
      <link>http://communities.vmware.com/message/1417084</link>
      <description>&lt;br /&gt;
To run/host the Studio 2.0 vm itself, the free license of vSphere would also work. To provision/build appliances using vSphere/VI:&lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;ESXi 4.0 and ESXi 3.5 U4 or later: a minimal of the vSphere Essentials license is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;ESXi 3.5 U3: free license of vSphere would work.&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
The minimal supported version of vSphere for running/hosting the Studio 2.0 vm itself is ESX 3.5 U3.&lt;br /&gt;
&lt;p /&gt;
Ref: &lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/studio/studio20/release_notes.html"&gt;http://www.vmware.com/support/developer/studio/studio20/release_notes.html&lt;/a&gt; &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Sat, 14 Nov 2009 00:08:50 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1417084</guid>
      <dc:date>2009-11-14T00:08:50Z</dc:date>
      <clearspace:dateToText>1 week, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Management Services customizations</title>
      <link>http://communities.vmware.com/message/1406429</link>
      <description>&lt;br /&gt;
Please look for "Adding a Linux Management Service" in Studio Developer Guide. (&lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/studio/studio20/studio_developer.pdf"&gt;http://www.vmware.com/support/developer/studio/studio20/studio_developer.pdf&lt;/a&gt;). &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
It is possible to accomplish what you are asking for,  you can use the lighttpd (webserver) to serve the webpage in the new tab and write a cgi file to run your command (lighttpd is already configured to work with python). &lt;br /&gt;
&lt;p /&gt;
You can create the Management Services by hand or use eclipse to create and build a service (Please see VMware Studio Plugin for Eclipse&amp;gt;Creating Management Services in Developer Guide)&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Please see the attached cgisample.tar that shows how to run a command and show the output. It also does http basic authentication. Please see  "Importing a Management Service" to see how to import and use the attached cgisample.tar&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Mon, 02 Nov 2009 18:41:17 GMT</pubDate>
      <author>sjalagam</author>
      <guid>http://communities.vmware.com/message/1406429</guid>
      <dc:date>2009-11-02T18:41:17Z</dc:date>
      <clearspace:dateToText>3 weeks, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>CentOS 5.4 support on VMware Studio 2.0</title>
      <link>http://communities.vmware.com/docs/DOC-11121</link>
      <description>In order to add CentOS 5.4 to be supported under VMware Studio 2.0 you must add it to the supported OS profiles.&lt;br /&gt;
I hope this helps someone.&lt;br /&gt;
&lt;br /&gt;
#1 Copy the DVD ISO to /opt/vmware/www/ISV/ISO/&lt;br /&gt;
&lt;br /&gt;
#2  Go to /opt/vmware/etc/build/templates/centos/5 and create directory “4” as the latest version can also add “4_x86_64”.&lt;br /&gt;
&lt;br /&gt;
#3 Create build_profile.xml as sample below. The latest md5sum must exist in the line that reads:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;vadk:ISO vadk:path="file:///opt/vmware/www/ISV/ISO/CentOS-5.4-i386-bin-DVD.iso" vadk:md5sum="071e18754c2fb066c526672f9aea0515" vadk:containFiles=""/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
So md5sum="071e18754c2fb066c526672f9aea0515" is the latest CentOS 5.4 DVD ISO md5.&lt;br /&gt;
&lt;br /&gt;
#4 Create build_profile.xml inside /opt/vmware/etc/build/templates/centos/5/4/&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ovf:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&lt;br /&gt;
 xsi:schemaLocation="http://schemas.dmtf.org/ovf/envelope/1 /opt/vmware/etc/build/schemas/vadk.xsd"&lt;br /&gt;
 xmlns:vadk="http://www.vmware.com/schema/vadk"&lt;br /&gt;
 xmlns:ovf="http://schemas.dmtf.org/ovf/envelope/1"&lt;br /&gt;
 xmlns:vssd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_VirtualSystemSettingData"&lt;br /&gt;
 xmlns:rasd="http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/CIM_ResourceAllocationSettingData"&lt;br /&gt;
 xmlns:vmw="http://www.vmware.com/schema/ovf"&lt;br /&gt;
 ovf:version="0.7.0"&lt;br /&gt;
 vadk:version="1.1"&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;References&amp;gt;&amp;lt;/References&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!--&lt;br /&gt;
        The Annotation element of the AnnotationSection_Type is the text&lt;br /&gt;
        that will be presented as the Description of the VM.&lt;br /&gt;
    --&amp;gt;&lt;br /&gt;
    &amp;lt;Section xsi:type="ovf:AnnotationSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;Annotation&amp;gt;&amp;lt;/Annotation&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="ovf:ProductSection_Type" ovf:required="false"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;VM ISV branding information&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;Product&amp;gt;CentOS Linux 5.4&amp;lt;/Product&amp;gt;&lt;br /&gt;
        &amp;lt;Vendor&amp;gt;Independent Software Vendor, Inc.&amp;lt;/Vendor&amp;gt;&lt;br /&gt;
        &amp;lt;!--&lt;br /&gt;
            Version is the actual product version in the&lt;br /&gt;
            form X.X.X.X where X is an unsigned 16-bit integer.&lt;br /&gt;
&lt;br /&gt;
            FullVersion is a descriptive version string&lt;br /&gt;
            including, for example, alpha or beta designations&lt;br /&gt;
            and other release criteria.&lt;br /&gt;
        --&amp;gt;&lt;br /&gt;
        &amp;lt;Version&amp;gt;1.0.0.0&amp;lt;/Version&amp;gt;&lt;br /&gt;
        &amp;lt;FullVersion&amp;gt;1.0.0.0 alpha&amp;lt;/FullVersion&amp;gt;&lt;br /&gt;
        &amp;lt;ProductUrl&amp;gt;&amp;lt;/ProductUrl&amp;gt;&lt;br /&gt;
        &amp;lt;VendorUrl&amp;gt;&amp;lt;/VendorUrl&amp;gt;&lt;br /&gt;
        &amp;lt;AppUrl&amp;gt;&lt;a class="jive-link-external" href="http://$"&gt;http://$&lt;/a&gt;{app.ip}/&amp;lt;/AppUrl&amp;gt;&lt;br /&gt;
        &amp;lt;Category&amp;gt;Application&amp;lt;/Category&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="vadk:ExtendedProductSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:VendorUUID&amp;gt;&amp;lt;/vadk:VendorUUID&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:ProductRID&amp;gt;&amp;lt;/vadk:ProductRID&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:AppUrlName&amp;gt;Application Home&amp;lt;/vadk:AppUrlName&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:Logo&amp;gt;&amp;lt;/vadk:Logo&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:LogoUrl&amp;gt;&amp;lt;/vadk:LogoUrl&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:WelcomeText&amp;gt;${app.name} - ${app.version}&lt;br /&gt;
&lt;br /&gt;
To manage this VM browse to ${vami.url}&lt;br /&gt;
&amp;lt;/vadk:WelcomeText&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="vadk:SSLCertificateSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:CommonName&amp;gt;Self-Signed by YourCompany, Inc.&amp;lt;/vadk:CommonName&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:OrganizationName&amp;gt;YourCompany, Inc.&amp;lt;/vadk:OrganizationName&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:OrganizationalUnitName&amp;gt;VM Division&amp;lt;/vadk:OrganizationalUnitName&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:CountryName&amp;gt;US&amp;lt;/vadk:CountryName&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="vadk:VAMISection_Type"&amp;gt;&lt;br /&gt;
         &amp;lt;Info&amp;gt;VAMI Specific Information&amp;lt;/Info&amp;gt;&lt;br /&gt;
         &amp;lt;vadk:Services&amp;gt;&lt;br /&gt;
             &amp;lt;vadk:Service vadk:name="core" vadk:version="2.0.0.0" vadk:tabOrder="0"/&amp;gt;&lt;br /&gt;
             &amp;lt;vadk:Service vadk:name="update" vadk:version="2.0.0.0" vadk:tabOrder="0"/&amp;gt;&lt;br /&gt;
             &amp;lt;vadk:Service vadk:name="system" vadk:version="2.0.0.0" vadk:tabOrder="1"/&amp;gt;&lt;br /&gt;
             &amp;lt;vadk:Service vadk:name="network" vadk:version="2.0.0.0" vadk:tabOrder="2"/&amp;gt;&lt;br /&gt;
         &amp;lt;/vadk:Services&amp;gt;&lt;br /&gt;
         &amp;lt;vadk:WebServer vadk:httpsPort="5480"/&amp;gt;&lt;br /&gt;
         &amp;lt;vadk:ViewCustomization&amp;gt;&lt;br /&gt;
             &amp;lt;vadk:FooterLeft&amp;gt;&amp;lt;!--Html for the footer left section, example ISV small logo --&amp;gt;&amp;lt;/vadk:FooterLeft&amp;gt;&lt;br /&gt;
             &amp;lt;vadk:FooterCopyright&amp;gt;&amp;lt;!--Html for footer middle section, ISV copyright section.--&amp;gt;&amp;lt;/vadk:FooterCopyright&amp;gt;&lt;br /&gt;
         &amp;lt;/vadk:ViewCustomization&amp;gt;&lt;br /&gt;
         &amp;lt;vadk:ShowEULA&amp;gt;true&amp;lt;/vadk:ShowEULA&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
    &amp;lt;Section xsi:type="vadk:ApplicationSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:VMXFilename&amp;gt;VM.vmx&amp;lt;/vadk:VMXFilename&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:DistributionFormat vadk:format="ovf" vadk:filename="VM" vadk:directory="VM"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:ApplicationPackages&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://"&gt;http://&lt;/a&gt;&lt;a class="jive-link-external" href="http://VADK.localIP"&gt;http://VADK.localIP&lt;/a&gt;/ISV/appliancePackages&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://"&gt;http://&lt;/a&gt;&lt;a class="jive-link-external" href="http://VADK.localIP"&gt;http://VADK.localIP&lt;/a&gt;/vmware-open-vm-tools/centos/5/3&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:ApplicationPackages&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:OSPackages&amp;gt;    &amp;lt;!-- Additional OS packages needed by the ISV's application --&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="openssh-server"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="openssh-clients"/&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:OSPackages&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:BootActions&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:FirstBoot&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
#Un comment to send the output of this script to a logfile&lt;br /&gt;
#exec &amp;gt; /opt/vmware/var/log/firstboot 2&amp;gt;&amp;amp;1&lt;br /&gt;
&lt;br /&gt;
echo This script is executed on first boot only.&lt;br /&gt;
&lt;br /&gt;
#Un comment to run subsequent boot script after first boot&lt;br /&gt;
#/opt/vmware/etc/isv/subsequentboot&lt;br /&gt;
            &amp;lt;/vadk:FirstBoot&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:SubsequentBoot&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
#Un comment to send the output of this script to a logfile&lt;br /&gt;
#exec &amp;gt; /opt/vmware/var/log/subsequentboot 2&amp;gt;&amp;amp;1&lt;br /&gt;
&lt;br /&gt;
echo This script is executed on all boots, except the first one.&lt;br /&gt;
            &amp;lt;/vadk:SubsequentBoot&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:BootActions&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:Users&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:User vadk:username="root" vadk:password="" vadk:passwordFormat="plaintext"/&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:Users&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
    &amp;lt;Section xsi:type="vadk:IpAssignmentSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;Supported IP assignment schemes&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;vmw:IpAssignmentSection&lt;br /&gt;
            ovf:required="false" vmw:protocols="IPv4" vmw:schemes="ovfenv,dhcp"&amp;gt;&lt;br /&gt;
            &amp;lt;Info&amp;gt;Supported IP assignment schemes&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;/vmw:IpAssignmentSection&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="vadk:PropertySection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info/&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="vadk:AnyOVFSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&lt;br /&gt;
            Unknown OVF elements in this element will be passed directly&lt;br /&gt;
            to the OVF output descriptor without interpretation&lt;br /&gt;
        &amp;lt;/Info&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
    &amp;lt;Section xsi:type="vadk:UpdateSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:Repository vadk:url="" vadk:username=""&lt;br /&gt;
            vadk:password="" vadk:passwordFormat="plaintext"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
        &amp;lt;vadk:RepositoryStagingServer vadk:hostname=""&lt;br /&gt;
            vadk:fileLogin="root" vadk:filePassword=""&lt;br /&gt;
            vadk:filePasswordFormat="plaintext" vadk:fileProto="scp"&lt;br /&gt;
            vadk:filePath="/tmp"/&amp;gt;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:Info&amp;gt;&amp;lt;/vadk:Info&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
        &amp;lt;vadk:RepositoryExport vadk:format="zip"&lt;br /&gt;
            vadk:filename="VADK_Update"/&amp;gt;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:PreInstallShellScript&amp;gt;#!/bin/sh&lt;br /&gt;
#Sample pre install update script&lt;br /&gt;
#This script will be executed with the following arguments:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;$1 - version of VM before update&lt;/li&gt;
&lt;li&gt;$2 - version of VM trying to be installed&lt;/li&gt;
&lt;/ol&gt;
echo "Installing update from version $1 to version $2"&lt;br /&gt;
&lt;br /&gt;
#exit with value of 0 to allow update to continue&lt;br /&gt;
exit 0&lt;br /&gt;
        &amp;lt;/vadk:PreInstallShellScript&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:PostInstallShellScript&amp;gt;#!/bin/sh&lt;br /&gt;
#Sample post install update script&lt;br /&gt;
#This script will be executed with the following arguments:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;$1 - version of VM before update&lt;/li&gt;
&lt;li&gt;$2 - version of VM trying to be installed&lt;/li&gt;
&lt;li&gt;$3 - status of update process&lt;/li&gt;
&lt;/ol&gt;
#&lt;br /&gt;
#The Status in $3 will indicate to success of failure of the update:&lt;br /&gt;
&lt;ol&gt;
&lt;li&gt;0 - all update steps are successful&lt;/li&gt;
&lt;li&gt;1 - pre install script failed, package test and installation skipped&lt;/li&gt;
&lt;li&gt;2 - pre install success, package test failed, installation skipped&lt;/li&gt;
&lt;li&gt;4 - pre install and package test success, package installation failed&lt;/li&gt;
&lt;/ol&gt;
#&lt;br /&gt;
#A Status of 2 is likely caused by a package dependency conflict.  A Status of 4&lt;br /&gt;
#is likely caused by a failed package install script.&lt;br /&gt;
&lt;br /&gt;
if &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=2815&amp;subject=+%243+-eq+0+"&gt; $3 -eq 0 &lt;/a&gt;; then&lt;br /&gt;
  echo "Finished installing version $2"&lt;br /&gt;
else&lt;br /&gt;
  echo "Failed with status of $3 while installing version $2"&lt;br /&gt;
  echo "VM version is still $1"&lt;br /&gt;
fi&lt;br /&gt;
&lt;br /&gt;
#Exit with a value of 0 to allow the VM version to be changed and set the final&lt;br /&gt;
#update status to success.&lt;br /&gt;
exit 0&lt;br /&gt;
        &amp;lt;/vadk:PostInstallShellScript&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!-- Defined by  CIM_OperatingSystem.OsType --&amp;gt;&lt;br /&gt;
    &amp;lt;Section ovf:id="88" ovf:version="5" xsi:type="ovf:OperatingSystemSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;Guest Operating System&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;Description&amp;gt;CentOS Linux 5.4&amp;lt;/Description&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="ovf:VirtualHardwareSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;Virtual Hardware Requirements&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;System&amp;gt;&lt;br /&gt;
            &amp;lt;vssd:VirtualSystemType&amp;gt;vmx-04&amp;lt;/vssd:VirtualSystemType&amp;gt;&lt;br /&gt;
        &amp;lt;/System&amp;gt;&lt;br /&gt;
        &amp;lt;Item&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Caption&amp;gt;1 virtual CPU&amp;lt;/rasd:Caption&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Description&amp;gt;Number of virtual CPUs&amp;lt;/rasd:Description&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:InstanceId&amp;gt;1&amp;lt;/rasd:InstanceId&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceType&amp;gt;3&amp;lt;/rasd:ResourceType&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:VirtualQuantity&amp;gt;1&amp;lt;/rasd:VirtualQuantity&amp;gt;&lt;br /&gt;
        &amp;lt;/Item&amp;gt;&lt;br /&gt;
        &amp;lt;Item&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:AllocationUnits&amp;gt;MegaBytes&amp;lt;/rasd:AllocationUnits&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Caption&amp;gt;512 MB of memory&amp;lt;/rasd:Caption&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Description&amp;gt;Memory Size&amp;lt;/rasd:Description&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:InstanceId&amp;gt;2&amp;lt;/rasd:InstanceId&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceType&amp;gt;4&amp;lt;/rasd:ResourceType&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:VirtualQuantity&amp;gt;512&amp;lt;/rasd:VirtualQuantity&amp;gt;&lt;br /&gt;
        &amp;lt;/Item&amp;gt;&lt;br /&gt;
        &amp;lt;Item&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:AutomaticAllocation&amp;gt;true&amp;lt;/rasd:AutomaticAllocation&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Caption&amp;gt;Ethernet adapter on vmnet&amp;lt;/rasd:Caption&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Connection&amp;gt;Network 1&amp;lt;/rasd:Connection&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:InstanceId&amp;gt;3&amp;lt;/rasd:InstanceId&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceSubType&amp;gt;PCNet32&amp;lt;/rasd:ResourceSubType&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceType&amp;gt;10&amp;lt;/rasd:ResourceType&amp;gt;&lt;br /&gt;
        &amp;lt;/Item&amp;gt;&lt;br /&gt;
        &amp;lt;Item&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:BusNumber&amp;gt;0&amp;lt;/rasd:BusNumber&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Caption&amp;gt;SCSI Controller 0 - LSI Logic&amp;lt;/rasd:Caption&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:InstanceId&amp;gt;4&amp;lt;/rasd:InstanceId&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceSubType&amp;gt;lsilogic&amp;lt;/rasd:ResourceSubType&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceType&amp;gt;6&amp;lt;/rasd:ResourceType&amp;gt;&lt;br /&gt;
        &amp;lt;/Item&amp;gt;&lt;br /&gt;
        &amp;lt;Item&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:AddressOnParent&amp;gt;0&amp;lt;/rasd:AddressOnParent&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Caption&amp;gt;Harddisk 0&amp;lt;/rasd:Caption&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:HostResource&amp;gt;/disk/system&amp;lt;/rasd:HostResource&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:InstanceId&amp;gt;5&amp;lt;/rasd:InstanceId&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:Parent&amp;gt;4&amp;lt;/rasd:Parent&amp;gt;&lt;br /&gt;
            &amp;lt;rasd:ResourceType&amp;gt;17&amp;lt;/rasd:ResourceType&amp;gt;&lt;br /&gt;
        &amp;lt;/Item&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
    &amp;lt;Section xsi:type="vadk:JEOSSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:BootArgs&amp;gt;&lt;br /&gt;
append ks=&lt;a class="jive-link-external" href="http://VADK.unattendedCfgURL"&gt;http://VADK.unattendedCfgURL&lt;/a&gt; ksdevice=eth0&lt;br /&gt;
method=http://&lt;a class="jive-link-external" href="http://VADK.localIP"&gt;http://VADK.localIP&lt;/a&gt;/build/&lt;a class="jive-link-external" href="http://VADK.buildID"&gt;http://VADK.buildID&lt;/a&gt;/&lt;br /&gt;
initrd=initrd.img&lt;br /&gt;
ip=&lt;a class="jive-link-external" href="http://VADK.ip"&gt;http://VADK.ip&lt;/a&gt; netmask=&lt;a class="jive-link-external" href="http://VADK.nm"&gt;http://VADK.nm&lt;/a&gt; gateway=&lt;a class="jive-link-external" href="http://VADK.gw"&gt;http://VADK.gw&lt;/a&gt; dns=&lt;a class="jive-link-external" href="http://VADK.ns1"&gt;http://VADK.ns1&lt;/a&gt;&lt;br /&gt;
lang=en_US keymap=us ramdisk_size=100000&lt;br /&gt;
divider=10 clocksource=acpi_pm&lt;br /&gt;
        &amp;lt;/vadk:BootArgs&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:BootArgsDHCP&amp;gt;&lt;br /&gt;
append ks=&lt;a class="jive-link-external" href="http://VADK.unattendedCfgURL"&gt;http://VADK.unattendedCfgURL&lt;/a&gt;&lt;br /&gt;
ksdevice=eth0 ip=dhcp&lt;br /&gt;
method=http://&lt;a class="jive-link-external" href="http://VADK.localIP"&gt;http://VADK.localIP&lt;/a&gt;/build/&lt;a class="jive-link-external" href="http://VADK.buildID"&gt;http://VADK.buildID&lt;/a&gt;/&lt;br /&gt;
initrd=initrd.img&lt;br /&gt;
lang=en_US keymap=us ramdisk_size=100000&lt;br /&gt;
divider=10 clocksource=acpi_pm&lt;br /&gt;
        &amp;lt;/vadk:BootArgsDHCP&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:BootFiles vadk:relPath="images/pxeboot" vadk:kernel="vmlinuz"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:UnattendedInstallTemplate&amp;gt;&lt;br /&gt;
            &lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/etc/build/templates/redhat/5/redhat5.xsl&lt;br /&gt;
        &amp;lt;/vadk:UnattendedInstallTemplate&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:PreInstallScript&lt;br /&gt;
            vadk:template="&lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/etc/build/templates/centos/5/preinstall.xsl"&lt;br /&gt;
            vadk:output="&lt;a class="jive-link-external" href="http://VADK.stageDir"&gt;http://VADK.stageDir&lt;/a&gt;/preinstall.sh"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:EVMInstallScript vadk:template="&lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/etc/build/templates/redhat/5/evm_install.xsl"/&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:EVMConfigScript vadk:template="&lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/etc/build/templates/redhat/5/evm_config.xsl"/&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:EVMCleanScript vadk:template="&lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/etc/build/templates/redhat/5/evm_clean.xsl"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:PostScriptRepoList&amp;gt;RepositoryList&amp;lt;/vadk:PostScriptRepoList&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:PostScriptPackageList&amp;gt;PackageList&amp;lt;/vadk:PostScriptPackageList&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:VADKPackages vadk:path="http://&lt;a class="jive-link-external" href="http://VADK.localIP"&gt;http://VADK.localIP&lt;/a&gt;/build/&lt;a class="jive-link-external" href="http://VADK.buildID"&gt;http://VADK.buildID&lt;/a&gt;/repo/vadkPackages/"&lt;br /&gt;
            vadk:sourceDir="&lt;a class="jive-link-external" href="http://VADK.vadkRoot"&gt;http://VADK.vadkRoot&lt;/a&gt;/lib/build/include/centos/5/3/"&lt;br /&gt;
            vadk:targetDir="&lt;a class="jive-link-external" href="http://VADK.stageDir"&gt;http://VADK.stageDir&lt;/a&gt;/repo/vadkPackages/"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:ISO vadk:path="file:///opt/vmware/www/ISV/ISO/CentOS-5.4-i386-bin-DVD.iso"&lt;br /&gt;
                vadk:md5sum="071e18754c2fb066c526672f9aea0515" vadk:containFiles=""/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:Distribution vadk:vendor="CentOS" vadk:OSverMajor="5" vadk:OSverMinor="3"&lt;br /&gt;
                            vadk:arch="i386" vadk:smp="1" vadk:packageFormat="rpm"&lt;br /&gt;
                            vadk:packageManager="yum" vadk:packageRepoDir="packageRepoDir"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:OSPackages&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="bash"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="bind-utils"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="boost"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="chkconfig"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="coreutils"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="curl"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="dhclient"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="gawk"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="grep"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="initscripts"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="iptables"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="libicu"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="libxml2-python"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="module-init-tools"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="ncurses"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="net-tools"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="openssl"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="passwd"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="rpm"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="procps"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="sed"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="sudo"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="sysklogd"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="SysVinit"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="util-linux"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="wget"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="which"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="yum"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Package vadk:name="yum-metadata-parser"/&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:OSPackages&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
    &amp;lt;Section xsi:type="vadk:BuildSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:ProvisioningSettings&amp;gt;  &amp;lt;!-- OS settings for the VM being provisioned --&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:NetworkConnection&amp;gt;&amp;lt;/vadk:NetworkConnection&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:NetworkType&amp;gt;dhcp&amp;lt;/vadk:NetworkType&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:IP&amp;gt;&amp;lt;/vadk:IP&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Netmask&amp;gt;&amp;lt;/vadk:Netmask&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:Gateway&amp;gt;&amp;lt;/vadk:Gateway&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:DNS1&amp;gt;&amp;lt;/vadk:DNS1&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:DNS2&amp;gt;&amp;lt;/vadk:DNS2&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:ProvisioningSettings&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;!--&lt;br /&gt;
        vadk:path maps to the Upload Path field in the web UI. This is a local directory path on the&lt;br /&gt;
        physical box where the VMware Server is running. This location will be used to store&lt;br /&gt;
        the provisioning virtual machine for building the VM.&lt;br /&gt;
&lt;br /&gt;
        vadk:filePath maps to the Registration Path field in the web UI. This is a path used by&lt;br /&gt;
        VMware Studio for uploading the provisioning virtual machine to the Upload Path mentioned above.&lt;br /&gt;
&lt;br /&gt;
        The Registration Path and the Upload Path above must refer to same physical directory.&lt;br /&gt;
        --&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:ProvisioningEngine&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:VmhostLan vadk:hostname="" vadk:port="" vadk:hostOS=""&lt;br /&gt;
                vadk:login="root" vadk:password="" vadk:passwordFormat="plaintext"&lt;br /&gt;
                vadk:path="/tmp" vadk:datastore=""&lt;br /&gt;
                vadk:datacenter="" vadk:managedESX=""&lt;br /&gt;
                vadk:resourcePool=""&lt;br /&gt;
                vadk:fileLogin="root" vadk:filePassword="" vadk:filePasswordFormat="plaintext"&lt;br /&gt;
                vadk:fileProto="scp" vadk:filePath="/tmp"&lt;br /&gt;
                vadk:vmrunPath="" vadk:wsXDisplay="&lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/shocked.gif" alt=":0" /&gt;.0"/&amp;gt;&lt;br /&gt;
            &amp;lt;vadk:VmhostProduct vadk:name="" vadk:majorVersion=""/&amp;gt;&lt;br /&gt;
        &amp;lt;/vadk:ProvisioningEngine&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;!-- all timeouts are in seconds    --&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:ProvisioningTimeouts vadk:boot="600" vadk:poweroff="25" vadk:hang="7200" vadk:sshWaitTime="120" vadk:scpOperationTime="300" vadk:scpAutoYesWaitTime="2" vadk:systemCmdWaitTime="30" vadk:systemCmdMaxTime="7200"/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:PreInstallShellScript&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
echo pre-install shell code&lt;br /&gt;
        &amp;lt;/vadk:PreInstallShellScript&amp;gt;&lt;br /&gt;
&lt;br /&gt;
        &amp;lt;vadk:PostInstallShellScript&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
echo post-install shell code&lt;br /&gt;
        &amp;lt;/vadk:PostInstallShellScript&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- example of existing vm provisioning:&lt;br /&gt;
        &amp;lt;vadk:ExistingVm vadk:filepath="/opt/vmware/www/build/exampleBuildId/exports/zip/exampleVM.zip" vadk:buildid="exampleBuildId" vadk:isAgentInstalled="false" /&amp;gt;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;!--&lt;br /&gt;
        The combination of a network device in ovf:VirtualHardwareSection_Type&lt;br /&gt;
        an entry in ovf:NetworkSection_Type describe a network.&lt;br /&gt;
    --&amp;gt;&lt;br /&gt;
    &amp;lt;Section xsi:type="ovf:NetworkSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;List of logical networks used in the package&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;Network ovf:name="Network 1" ovf:id="vmnet"&amp;gt;&lt;br /&gt;
            &amp;lt;Description&amp;gt;Network 1&amp;lt;/Description&amp;gt;&lt;br /&gt;
        &amp;lt;/Network&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
    &amp;lt;!--&lt;br /&gt;
        The combination of a disk device in ovf:VirtualHardwareSection_Type,&lt;br /&gt;
        an entry in ovf:DiskSection_Type, and optionally entries in&lt;br /&gt;
        vadk:DiskPartitionSection_Type describe a disk, referenced by ovf:diskId&lt;br /&gt;
    --&amp;gt;&lt;br /&gt;
    &amp;lt;Section xsi:type="ovf:DiskSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;List of the virtual disks and partitions needed&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;Disk ovf:diskId="system" ovf:capacity="2048"&lt;br /&gt;
              ovf:capacityAllocationUnits="MegaBytes"&lt;br /&gt;
              ovf:fileRef="system.vmdk"&lt;br /&gt;
              ovf:format="http://www.vmware.com/specifications/vmdk.html#sparse"&lt;br /&gt;
        /&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;Section xsi:type="vadk:DiskPartitionSection_Type"&amp;gt;&lt;br /&gt;
        &amp;lt;Info&amp;gt;&amp;lt;/Info&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:Partition vadk:diskId="system" vadk:bootable="1" vadk:fs="ext3" vadk:mount="/boot" vadk:size="128"/&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:Partition vadk:diskId="system" vadk:bootable="0" vadk:fs="ext3" vadk:mount="/" vadk:size="grow"/&amp;gt;&lt;br /&gt;
        &amp;lt;vadk:Partition vadk:diskId="system" vadk:bootable="0" vadk:fs="swap" vadk:mount="" vadk:size="128"/&amp;gt;&lt;br /&gt;
    &amp;lt;/Section&amp;gt;&lt;br /&gt;
&lt;p /&gt;
&amp;lt;/ovf:Envelope&amp;gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">centos</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">5.4</category>
      <pubDate>Sun, 01 Nov 2009 04:22:02 GMT</pubDate>
      <author>NickelNetworks</author>
      <guid>http://communities.vmware.com/docs/DOC-11121</guid>
      <dc:date>2009-11-01T04:22:02Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
    </item>
    <item>
      <title>Simple Q: Can I create Windows XP (x64) Virtual Appliance w VMWare Studio?</title>
      <link>http://communities.vmware.com/message/1405216</link>
      <description>Yes - our appication depends on Windows XP 64-Bit as and OS. Therefore it is necessary to build a Windows XP 64Bit Virtual Appliance. I would like to use Vmware Studio to do this, but would be open to doing it with whatever tools or add-ons are necessary. Do you know of any?</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">create</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">windows</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">xp</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliances</category>
      <pubDate>Sat, 31 Oct 2009 19:50:09 GMT</pubDate>
      <author>mattyche</author>
      <guid>http://communities.vmware.com/message/1405216</guid>
      <dc:date>2009-10-31T19:50:09Z</dc:date>
      <clearspace:dateToText>3 weeks, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Error installing the Eclipse plugin</title>
      <link>http://communities.vmware.com/message/1404145</link>
      <description>&lt;br /&gt;
Thank you! &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
This is a lab environment and had no access to internet. I did not know it needed to download the dependencies, I thought they were included on the VMware Studio appliance. I gave the VM internet access and everything went fine after that. Thanks again.</description>
      <pubDate>Fri, 30 Oct 2009 13:31:50 GMT</pubDate>
      <author>GoVikes</author>
      <guid>http://communities.vmware.com/message/1404145</guid>
      <dc:date>2009-10-30T13:31:50Z</dc:date>
      <clearspace:dateToText>3 weeks, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>International character support</title>
      <link>http://communities.vmware.com/message/1395534</link>
      <description>&lt;div class="jive-quote"&gt;The word "Anschließend" is not properly displayed in the Welcome Text box.&lt;/div&gt;
&lt;br /&gt;
The answer is hidden somewhere in system environment variable. Because when I set the ENV variable to german in /etc/bashrc &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=export+LANG%3Dgerman"&gt;export LANG=german&lt;/a&gt;, I am able to paste "Anschließend" word properly in the file otherwise cryptic value is pasted in the file.</description>
      <pubDate>Thu, 22 Oct 2009 06:06:11 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1395534</guid>
      <dc:date>2009-10-22T06:06:11Z</dc:date>
      <clearspace:dateToText>1 month, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>IP address not set at VM boot</title>
      <link>http://communities.vmware.com/message/1394956</link>
      <description>&lt;br /&gt;
Thanks &lt;a class="jive-link-profile" href="http://communities.vmware.com/people/chorgeas"&gt;chorgeas&lt;/a&gt;.&lt;br /&gt;
&lt;p /&gt;
That should do the trick for me.</description>
      <pubDate>Wed, 21 Oct 2009 15:59:12 GMT</pubDate>
      <author>blainek</author>
      <guid>http://communities.vmware.com/message/1394956</guid>
      <dc:date>2009-10-21T15:59:12Z</dc:date>
      <clearspace:dateToText>1 month, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Is there a way to reduce VMWare Tools dependencies?</title>
      <link>http://communities.vmware.com/message/1394304</link>
      <description>You may try removing all the dependencies of redhat-lsb as a start; vmware-open-vm-tools needs redhat-lsb but probably not any (or most) of its dependencies. You would need to experiment a little bit. As for the command to remove the pkgs, yes that what I'd use.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware_studio_2.0</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware_tools</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">yum</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">dependencies</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">centos</category>
      <pubDate>Wed, 21 Oct 2009 00:26:10 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1394304</guid>
      <dc:date>2009-10-21T00:26:10Z</dc:date>
      <clearspace:dateToText>1 month, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Studio bug? Disk capacity truncated to two digits</title>
      <link>http://communities.vmware.com/message/1393103</link>
      <description>This unfortunately does look like a profile-display bug that needs to be addressed! Thnx for reporting it and sorry for the inconvenience! In the mean time, given the profile does carry the correct disk capacity value as from an intended save, pls disregard the display error and proceed with the appliance building. Bottom line, remember to verify the disk capacity value(s) directly from the xml file (/opt/vmware/var/lib/build/profiles/&amp;lt;profile&amp;gt;.xml) before building your appliances.</description>
      <pubDate>Mon, 19 Oct 2009 20:50:21 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1393103</guid>
      <dc:date>2009-10-19T20:50:21Z</dc:date>
      <clearspace:dateToText>1 month, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Error validating VM's Disk configuration</title>
      <link>http://communities.vmware.com/message/1393021</link>
      <description>Great! Thnx for the updates!</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmdisk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vm_disk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">validate_profile</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">build_profile</category>
      <pubDate>Mon, 19 Oct 2009 19:38:07 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1393021</guid>
      <dc:date>2009-10-19T19:38:07Z</dc:date>
      <clearspace:dateToText>1 month, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>ESXi 4.0 as a build server doesn't work</title>
      <link>http://communities.vmware.com/message/1392003</link>
      <description>The vSphere Essentials licenses would allow your ESX/ESXi to work with Studio 2.0. FWIW about VMware licenses check out&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://blogs.vmware.com/esxi/2009/06/esxi-vs-esx-a-comparison-of-features.html"&gt;http://blogs.vmware.com/esxi/2009/06/esxi-vs-esx-a-comparison-of-features.html&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">esxi</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">esxi4</category>
      <pubDate>Sun, 18 Oct 2009 02:49:12 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1392003</guid>
      <dc:date>2009-10-18T02:49:12Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Studio: Unable to connect to server. Please try again.</title>
      <link>http://communities.vmware.com/message/1390140</link>
      <description>Please try following things.&lt;br /&gt;
&lt;br /&gt;
1. Check the port number in browser i.e. &lt;a class="jive-link-external" href="https://VMwareStudioIP:5480/"&gt;https://VMwareStudioIP:5480/&lt;/a&gt;&lt;br /&gt;
2. User username as root and password what you have set in first boot of VMware Studio.&lt;br /&gt;
3. Try to ping your host machine from VMware Studio VA and vice versa.&lt;br /&gt;
4. If your VMware Studio is on hosted class product, &lt;br /&gt;
      a. Set Ethernet Adaptor to Bridge and select ‘Connect at power on’ option in Virtual Machine settings.&lt;br /&gt;
      b. Disable host machine firewall.</description>
      <pubDate>Thu, 15 Oct 2009 10:22:34 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1390140</guid>
      <dc:date>2009-10-15T10:22:34Z</dc:date>
      <clearspace:dateToText>1 month, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Cannot create Ubuntu profile</title>
      <link>http://communities.vmware.com/message/1384279</link>
      <description>My suggestions are,&lt;br /&gt;
&lt;br /&gt;
1. As mentioned in studio_developer.pdf, you can download the required ISO's from &lt;a class="jive-link-external" href="http://cdimage.ubuntu.com/releases/"&gt;http://cdimage.ubuntu.com/releases/&lt;/a&gt; location.&lt;br /&gt;
&lt;br /&gt;
studio_developer.pdf link = &lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/studio/studio20/studio_developer.pdf"&gt;http://www.vmware.com/support/developer/studio/studio20/studio_developer.pdf&lt;/a&gt;&lt;br /&gt;
Section = "Operating System ISO Image"&lt;br /&gt;
&lt;br /&gt;
2. After downloading the ISO file, copy it in /opt/vmware/www/ISV/ISO/ folder.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware_studio_2.0</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">ubuntu_8_04</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vm_profile</category>
      <pubDate>Thu, 08 Oct 2009 03:55:39 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1384279</guid>
      <dc:date>2009-10-08T03:55:39Z</dc:date>
      <clearspace:dateToText>1 month, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Validate or Build failing to find application packages</title>
      <link>http://communities.vmware.com/message/1378225</link>
      <description>&lt;br /&gt;
That was exactly it. I reconfigured and set the proxy config to n and validation worked immediately. I'll have to write that into my setup list.&lt;br /&gt;
&lt;p /&gt;
Thanks for the help...back on track again.</description>
      <pubDate>Wed, 30 Sep 2009 19:08:23 GMT</pubDate>
      <author>blainek</author>
      <guid>http://communities.vmware.com/message/1378225</guid>
      <dc:date>2009-09-30T19:08:23Z</dc:date>
      <clearspace:dateToText>1 month, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Doubts in Using VMware Studio..</title>
      <link>http://communities.vmware.com/message/1375919</link>
      <description>Sorry, VMware Studio doesn't do that, and you cannot convert a VM into a OS ISO as far as I know.</description>
      <pubDate>Mon, 28 Sep 2009 17:51:49 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1375919</guid>
      <dc:date>2009-09-28T17:51:49Z</dc:date>
      <clearspace:dateToText>1 month, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Connection Wizard to ESX4 machine fails with "Connection refused"</title>
      <link>http://communities.vmware.com/message/1374853</link>
      <description>&lt;br /&gt;
It's amazing what some time and space away from a problem will do. I returned to the problem tonight to try out these suggestions and when I looked at the settings again, I realized I had used the wrong IP address in the connection host - I had put in the address for the VM into the field for the ESX host. No wonder the connection failed. &lt;br /&gt;
&lt;p /&gt;
All my fault, sorry for taking up your time. The connection wizard worked once I put in the correct address and I'm running the build now.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">connection</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">refused</category>
      <pubDate>Sun, 27 Sep 2009 02:39:36 GMT</pubDate>
      <author>blainek</author>
      <guid>http://communities.vmware.com/message/1374853</guid>
      <dc:date>2009-09-27T02:39:36Z</dc:date>
      <clearspace:dateToText>1 month, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Building OVF Based Appliances</title>
      <link>http://communities.vmware.com/message/1371248</link>
      <description>You can definitely use VMware Studio to build OVFs. Check out for more information: &lt;a class="jive-link-external" href="http://blogs.vmware.com/vapp/2009/08/configuring-ovf-properties-through-vmware-studio-20.html"&gt;http://blogs.vmware.com/vapp/2009/08/configuring-ovf-properties-through-vmware-studio-20.html&lt;/a&gt;</description>
      <pubDate>Tue, 22 Sep 2009 21:31:05 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1371248</guid>
      <dc:date>2009-09-22T21:31:05Z</dc:date>
      <clearspace:dateToText>2 months, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Network Interface types on Studio-authored appliances</title>
      <link>http://communities.vmware.com/message/1371116</link>
      <description>Thanks, Vishwas, this is great. The ability to do so from the standard menu (and preserve during builds) is a feature request. As is the ability to give the Interfaces names, which I see I can edit in the ovf file too.</description>
      <pubDate>Tue, 22 Sep 2009 19:41:57 GMT</pubDate>
      <author>HMVM123</author>
      <guid>http://communities.vmware.com/message/1371116</guid>
      <dc:date>2009-09-22T19:41:57Z</dc:date>
      <clearspace:dateToText>2 months, 3 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>EULA on import and startup</title>
      <link>http://communities.vmware.com/message/1370938</link>
      <description>The only "configuration", or the tools installation information that we expose is the entry is in the application repository section in the build UI.&lt;br /&gt;
If you goto the Application tab you should see "http://&lt;a class="jive-link-external" href="http://VADK.localIP"&gt;http://VADK.localIP&lt;/a&gt;/vmware-open-vm-tools/centos/5/2", this refers to the path within Studio from where we install tools.&lt;br /&gt;
&lt;br /&gt;
You could infact goto this webpage &lt;a class="jive-link-external" href="http://packages.vmware.com/tools/esx/index.html,"&gt;http://packages.vmware.com/tools/esx/index.html,&lt;/a&gt; where you may be able to find updates to vmware-tools for your OS. You can then download them and add it to your application repository and you get new tools.&lt;br /&gt;
&lt;br /&gt;
Vishwas</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">eula</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <pubDate>Tue, 22 Sep 2009 17:15:27 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1370938</guid>
      <dc:date>2009-09-22T17:15:27Z</dc:date>
      <clearspace:dateToText>2 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Protect virtual appliances from duplication</title>
      <link>http://communities.vmware.com/message/1367113</link>
      <description>Hi tut thanks for your rsponse will try that!</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <pubDate>Fri, 18 Sep 2009 01:45:24 GMT</pubDate>
      <author>nsolop</author>
      <guid>http://communities.vmware.com/message/1367113</guid>
      <dc:date>2009-09-18T01:45:24Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Running studiocli via ssh -o using authorized_keys results in Epic Build Fail</title>
      <link>http://communities.vmware.com/message/1366990</link>
      <description>&lt;br /&gt;
Just call vabs.pl directly instead of studiocli, as in:&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
ssh root@vmstudio2 /opt/vmware/share/build/vabs.pl \
                -cvp /tmp/profile.xml -i instance X&lt;br /&gt;
&lt;p /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studiocli</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">ssh</category>
      <pubDate>Thu, 17 Sep 2009 22:06:33 GMT</pubDate>
      <author>Will DeHaan</author>
      <guid>http://communities.vmware.com/message/1366990</guid>
      <dc:date>2009-09-17T22:06:33Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Attempting to change the Guest NIC drivers with a VIM Sh script HELP !</title>
      <link>http://communities.vmware.com/message/1365569</link>
      <description>As mentioned, you'll want to look at using vSphere API in accomplishing this task using either the vSphere SDK for Perl or PowerCLI.&lt;br /&gt;
&lt;br /&gt;
In either case, the proper way to melodramatically do this is to locate the VM(s) that you want to modify, shutdown the VM, add the new vmxnet adapter, remove the old and then power back on the VM and re-ip. When you remove the adapter or even adding a new adapter you'll get a new MAC Address, this may break any type of software you may have that licenses against a specific MAC. You of course, could record the previous MAC and then set it to preserve. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
=========================================================================&lt;br /&gt;
William Lam&lt;br /&gt;
VMware vExpert 2009&lt;br /&gt;
VMware ESX/ESXi scripts and resources at: &lt;a class="jive-link-external" href="http://engineering.ucsb.edu/~duonglt/vmware/"&gt;http://engineering.ucsb.edu/~duonglt/vmware/&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-9852"&gt;vGhetto Script Repository&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-community" href="http://communities.vmware.com/community/private/bitbucket/developer/codecentral" title="Sample code for VMware vSphere SDKs and APIs"&gt;VMware Code Central - Scripts/Sample code for Developers and Administrators&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-community" href="http://communities.vmware.com/community/vmtn/archive/beta/vibeta1/developer"&gt;VMware Developer Comuunity&lt;/a&gt;&lt;br /&gt;
&lt;a class="jive-link-external" href="http://twitter.com/lamw"&gt;Twitter: @lamw&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;img src="http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg" alt="http://engineering.ucsb.edu/~duonglt/vmware/vexpert_silver_icon.jpg" class="jive-image"  /&gt;&lt;br /&gt;
&lt;br /&gt;
If you find this information useful, please award points for "correct" or "helpful".</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vim</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">sh</category>
      <pubDate>Wed, 16 Sep 2009 17:18:06 GMT</pubDate>
      <author>lamw</author>
      <guid>http://communities.vmware.com/message/1365569</guid>
      <dc:date>2009-09-16T17:18:06Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>How can I access VMware Studio via Eclipse through a proxy?</title>
      <link>http://communities.vmware.com/message/1363755</link>
      <description>Windows XP, Java 1.6</description>
      <pubDate>Tue, 15 Sep 2009 07:02:22 GMT</pubDate>
      <author>JVRDT</author>
      <guid>http://communities.vmware.com/message/1363755</guid>
      <dc:date>2009-09-15T07:02:22Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>Debugging application install</title>
      <link>http://communities.vmware.com/message/1363236</link>
      <description>&lt;br /&gt;
I wanted to folow up with my findings to share information. I did not do extensive testing, but enough to lead me to believe this suggestion did not work as hoped.&lt;br /&gt;
&lt;p /&gt;
I changed my profile to look like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;vadk:ApplicationPackages&amp;gt;&lt;br /&gt;
&amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://172.16.1.65/ISV/appliancePackages/3rdparty*1*/3rdparty-ssl-4.2-99.i586.rpm"&gt;http://172.16.1.65/ISV/appliancePackages/3rdparty*1*/3rdparty-ssl-4.2-99.i586.rpm&lt;/a&gt;&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
&amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://172.16.1.65/ISV/appliancePackages/3rdparty*2*/3rdparty-apache2-4.2-99.i586.rpm"&gt;http://172.16.1.65/ISV/appliancePackages/3rdparty*2*/3rdparty-apache2-4.2-99.i586.rpm&lt;/a&gt;&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
&amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://172.16.1.65/ISV/appliancePackages/3rdparty*3*/3rdparty-php4-4.2-99.i586.rpm"&gt;http://172.16.1.65/ISV/appliancePackages/3rdparty*3*/3rdparty-php4-4.2-99.i586.rpm&lt;/a&gt;&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
&amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://172.16.1.65/ISV/appliancePackages/3rdparty*4*/3rdparty-oracleSoftware-1.0-1.i586.rpm"&gt;http://172.16.1.65/ISV/appliancePackages/3rdparty*4*/3rdparty-oracleSoftware-1.0-1.i586.rpm&lt;/a&gt;&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
&amp;lt;vadk:url&amp;gt;&lt;a class="jive-link-external" href="http://172.16.1.65/ISV/appliancePackages/pre_chroot/onesign-4.2-99.i586.rpm"&gt;http://172.16.1.65/ISV/appliancePackages/pre_chroot/onesign-4.2-99.i586.rpm&lt;/a&gt;&amp;lt;/vadk:url&amp;gt;&lt;br /&gt;
&amp;lt;/vadk:ApplicationPackages&amp;gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Here are the lines from the postinstall.log in the status directory which shows the order of install:&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
&lt;blockquote&gt;+ &lt;b&gt;grep '&amp;lt;install&amp;gt;' postinstall.log&lt;/b&gt; +&lt;/blockquote&gt;
&lt;blockquote&gt;&amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-vami-network-2.0.0.0-0.i386 &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-init-2.0.0.1017-185256.noarch &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-vami-core-2.0.0.0-0.i386 &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-vami-2.0.0.1017-185256.i386 &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-vami-servicebase-2.0.0.1017-185256.i386 &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-vami-system-2.0.0.0-0.i386 &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-vami-update-2.0.0.0-0.i386 &lt;br clear="all" /&gt; &amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S3%3A0"&gt;S3:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;vmware-studio-appliance-config-2.0.0.0-090914173127.noarch &lt;br clear="all" /&gt; &lt;b&gt;&amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S4%3A0"&gt;S4:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;3rdparty-oracleSoftware-1.0-1.i586&lt;/b&gt; &lt;br clear="all" /&gt; *	&amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S4%3A0"&gt;S4:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;3rdparty-php4-4.2-99.i586* &lt;br clear="all" /&gt; *	&amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S4%3A0"&gt;S4:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;3rdparty-apache2-4.2-99.i586* &lt;br clear="all" /&gt; *	&amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S4%3A0"&gt;S4:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;onesign-4.2-99.i586* &lt;br clear="all" /&gt; *	&amp;lt;install&amp;gt;   &lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=S4%3A0"&gt;S4:0&lt;/a&gt;&lt;a class="jive-link-adddocument" href="http://communities.vmware.com/community-document-picker.jspa?communityID=&amp;subject=package"&gt;package&lt;/a&gt;3rdparty-ssl-4.2-99.i586*&lt;/blockquote&gt;
&lt;br /&gt;
The documentation is a bit confusing on controlling the order of the RPM install. I am going to try the suggestions of having a pre or post script handle the installion of my application. Changing the dependcies of the RPMs is a longer term effort. I do not want this virtual appliance effort to impact many existing processes that use the RPMs as built today. &lt;br /&gt;
&lt;p /&gt;
Thanks&lt;br /&gt;
&lt;p /&gt;
Alan</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware_studio_2.0</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">create</category>
      <pubDate>Mon, 14 Sep 2009 18:05:36 GMT</pubDate>
      <author>AlanJS</author>
      <guid>http://communities.vmware.com/message/1363236</guid>
      <dc:date>2009-09-14T18:05:36Z</dc:date>
      <clearspace:dateToText>2 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>getting Virtual Disk state - persistent / non persistent</title>
      <link>http://communities.vmware.com/message/1351027</link>
      <description>This is VMware Studio product community. You should try posting this question to the vSphere C# SDK forum, I believe this link is the right one: &lt;a class="jive-link-external" href="http://communities.vmware.com/community/developer/codecentral/vsphere_ws_c"&gt;http://communities.vmware.com/community/developer/codecentral/vsphere_ws_c&lt;/a&gt;</description>
      <pubDate>Mon, 31 Aug 2009 17:20:03 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1351027</guid>
      <dc:date>2009-08-31T17:20:03Z</dc:date>
      <clearspace:dateToText>2 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Studio Readme</title>
      <link>http://communities.vmware.com/docs/DOC-10599</link>
      <description>VMware Studio Readme</description>
      <pubDate>Tue, 25 Aug 2009 22:12:13 GMT</pubDate>
      <author>Corey_R</author>
      <guid>http://communities.vmware.com/docs/DOC-10599</guid>
      <dc:date>2009-08-25T22:12:13Z</dc:date>
      <clearspace:dateToText>2 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Create OVA file as part of build</title>
      <link>http://communities.vmware.com/message/1345371</link>
      <description>&lt;br /&gt;
Sorry, currently VMware Studio only allows you to create appliances with  supported OSes/distros and it also automates other parts (ex: installation of application packages,etc). We will try to support such scenarios in Studio in the future.&lt;br /&gt;
&lt;p /&gt;
You may find the following useful. &lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;vSphere SDK/powercli provided by VMware will be useful for automated creation of your VM (this will need some amount of scripting/programming).&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;VMware's ovftool will help packaging your VM into an OVA (this doesn't allow customization of text/and various other options in the OVF).&lt;/li&gt;
&lt;/ul&gt;
&lt;p /&gt;
 Vishwas&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">ova</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">build</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">script</category>
      <pubDate>Mon, 24 Aug 2009 21:04:23 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1345371</guid>
      <dc:date>2009-08-24T21:04:23Z</dc:date>
      <clearspace:dateToText>3 months, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Communication with the virtual machine may have been interrupted</title>
      <link>http://communities.vmware.com/message/1342596</link>
      <description>Hi, &lt;br /&gt;
&lt;br /&gt;
Looks like you are having issues powering VMs when using VMware Server product directly (and not while using VMware Studio) ? If yes, VMware Server forums may be of more help.&lt;br /&gt;
Could you give us more information: are you using VMware Studio 1.0? Are you using VMware Server 1.04,1.0.5, or 1.06 (other versions probably don't work with Studio 1.0 I mean)? &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Also, could you try out VMware Studio 2.0 beta (it supports other platforms/products like ESX, vCenter, Server 2.0, WorkStation)? &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Vishwas&lt;br /&gt;
&lt;br /&gt;
Message was edited by: vnagaraja</description>
      <pubDate>Thu, 20 Aug 2009 15:29:17 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1342596</guid>
      <dc:date>2009-08-20T15:29:17Z</dc:date>
      <clearspace:dateToText>3 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>18</clearspace:replyCount>
    </item>
    <item>
      <title>Technology Exchange Developer Day - VMware Studio - Enabling Creation and Deployment of vApps</title>
      <link>http://communities.vmware.com/message/1341150</link>
      <description>Hi Thomas,&lt;br /&gt;
&lt;br /&gt;
Some of the sessions will be video taped and will be made public to the community after the event @ www.developer.vmware.com&lt;br /&gt;
&lt;br /&gt;
So, stay tuned!&lt;br /&gt;
Nava</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">enabling</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">creation</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">deployment</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vapps</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">technology_exchange</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">developer_day</category>
      <pubDate>Wed, 19 Aug 2009 07:03:22 GMT</pubDate>
      <author>navadavuluri</author>
      <guid>http://communities.vmware.com/message/1341150</guid>
      <dc:date>2009-08-19T07:03:22Z</dc:date>
      <clearspace:dateToText>3 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Studio Session @ Technology Exchange - Developer Day - VMworld 2009 - August 31, 2009</title>
      <link>http://communities.vmware.com/message/1310789</link>
      <description>Here is the event site: &lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-community" href="http://communities.vmware.com/community/private/bitbucket/developer/techexchange"&gt;http://communities.vmware.com/community/developer/techexchange&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
Sessions/labs schedule:&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;a class="jive-link-external" href="http://blogs.vmware.com/developer/2009/07/vmware-technology-exchange-developer-day-sessions-schedule.html"&gt;http://blogs.vmware.com/developer/2009/07/vmware-technology-exchange-developer-day-sessions-schedule.html&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
twitter info: &lt;a class="jive-link-external" href="http://twitter.com/VMDeveloperday"&gt;http://twitter.com/VMDeveloperday&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">technology_exchange</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmworld_2009</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">sdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">api</category>
      <pubDate>Tue, 14 Jul 2009 17:59:26 GMT</pubDate>
      <author>navadavuluri</author>
      <guid>http://communities.vmware.com/message/1310789</guid>
      <dc:date>2009-07-14T17:59:26Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>OS Hard Disk size</title>
      <link>http://communities.vmware.com/message/1327713</link>
      <description>&lt;br /&gt;
We getting close to GA?&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Thomas H. Bryant III&lt;br /&gt;
Director, Advanced Technology &amp;#38; Products&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com"&gt;Vizioncore, Inc.&lt;/a&gt;&lt;br /&gt;
VMware Communities User Moderator</description>
      <pubDate>Mon, 03 Aug 2009 13:55:24 GMT</pubDate>
      <author>kix1979</author>
      <guid>http://communities.vmware.com/message/1327713</guid>
      <dc:date>2009-08-03T13:55:24Z</dc:date>
      <clearspace:dateToText>3 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>cant create or validate virtual appliance</title>
      <link>http://communities.vmware.com/message/1327448</link>
      <description>Thanks Nagaraja, for replying. You are right. I need studio to automate the VM packaging, and generate the ovf format. I need to create a VA for a customized version of my OS which runs on an x86 platform. VmWare Server works fine for me. So its an OS specific VA I want to achieve. It will be easier than me zipping the VM everytime I have a new release.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">create</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vix</category>
      <pubDate>Mon, 03 Aug 2009 08:05:56 GMT</pubDate>
      <author>rakshit</author>
      <guid>http://communities.vmware.com/message/1327448</guid>
      <dc:date>2009-08-03T08:05:56Z</dc:date>
      <clearspace:dateToText>3 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>23</clearspace:replyCount>
    </item>
    <item>
      <title>OVF inside the guest use</title>
      <link>http://communities.vmware.com/message/1314272</link>
      <description>&lt;br /&gt;
The sample is the script vami_ovf_process, it is located in /opt/vmware/share/vami/. It is written in python, so if you don't mind writing python code you can use that code as a reference. &lt;br /&gt;
&lt;p /&gt;
This is the in-guest script present on all linux VMs build by Studio.</description>
      <pubDate>Fri, 17 Jul 2009 20:43:04 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1314272</guid>
      <dc:date>2009-07-17T20:43:04Z</dc:date>
      <clearspace:dateToText>4 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>vApp, ovf-en.xml - Samples?</title>
      <link>http://communities.vmware.com/message/1311347</link>
      <description>We have posted an example on the vApp blog.</description>
      <pubDate>Wed, 15 Jul 2009 07:25:10 GMT</pubDate>
      <author>martinamdisen</author>
      <guid>http://communities.vmware.com/message/1311347</guid>
      <dc:date>2009-07-15T07:25:10Z</dc:date>
      <clearspace:dateToText>4 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>change credentials in repository</title>
      <link>http://communities.vmware.com/message/1310761</link>
      <description>&lt;br /&gt;
&lt;span class="jive-thread-reply-body-container"&gt;&lt;br /&gt;
btw:&lt;br /&gt;
is it possible to use a md5 hash password in the service-deploy.xml file?&lt;br /&gt;
&lt;p /&gt;
Thomas,&lt;br /&gt;
&lt;p /&gt;
 We authenticate with the webserver hosting the repository if a password is present, so you should be able to do this. It might require some work, as in finding the right authentication module for your webserver which can authenticate using the md5 hash password.&lt;br /&gt;
&lt;p /&gt;
Vishwas &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">repo</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">repository</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">change_user</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">change_password</category>
      <pubDate>Tue, 14 Jul 2009 17:36:29 GMT</pubDate>
      <author>vnagaraja</author>
      <guid>http://communities.vmware.com/message/1310761</guid>
      <dc:date>2009-07-14T17:36:29Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Is it possbile to mount /proc to /target/proc?</title>
      <link>http://communities.vmware.com/message/1308397</link>
      <description>&lt;div class="jive-quote"&gt;The problem is that the software (Postfix and MySQL Server) needs the /proc system because of start/stop scripts. &lt;/div&gt;
&lt;br /&gt;
If you are facing problem in installing Postfix and MySQL Server in Ubuntu. I have one suggestion, &lt;br /&gt;
&lt;br /&gt;
If you are using Postfix and MySQL Server debian packages from Ubuntu DVD then instead of installing these packages separately you can add these packages in 'List of packages from OS install media' of Application tab of VMware Studio 1.0 web UI. And then write the Postfix and MySQL Server configuration script in post-install script in OS tab of VMware Studio 1.0 web UI. i.e. installation will get done by Studio. &lt;br /&gt;
&lt;br /&gt;
For Postfix and MySQL Server configuration if you need /proc file system you can add the configuration script in firstboot script. &lt;br /&gt;
&lt;br /&gt;
Currently I don't have Ubuntu 7.04/7.10/8.04 DVD but I think these packages comes with Ubuntu server not with the desktop. &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;The VMware Studio 2.0 Beta is release, from where you will get more number of operating systems and advance features than VMware Studio 1.0.&lt;/b&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">variables</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">upgrade</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">proc</category>
      <pubDate>Sat, 11 Jul 2009 07:47:26 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1308397</guid>
      <dc:date>2009-07-11T07:47:26Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Problem with creating a virtual appliance with Ubuntu 8.0.4</title>
      <link>http://communities.vmware.com/message/1307478</link>
      <description>I had this problem too and solved it by setting a static ip adress but in the gateway field I inserted the VMware Studio IP!!!!&lt;br /&gt;
This works great. .. And YES Studio und Server are both in the same network and connected to the same switch!&lt;br /&gt;
&lt;br /&gt;
;o)&lt;br /&gt;
&lt;br /&gt;
Regards&lt;br /&gt;
Thomas</description>
      <pubDate>Fri, 10 Jul 2009 08:42:37 GMT</pubDate>
      <author>Jogarem</author>
      <guid>http://communities.vmware.com/message/1307478</guid>
      <dc:date>2009-07-10T08:42:37Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>vmware studio not cancelling a build</title>
      <link>http://communities.vmware.com/message/1307475</link>
      <description>you can normally click on details when canceling. Search on your process list that this process is really away and if it is so this&lt;br /&gt;
message will disappear when you start a build again.</description>
      <pubDate>Fri, 10 Jul 2009 08:38:25 GMT</pubDate>
      <author>Jogarem</author>
      <guid>http://communities.vmware.com/message/1307475</guid>
      <dc:date>2009-07-10T08:38:25Z</dc:date>
      <clearspace:dateToText>4 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Virtual Appliance Timezone</title>
      <link>http://communities.vmware.com/message/1304597</link>
      <description>&lt;br /&gt;
Yeah, I'm excited about VMWare Studio 2.0 - however; its in Beta so it can't be used for production VM's.&lt;br /&gt;
&lt;p /&gt;
 I think I'm going to just stick with UTC and not worry about timezones , since our application handles the timekeeping via Java tzupdate. &lt;br /&gt;
&lt;p /&gt;
 I'm hoping that , at least for now  - NTP added to the VA along with an ntp.conf with the settings recommended from VMware' s TimeKeeping guide would be enough for the VMWare Ready certification..</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">timezone</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">default</category>
      <pubDate>Tue, 07 Jul 2009 18:02:01 GMT</pubDate>
      <author>draygen</author>
      <guid>http://communities.vmware.com/message/1304597</guid>
      <dc:date>2009-07-07T18:02:01Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Coffee Talk - VMware Studio 2.0 Live Webinar - June 24th 2009 - 9:00 - 10:00 AM PST</title>
      <link>http://communities.vmware.com/message/1285974</link>
      <description>Folks, &lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;PDF slides available - please see attachment.&lt;/b&gt; &lt;br /&gt;
&lt;br /&gt;
All recordings and pdfs will be available on our &lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/DeveloperCenter/2009/06/11/announcing-the-vmware-coffee-talk-live-webinars-first-wed-of-the-month-900-am-1000-am-pst"&gt;VMware Coffee Talk&lt;/a&gt; Blog&lt;br /&gt;
&lt;br /&gt;
Link to Coffee Talk Blog &lt;br /&gt;
&lt;a class="jive-link-external" href="http://communities.vmware.com/blogs/DeveloperCenter/2009/07/01/announcing-the-vmware-coffee-talk-live-webinars-first-wed-of-the-month-900-am-1000-am-pst"&gt;http://communities.vmware.com/blogs/DeveloperCenter/2009/07/01/announcing-the-vmware-coffee-talk-live-webinars-first-wed-of-the-month-900-am-1000-am-pst&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Title: Studio 2.0: Build vApps and virtual appliances for the cloud &lt;br /&gt;
Date: Wednesday, June 24, 2009 &lt;br /&gt;
Time: 9:00 am, Pacific Daylight Time (GMT -07:00, San Francisco) &lt;br /&gt;
Meeting Number: 929 034 081 &lt;br /&gt;
Meeting Password: (This meeting does not require a password.) &lt;br /&gt;
More registration details below.&lt;br /&gt;
&lt;br /&gt;
Abstract: VMware Studio 2.0 helps configure, build, deploy, customize and maintain vApps and virtual appliances. These solution stacks can be deployed on VMware vSphere 4.0 or in the cloud and can be managed from the VMware Studio web console or from VMware vCenter Server. In this webinar, software vendors, application developers and IT administrators will get an overview of vApps and virtual appliances followed by what's new in Studio 2.0. We will walk you through the entire build process by starting with an application created in Eclipse (via the Eclipse plug-in in Studio) and demonstrating how it can be packaged as either a vApp or virtual appliance in OVF format. The process will also reveal various automated tools available, for creating a clean out-of-box experience, such as specifying exact OS requirements, building an update repository, adding custom management services and adding existing VM builds as input.VMware Studio 2.0 is going to be available as a public beta starting June 29, 2009&lt;br /&gt;
&lt;br /&gt;
Level: Beginner with basic understanding of Eclipse and Virtualization concepts. &lt;br /&gt;
&lt;br /&gt;
Speaker Matthew Ford Sr. Member Technical Staff BIO</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware_studio_2.0</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">coffee_talk_webinar</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">sdk</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">api</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">cloud</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">api</category>
      <pubDate>Tue, 16 Jun 2009 20:29:41 GMT</pubDate>
      <author>heyitspablo</author>
      <guid>http://communities.vmware.com/message/1285974</guid>
      <dc:date>2009-06-16T20:29:41Z</dc:date>
      <clearspace:dateToText>4 months, 3 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Build fails</title>
      <link>http://communities.vmware.com/message/1293585</link>
      <description>Thanks....&lt;br /&gt;
/&amp;#38;%(&amp;#38;=&amp;curren;)/&amp;#38;?//=(/?(/?&lt;br /&gt;
Now I can start all over &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/sad.gif" alt=":-(" /&gt;&lt;br /&gt;
&lt;p /&gt;
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points.&lt;br /&gt;
&lt;br /&gt;
Regards&lt;br /&gt;
A. Mikkelsen</description>
      <pubDate>Wed, 24 Jun 2009 11:23:18 GMT</pubDate>
      <author>A.Mikkelsen</author>
      <guid>http://communities.vmware.com/message/1293585</guid>
      <dc:date>2009-06-24T11:23:18Z</dc:date>
      <clearspace:dateToText>5 months, 4 days ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Deploying appliance on vSphere, warnings</title>
      <link>http://communities.vmware.com/message/1272243</link>
      <description>As per the comments from studio_relnotes10.html, Virtual appliances created with VMware Studio 1.0 can run on:&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;VMware Server 1.0.4, 1.0.5, 1.0.6, or 2.0.&lt;/li&gt;
&lt;li&gt;VMware ESX 3.0.3 or 3.5 Update 2.&lt;/li&gt;
&lt;li&gt;VMware ESXi Installable Update 2.&lt;/li&gt;
&lt;li&gt;VMware Workstation 6.0.4.&lt;/li&gt;
&lt;li&gt;VMware Player 2.0.4.&lt;/li&gt;
&lt;li&gt;VMware Fusion 1.1.3.&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
reference : &lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/studio/studio10/studio_relnotes10.html"&gt;http://www.vmware.com/support/developer/studio/studio10/studio_relnotes10.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
So I think vSphere is not supported platform for the VA which is created by VMware Studio 1.0</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">centos</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">warning</category>
      <pubDate>Thu, 04 Jun 2009 09:11:52 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1272243</guid>
      <dc:date>2009-06-04T09:11:52Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>appliance built with studio not working in VMware Workstation</title>
      <link>http://communities.vmware.com/message/1272159</link>
      <description>&lt;div class="jive-quote"&gt;OVF is basically meant for Hypervisor class i.e. ESX, ESXi.&lt;/div&gt;
&lt;br /&gt;
Sorry for this wrong comment. Actually Workspace 6.5.x can also take OVF (via the embeded Converter). &lt;br /&gt;
&lt;br /&gt;
Also I found that Virtual appliances created with VMware Studio 1.0 can run on:&lt;br /&gt;
    * VMware Server 1.0.4, 1.0.5, 1.0.6, or 2.0.&lt;br /&gt;
    * VMware ESX 3.0.3 or 3.5 Update 2.&lt;br /&gt;
    * VMware ESXi Installable Update 2.&lt;br /&gt;
    * VMware Workstation 6.0.4.&lt;br /&gt;
    * VMware Player 2.0.4.&lt;br /&gt;
    * VMware Fusion 1.1.3.&lt;br /&gt;
&lt;br /&gt;
reference: &lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/studio/studio10/studio_relnotes10.html"&gt;http://www.vmware.com/support/developer/studio/studio10/studio_relnotes10.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
That means Workstation 6.5.x is not officially supported platform for the VA which is created by VMware Studio 1.0</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">workstation</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">error</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">import</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">ovf</category>
      <pubDate>Thu, 04 Jun 2009 07:45:11 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1272159</guid>
      <dc:date>2009-06-04T07:45:11Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Problem installing PostgreSQL-8.3 on Ubuntu 8.04 VMWare Studio generated VM</title>
      <link>http://communities.vmware.com/message/1267950</link>
      <description>&lt;br /&gt;
Thanks for the reply, the postgresql-8.3 install worked fine when I installed it as an OS package - I guess during this phase of installation it is able to retrieve all of the required dependencies and it installs them in the proper order.&lt;br /&gt;
&lt;p /&gt;
It works great , now I just need to figure out why Tomcat 5.5 will not start during bootup, but starts fine if i manually start it up... But i guess this issue is for another thread &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
&lt;p /&gt;
 Thanks,&lt;br /&gt;
&lt;p /&gt;
 Brian</description>
      <pubDate>Mon, 01 Jun 2009 13:22:57 GMT</pubDate>
      <author>draygen</author>
      <guid>http://communities.vmware.com/message/1267950</guid>
      <dc:date>2009-06-01T13:22:57Z</dc:date>
      <clearspace:dateToText>5 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Screen displayed after appliance startup.</title>
      <link>http://communities.vmware.com/message/1265902</link>
      <description>&lt;div class="jive-quote"&gt;I'd like to include a link to our application's URL, something like &lt;a class="jive-link-external" href="http://"&gt;http://&lt;/a&gt;&amp;lt;appliance ip&amp;gt;:1234&lt;/div&gt;
&lt;br /&gt;
Please refer the &lt;a class="jive-link-external" href="http://communities.vmware.com/thread/204043"&gt;http://communities.vmware.com/thread/204043&lt;/a&gt; for the same.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">configuration</category>
      <pubDate>Fri, 29 May 2009 09:21:19 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1265902</guid>
      <dc:date>2009-05-29T09:21:19Z</dc:date>
      <clearspace:dateToText>6 months, 9 hours ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>VM EULA on import and boot</title>
      <link>http://communities.vmware.com/message/1263705</link>
      <description>&lt;br /&gt;
I've got it working, though it's a manual process.&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;remove the EULA from the Description page in vmware-studio&lt;/li&gt;
&lt;li&gt;build the appliance&lt;/li&gt;
&lt;li&gt;modify the output .OVF file and add the EULA xml section back in (copied from a previous OVF)&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
It works, but it's a bit of a hack. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
The XML code that I inserted into the output .OVF file is below&lt;br /&gt;
&lt;p /&gt;
&amp;lt;Section xsi:type="ovf:EulaSection_Type" xml:lang="en"&amp;gt;&lt;br /&gt;
&amp;lt;Info&amp;gt;End User License Agreement&amp;lt;/Info&amp;gt;&lt;br /&gt;
&amp;lt;License&amp;gt;CHANGE ME - EULA Text&amp;lt;/License&amp;gt;&lt;br /&gt;
&amp;lt;/Section&amp;gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">eula</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <pubDate>Wed, 27 May 2009 13:52:32 GMT</pubDate>
      <author>mkolcun</author>
      <guid>http://communities.vmware.com/message/1263705</guid>
      <dc:date>2009-05-27T13:52:32Z</dc:date>
      <clearspace:dateToText>6 months, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Cygwin/OpenSSH</title>
      <link>http://communities.vmware.com/message/1263273</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;lshrivas wrote:&lt;/span&gt;&lt;div class="jive-quote"&gt;
&lt;p /&gt;
I am also facing same issues while creating virtual appliance from VmWare Studio.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;

&lt;ul class="jive-dash"&gt;
&lt;li&gt;I have Vmware server and Open SSH 4.2p1 on windows server2003 and when i try to do scp from&lt;/li&gt;
&lt;/ul&gt;
&lt;/ul&gt;
vmware studio machine I get &lt;b&gt;Read from socket failed: Connection reset by peer&lt;/b&gt;.&lt;/div&gt;
&lt;/div&gt;
&lt;p /&gt;
Unfortunately the error message itself provides little useful information, all that is being reported back is that a TCP RST (Reset packet) was sent by the remote host, it doesn't indicate the reason. TCP RSTs can be sent because of any sort of normal session teardown, and just demonstrate that the remote TCP stack "closed" the connection cleanly (sending RST rather than ceasing to send any traffic at all).&lt;br /&gt;
&lt;br /&gt;
You'll need to run scp with at least minimal verbosity enabled (single *-v*) if not detailed verbosity (multiple *-v*) to get any sort of useful information on when, and &lt;b&gt;maybe&lt;/b&gt; why the session was torn down.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">openssh</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">lost</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">connection</category>
      <pubDate>Wed, 27 May 2009 04:02:30 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1263273</guid>
      <dc:date>2009-05-27T04:02:30Z</dc:date>
      <clearspace:dateToText>6 months, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>17</clearspace:replyCount>
    </item>
    <item>
      <title>creating first vmware appliance</title>
      <link>http://communities.vmware.com/message/1234759</link>
      <description>thanks for the info.</description>
      <pubDate>Fri, 24 Apr 2009 06:04:29 GMT</pubDate>
      <author>boarder428</author>
      <guid>http://communities.vmware.com/message/1234759</guid>
      <dc:date>2009-04-24T06:04:29Z</dc:date>
      <clearspace:dateToText>7 months, 5 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>How to create Red Hat 4 AS x64 bit Virtual Appliance via VMware Studio?</title>
      <link>http://communities.vmware.com/message/1233546</link>
      <description>&lt;b&gt;The Red Hat 4 AS x64 bit is not supported by VMware Studio 1.0.&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
If you just want to build a VA, and don't care about management tools, you might be able to modify the existing Red Hat Linux appliance template. &lt;br /&gt;
&lt;br /&gt;
I have tried the following procedure for RHEL3.8 to build Virtual Appliance (VA). This procedure can be use to build VA but I observed that the pre, post, first boot and subsequent boot scripts are not get executed during VA creation. Also my application package is not getting installed in VA during VA creation. You can give a try to build VA for 64 bit using VMware Studio 1.0.&lt;br /&gt;
&lt;br /&gt;
1.	mkdir p /opt/vmware/lib/build/include/rhel/3/8 and make same soft links as RHEL 5.1 &lt;br /&gt;
2.	mkdir p /opt/vmware/etc/build/templates/redhat/3/8 &lt;br /&gt;
3.	cp /opt/vmware/etc/build/templates/redhat/5/redhat5.xsl /opt/vmware/etc/build/templates/redhat/3/ &lt;br /&gt;
4.	mv /opt/vmware/etc/build/templates/redhat/3/redhat5.xsl /opt/vmware/etc/build/templates/redhat/3/redhat3.xsl &lt;br /&gt;
5.	Using redhat-config-kickstart prepared kickstart configuration in working RHEL3.8 VM. &lt;br /&gt;
6.	Replace the RHEL5.1 kickstart configuration with redhat3.8 in redhat3.xsl file.  &lt;br /&gt;
7.	Make necessary OS changes in RHEL3.8 build profile file. [RHEL5.1 =&amp;gt; RHEL3.8]&lt;br /&gt;
8.	All other things are similar as RHEL5.1 including vmware tools. &lt;br /&gt;
9.	Build the VA using VMware Studio.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <pubDate>Thu, 23 Apr 2009 07:32:32 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1233546</guid>
      <dc:date>2009-04-23T07:32:32Z</dc:date>
      <clearspace:dateToText>7 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Writing your own operating system</title>
      <link>http://communities.vmware.com/message/1232598</link>
      <description>&lt;br /&gt;
JMills,&lt;br /&gt;
&lt;p /&gt;
 Thanks too for your response, I couldn't decide which forum, maybe we should ask vmware to start a forum for OS development tactics and strategies with vmware.&lt;br /&gt;
&lt;p /&gt;
 I just took a quick look at the menuetOS.net site it looks pretty impressive what they have achieved.&lt;br /&gt;
&lt;p /&gt;
 I'm still very much a beginner to OS development but I am determined to give it a go and document my findings of using vmware products.&lt;br /&gt;
&lt;p /&gt;
 Thanks again&lt;br /&gt;
&lt;p /&gt;
Peter&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">writing_your_own_os</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">operating_system</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">developing</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">create</category>
      <pubDate>Wed, 22 Apr 2009 13:56:43 GMT</pubDate>
      <author>PeterJ1983</author>
      <guid>http://communities.vmware.com/message/1232598</guid>
      <dc:date>2009-04-22T13:56:43Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>8</clearspace:replyCount>
    </item>
    <item>
      <title>File permission</title>
      <link>http://communities.vmware.com/message/1232241</link>
      <description>Some followup from one of the folks on the VMware Studio 1.0 engineering team. &lt;br /&gt;
 Contextual edits I have added are marked with [ ] brackets.&lt;br /&gt;
&lt;br /&gt;
 They should not be [0]777, they should be [0]644, writable by owner [only].&lt;br /&gt;
&lt;p /&gt;
I've just tested this, and after unzip'ing, the files have these modes:&lt;br /&gt;
&lt;br /&gt;
-rwxr-xr-x  1 vaeng01 vaeng01      1035 2009-04-09 10:22 Appliance.vmx&lt;br /&gt;
-rw-r--r--  1 vaeng01 vaeng01  25034752 2009-04-09 10:23 data1-s001.vmdk&lt;br /&gt;
-rw-r--r--  1 vaeng01 vaeng01       419 2009-04-09 09:44 data1.vmdk&lt;br /&gt;
-rw-r--r--  1 vaeng01 vaeng01  22806528 2009-04-09 10:23 system-s001.vmdk&lt;br /&gt;
-rw-r--r--  1 vaeng01 vaeng01 922746880 2009-04-09 10:23 system-s002.vmdk&lt;br /&gt;
-rw-r--r--  1 vaeng01 vaeng01       456 2009-04-09 09:44 system.vmdk&lt;br /&gt;
&lt;br /&gt;
 This is exactly correct. We had to set the execute bits on the vmx file for [some &lt;br /&gt;
 behavioral quirk in] Server 1.0, but all the others are [0]644, writable [only] by the &lt;br /&gt;
 person that extracted the zip file (me).&lt;br /&gt;
&lt;br /&gt;
 Note that the user's umask plays a large part in what the modes will be; his umask &lt;br /&gt;
 is probably set incorrectly [or the user account which was used to extract the file is &lt;br /&gt;
 not the same one being used to run the virtual appliance].</description>
      <pubDate>Wed, 22 Apr 2009 06:14:58 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1232241</guid>
      <dc:date>2009-04-22T06:14:58Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VMware vSphere 4 has been announced ... what about VMware Studio compatibility?</title>
      <link>http://communities.vmware.com/message/1232234</link>
      <description>&lt;br /&gt;
Now that VMware vSphere 4 (vCenter Server 4 + ESX / ESXi 4) can be discussed without NDA, the next question of course is "What about VMware Studio compatibility?"&lt;br /&gt;
&lt;p /&gt;
The answer is two-fold, because vSphere 4 has support for both OVF 0.9 (VMware draft implementations) and OVF 1.0 (DMTF ratified standard DSP0243 1.0.0) bundles:&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;VMware Studio 1.0&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
Out of the box, virtual appliances created with VMware Studio 1.0 (build 620) as OVF bundles can be imported ("deployed" in vSphere 4 parlance) &lt;b&gt;without modification&lt;/b&gt; to a vSphere 4 host* using the vSphere 4 client.&lt;br /&gt;
&lt;p /&gt;
&lt;b&gt;HOWEVER...&lt;/b&gt;&lt;br /&gt;
&lt;p /&gt;
If the import occurs via a vCenter Server 4 instance, the "Product" data within that OVF bundle will be used to add vApp properties to that virtual appliance, and the vApp bit will be set to "true".&lt;br /&gt;
&lt;p /&gt;
If the import occurs via an ESX / ESXi 4 host directly (whether managed or standalone), the "Product" data will be &lt;b&gt;silently discarded&lt;/b&gt;, and the vApp bit will be left set to "false".&lt;br /&gt;
&lt;p /&gt;
Several additional "Product" data elements are capable of being parsed into vApp properties, but I will reserve that for a separate post which delves into further detail on vApp properties exclusively.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li&gt;VMware Studio 2.0&lt;/li&gt;
&lt;/ul&gt;
&lt;br /&gt;
VMware Studio 2.0 (as mentioned in message 1207318 in this thread &lt;a class="jive-link-message" href="http://communities.vmware.com/message/1207318#1207318"&gt;http://communities.vmware.com/message/1207318&lt;/a&gt; ) will incorporate support for OVF 1.0, officially known as DMTF DSP0243 1.0.0 -- which adds a number of extensibility options necessary for more complex vApp constructs.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
(*) "vSphere 4 host" == A VMware vCenter Server 4 managed ESX / ESXi host, or an ESX / ESXi 4 host in "Single Server" mode</description>
      <pubDate>Wed, 22 Apr 2009 05:45:13 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1232234</guid>
      <dc:date>2009-04-22T05:45:13Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>How to specify machine ID in OVF</title>
      <link>http://communities.vmware.com/message/1232233</link>
      <description>MS-&lt;br /&gt;
&lt;br /&gt;
"A VMware host can send the machine id located in the *.vmx file to the guest."&lt;br /&gt;
&lt;br /&gt;
Technically the virtual machine monitor (VMM) exposes the machine.id value to the guest based on the in-memory representation of the .vmx file data. Assuming of course you were referring to machine.id value itself and not the behavior of smbios.reflectHost functionality.&lt;br /&gt;
&lt;p /&gt;
Back to the topic at hand...&lt;br /&gt;
&lt;br /&gt;
The implementation of OVF within VMware Studio 1.0 and VMware ESX / ESXi 3.5.0 is based on the Open Virtualization Format standard proposal drafts (loosely versioned 0.9), far predating the recent ratification by the DMTF of OVF as DSP0243 1.0.0 (~Q1 2009). Certain nice-to-have features such as extensibility for virtualization platform specific directives (machine.id = "...." for VMware native VMX as an example) were not included in those early drafts, and are therefore unavailable.&lt;br /&gt;
&lt;br /&gt;
In short, even if you were able to include that data in an OVF bundle using VMware Studio 1.0, it would not be propagated during import and conversion to VMware native VMX format using the VI Client connecting to an ESX / ESXi 3.5.0 host.</description>
      <pubDate>Wed, 22 Apr 2009 05:16:04 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1232233</guid>
      <dc:date>2009-04-22T05:16:04Z</dc:date>
      <clearspace:dateToText>7 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Welcome Text...</title>
      <link>http://communities.vmware.com/message/1223313</link>
      <description>There might be some other way to add the text in welcome screen but following is my workaround for this problem.&lt;br /&gt;
&lt;br /&gt;
By default the machine IP is shown in welcome screen of Virtual Appliance created by VMware Studio. But if you want to add your application name with the IP address and port number, then you can edit the /opt/vmware/etc/isv/textscript file in runtime as follows.&lt;br /&gt;
&lt;br /&gt;
1. Write a small shell script for finding the IP address as follows and add your text along with the IP address.&lt;br /&gt;
#/bin/bash&lt;br /&gt;
ifconfig | grep Bcast | awk '{ print $2 }' | awk -F ":" '{ print "you can access XYZ application at &lt;a class="jive-link-external" href="http://"&gt;http://&lt;/a&gt;"$2 ":9999" }' &amp;gt;&amp;gt; /opt/vmware/etc/isv/textscript&lt;br /&gt;
exit 0&lt;br /&gt;
2. Put the shell script in VMware Studio's first boot.&lt;br /&gt;
&lt;br /&gt;
If you think your Virtual Appliance might change the IP in subsequent boot then write the whole textscript using shell script and put that script in VMware Studio's subsequent boot area or /etc/rc.local to execute on every boot.</description>
      <pubDate>Sat, 11 Apr 2009 09:35:29 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1223313</guid>
      <dc:date>2009-04-11T09:35:29Z</dc:date>
      <clearspace:dateToText>7 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>OVF - How much does VMware support?</title>
      <link>http://communities.vmware.com/message/1207318</link>
      <description>&lt;br /&gt;
VMware Studio 1.0 supports OVF 0.9 only. VMware Studio 1.0 was released at VMworld 2008 (Sept 2008) last year when OVF 1.0 was not decided upon as a standard. The next version of Studio i.e. Studio 2.0 will support OVF 1.0.</description>
      <pubDate>Tue, 24 Mar 2009 14:15:10 GMT</pubDate>
      <author>asahai</author>
      <guid>http://communities.vmware.com/message/1207318</guid>
      <dc:date>2009-03-24T14:15:10Z</dc:date>
      <clearspace:dateToText>8 months, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Error on web access - 'Toolbar' is null or not an object.</title>
      <link>http://communities.vmware.com/message/1190451</link>
      <description>&lt;br /&gt;
Hi all.&lt;br /&gt;
&lt;p /&gt;
 many thanks for your help.&lt;br /&gt;
&lt;p /&gt;
I solved the problem by recreating the web access link of the hosts that gave this error message.&lt;br /&gt;
&lt;p /&gt;
Using the new link, the problem was gone..&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thanks Again &lt;img src="!" alt="!" class="jive-image"  /&gt;&lt;br /&gt;
&lt;p /&gt;
Jo.</description>
      <pubDate>Thu, 05 Mar 2009 23:44:09 GMT</pubDate>
      <author>Yossian</author>
      <guid>http://communities.vmware.com/message/1190451</guid>
      <dc:date>2009-03-05T23:44:09Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Where to download latest vmware tools?</title>
      <link>http://communities.vmware.com/message/1189443</link>
      <description>It turns out it's possible to download vmware tools here now:&lt;br /&gt;
    &lt;a class="jive-link-external" href="http://www.vmware.com/download/packages.html"&gt;http://www.vmware.com/download/packages.html&lt;/a&gt;&lt;br /&gt;
    &lt;a class="jive-link-external" href="http://packages.vmware.com/tools"&gt;http://packages.vmware.com/tools&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Unfortunately the sources aren't there, so I guess if you're not using a standard kernel and a standard linux distro: bummer.&lt;br /&gt;
&lt;br /&gt;
However it's not all doom and gloom. It looks like those packages are just open-vm-tools!!!&lt;br /&gt;
&lt;br /&gt;
Also, this conversation has been pointed out to me:&lt;br /&gt;
    &lt;a class="jive-link-external" href="http://sourceforge.net/mailarchive/forum.php?thread_name=48C15444.3000904@feds.uwaterloo.ca&amp;#38;forum_name=open-vm-tools-discuss"&gt;http://sourceforge.net/mailarchive/forum.php?thread_name=48C15444.3000904@feds.uwaterloo.ca&amp;#38;forum_name=open-vm-tools-discuss&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
We ship a kernel that vmware doesn't provide a binary package for. We used to compile the "latest" vmware tools, where "latest" meant "the version in the most recent esxi we have running".&lt;br /&gt;
&lt;br /&gt;
From now on, we'll probably just use open-vm-tools...</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware_tools</category>
      <pubDate>Thu, 05 Mar 2009 09:32:37 GMT</pubDate>
      <author>wesleyd</author>
      <guid>http://communities.vmware.com/message/1189443</guid>
      <dc:date>2009-03-05T09:32:37Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Post-install script debugging for Virtual Appliance</title>
      <link>http://communities.vmware.com/message/1183745</link>
      <description>Thx:)</description>
      <pubDate>Fri, 27 Feb 2009 10:36:32 GMT</pubDate>
      <author>Hrits</author>
      <guid>http://communities.vmware.com/message/1183745</guid>
      <dc:date>2009-02-27T10:36:32Z</dc:date>
      <clearspace:dateToText>9 months, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Installing sun java packages - Ubuntu</title>
      <link>http://communities.vmware.com/message/1183068</link>
      <description>Did you do that by modifying the Java packages?  I would like to know, because I'm working on an Eclipse appliance.  (Eclipse requires Java.)  Thanks!</description>
      <pubDate>Thu, 26 Feb 2009 18:14:28 GMT</pubDate>
      <author>tut</author>
      <guid>http://communities.vmware.com/message/1183068</guid>
      <dc:date>2009-02-26T18:14:28Z</dc:date>
      <clearspace:dateToText>9 months, 2 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Creation of virtual appliance using VMware Studio</title>
      <link>http://communities.vmware.com/message/1166988</link>
      <description>&lt;div class="jive-quote"&gt;&lt;div class="jive-quote"&gt;My goal, as I mentioned, is to create a basic virtual appliance using the VMware studio.&lt;/div&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;&lt;div class="jive-quote"&gt;It would be greatly appreciated if you can highlight the steps I should follow, and the required OS\VM platform for these steps.&lt;/div&gt;&lt;/div&gt;
&lt;br /&gt;
Following are the generalized steps you should follow to create Virtual Appliance (VA)&lt;br /&gt;
&lt;br /&gt;
   1. Make sure which operating system is compatible for your application.&lt;br /&gt;
   2. Your application should be in rpm/deb format.&lt;br /&gt;
   3. Download the Operating system (OS) iso from the links given in VMware Stuio admin guide and put in Studio&amp;rsquo;s /opt/vmware/www/ISV/ISO folder.&lt;br /&gt;
   4. Copy your application in application package repositories folder.&lt;br /&gt;
   5. Share the ssh keys between VMware Studio and your host OS.&lt;br /&gt;
   6. Create the build profile manually mentioned in VMware Studio admin guide.&lt;br /&gt;
   7. Validate the profile using VMware studio web console.&lt;br /&gt;
   8. Build the profile using VMware studio web console.&lt;br /&gt;
&lt;br /&gt;
Following is the link where you can download the VMware Studio admin guide.&lt;br /&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://vmware.com/files/pdf/vmware_studio_adminguide.pdf"&gt;http://vmware.com/files/pdf/vmware_studio_adminguide.pdf&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">create</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">virtual</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">using</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <pubDate>Tue, 10 Feb 2009 09:49:40 GMT</pubDate>
      <author>chorgeas</author>
      <guid>http://communities.vmware.com/message/1166988</guid>
      <dc:date>2009-02-10T09:49:40Z</dc:date>
      <clearspace:dateToText>9 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>unable to load pxelinux.0 file</title>
      <link>http://communities.vmware.com/message/1155450</link>
      <description>thanks buddy..it worked..awesome.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">studio</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">pcnet</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">issue</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">pxelinux.0</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">file</category>
      <pubDate>Wed, 28 Jan 2009 12:04:21 GMT</pubDate>
      <author>srikanthchouta</author>
      <guid>http://communities.vmware.com/message/1155450</guid>
      <dc:date>2009-01-28T12:04:21Z</dc:date>
      <clearspace:dateToText>10 months, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Studio 1.0 Feature Requests</title>
      <link>http://communities.vmware.com/message/1148056</link>
      <description>Responded &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thomas H. Bryant III&lt;br /&gt;
Director, Advanced Technology &amp;#38; Products&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com"&gt;Vizioncore, Inc.&lt;/a&gt;&lt;br /&gt;
VMware Communities User Moderator</description>
      <pubDate>Mon, 19 Jan 2009 21:29:33 GMT</pubDate>
      <author>kix1979</author>
      <guid>http://communities.vmware.com/message/1148056</guid>
      <dc:date>2009-01-19T21:29:33Z</dc:date>
      <clearspace:dateToText>10 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>Creation of appliance from an existing VM</title>
      <link>http://communities.vmware.com/message/1140459</link>
      <description>Satish, when I first encountered VMware Studio, that's how I expected it would work.  However the design was to require a standard OS and a known set of packages, so the resulting virtual appliance can be fully reproducible, highly portable, and field-updatable.  I don't know if you have noticed, but often when cloning or transporting a virtual machine, many of the local customizations disappear, or things stop working. That is a drawback that VMware Studio strives to solve.  It is possible to imagine easier ways to formulate package dependencies, but for now, we are hoping you understand the trade-off.&lt;br /&gt;
&lt;p /&gt;
A new OVF tool is available, conforming to the 1.0 instead of 0.9 standard.  I think it still does what you want.  &lt;a class="jive-link-external" href="http://www.vmware.com/resources/techresources/1013"&gt;http://www.vmware.com/resources/techresources/1013&lt;/a&gt;</description>
      <pubDate>Fri, 09 Jan 2009 21:46:10 GMT</pubDate>
      <author>tut</author>
      <guid>http://communities.vmware.com/message/1140459</guid>
      <dc:date>2009-01-09T21:46:10Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Create a signed OVA from Studio's OVF files?</title>
      <link>http://communities.vmware.com/message/1140505</link>
      <description>Thanks Tut.&lt;br /&gt;
&lt;br /&gt;
The self-signed cert created by Studio is destined for use by the end user.&lt;br /&gt;
&lt;br /&gt;
The cert needed to sign an OVA is the appliance creators and should not be self-signed.&lt;br /&gt;
&lt;br /&gt;
I'll post in the Converter forum to find out if that can validate &amp;#38; convert a signed OVA let alone create one.&lt;br /&gt;
&lt;br /&gt;
Best,&lt;br /&gt;
&lt;p /&gt;
/Will</description>
      <pubDate>Fri, 09 Jan 2009 22:42:26 GMT</pubDate>
      <author>Will DeHaan</author>
      <guid>http://communities.vmware.com/message/1140505</guid>
      <dc:date>2009-01-09T22:42:26Z</dc:date>
      <clearspace:dateToText>10 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Duplicate disk names</title>
      <link>http://communities.vmware.com/message/1137648</link>
      <description>It boots fine now, after the partition issues and a few other things.  I rebuilt Studio from scratch, made my manual changes to use SLES 10SP2 x86_64, but no support, so no suprise that it builds and the network is DOA when it boots.  Once I can work through that, I can install my BIN files (no RPMs available which sucks) and I have a VA.  All and all it's a bit weird the way everything works and how locked down the app is, but it's a great thing overall.  It has a ton of promise.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
Thomas H. Bryant III&lt;br /&gt;
Director, Advanced Technology &amp;#38; Products&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vizioncore.com"&gt;Vizioncore, Inc.&lt;/a&gt;&lt;br /&gt;
VMware Communities User Moderator</description>
      <pubDate>Wed, 07 Jan 2009 03:58:46 GMT</pubDate>
      <author>kix1979</author>
      <guid>http://communities.vmware.com/message/1137648</guid>
      <dc:date>2009-01-07T03:58:46Z</dc:date>
      <clearspace:dateToText>10 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Installing openjdk on ubuntu?  Please help!!!!!</title>
      <link>http://communities.vmware.com/message/1137476</link>
      <description>&lt;br /&gt;
Did you solve the java installation on ubuntu?&lt;br /&gt;
&lt;p /&gt;
I did it successfully in the following way:&lt;br /&gt;
&lt;p /&gt;
 - download the jre (or jdk) bin file from the sun website&lt;br /&gt;
&lt;p /&gt;
 - install it inside the vmware studio&lt;br /&gt;
&lt;p /&gt;
 - make a post-installation script for setting the JAVA_HOME and PATH&lt;br /&gt;
&lt;p /&gt;
 - make a .deb package of the installed jre (or jdk), by using the mkpkg program&lt;br /&gt;
&lt;p /&gt;
 - copy the .deb package into the appliancePackages directory&lt;br /&gt;
&lt;p /&gt;
In this way the java installation is silent and vmware studio is working without problem.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Tue, 06 Jan 2009 22:35:47 GMT</pubDate>
      <author>pinootto</author>
      <guid>http://communities.vmware.com/message/1137476</guid>
      <dc:date>2009-01-06T22:35:47Z</dc:date>
      <clearspace:dateToText>10 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>9</clearspace:replyCount>
    </item>
    <item>
      <title>SLES 10 SP1 support</title>
      <link>http://communities.vmware.com/message/1127299</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;tut wrote:&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
Stefaan, I am sorry to report that VMware has no plans to support SLES 10 SP1 64-bit (nor 32-bit), only SP2 64-bit.  Studio 1.0 supports SLES 10 SP2 32-bit.&lt;br /&gt;
&lt;/div&gt;
&lt;p /&gt;
In this context, "Supports" is the Caps-S definition, meaning "VMware Supported" rather than "can be made to work".&lt;br /&gt;
&lt;p /&gt;
&lt;div class="jive-quote"&gt; &lt;br /&gt;
That is a very interesting post by Will DeHaan!&lt;br /&gt;
&lt;/div&gt;
&lt;p /&gt;
Amusing phrasing as well in the 05 Nov 2008 post, but that's another story. &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":-)" /&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;tut wrote:&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
I really don't know what XML changes would be needed between SLES 10 SP2 and SP1.&lt;br /&gt;
&lt;/div&gt;
&lt;p /&gt;
The &lt;i&gt;XML&lt;/i&gt; changes would likely be limited to a different MD5sum value, and some package version data.&lt;br /&gt;
&lt;p /&gt;
The &lt;i&gt;other&lt;/i&gt; changes would be the tougher part, given that the VMware Studio VA specific packages (VMware Tools, web management, instrumentation) built for SLES 10 SP2 may not be directly compatible with SLES10 SP1/x86_64.</description>
      <pubDate>Thu, 18 Dec 2008 12:42:45 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1127299</guid>
      <dc:date>2008-12-18T12:42:45Z</dc:date>
      <clearspace:dateToText>11 months, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>VMware Studio with VMware Server 2.0</title>
      <link>http://communities.vmware.com/message/1119784</link>
      <description>No, except insofar as you could have a computer with dual-boot, one with Linux or Windows running VMware Server 2.0, the other with Linux or Windows running VMware Server 1.0.6.  Sorry.&lt;br /&gt;
&lt;br /&gt;
Actually, Server 1.0.x is required for provisioning.  You can run VMware Studio on other VMware products, such as Workstation 6.5, and provision on a remote VMware Server 1.0.6.</description>
      <pubDate>Tue, 09 Dec 2008 21:05:51 GMT</pubDate>
      <author>tut</author>
      <guid>http://communities.vmware.com/message/1119784</guid>
      <dc:date>2008-12-09T21:05:51Z</dc:date>
      <clearspace:dateToText>11 months, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>MD5 and custom ISOs to use as the OS</title>
      <link>http://communities.vmware.com/message/1116498</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;tut wrote:&lt;/span&gt;&lt;br /&gt;
Satish,&lt;br /&gt;
&lt;p /&gt;
I would not recommend that.&lt;br /&gt;
&lt;p /&gt;
The Ubuntu (and other Linux) operating systems are already fairly stripped-down&lt;br /&gt;
and JeOS like.  In the documentation, &lt;i&gt;Guide to Building and Implementing Virtual Appliances&lt;/i&gt;,&lt;br /&gt;
note the use of JeOS in Figure 1-2.&lt;/div&gt;
&lt;p /&gt;
To expand on this some...&lt;br /&gt;
&lt;br /&gt;
The current structure of VMware Studio (i.e., version 1.0) is such that we are reliant on a very specific kernel package for each Supported Guest OS Template in order to install things such as VMware Tools components. We do not recompile the components "on-the-fly" during VA provisioning.&lt;br /&gt;
&lt;p /&gt;
The primary reasoning for using a "respun" ISO image based on an existing Supported Guest OS Template is to include updated OS level packages (a la "slipstreaming" for Microsoft Windows) rather than have to maintain an archive of updated packages which must be pushed out to the VA in the post-install phase. I have a tough time explaining the tradeoffs of respin vs. standalone archive without a whiteboard, but it can amount to a significant reduction in the volume of data exchanged over the network during VA provisioning, and typically a reduction in the overall provisioning time as well.&lt;br /&gt;
&lt;p /&gt;
I do have a nice hands-on example including the archive methodology, but haven't yet had an opportunity since VMworld to finalize it for public consumption.</description>
      <pubDate>Fri, 05 Dec 2008 10:11:17 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1116498</guid>
      <dc:date>2008-12-05T10:11:17Z</dc:date>
      <clearspace:dateToText>11 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>VMWARE studio with VMWARE server</title>
      <link>http://communities.vmware.com/message/1115246</link>
      <description>&lt;br /&gt;
Hi,&lt;br /&gt;
&lt;p /&gt;
quick update - &lt;br /&gt;
&lt;p /&gt;
I was able to debug the problem I was facing.&lt;br /&gt;
&lt;p /&gt;
The problem I was facing was because of the combination of the following:&lt;br /&gt;
&lt;p /&gt;
1) Firewall was coming in the way of communication between Studio and the system hosting the VMWARE Server (for SSH).&lt;br /&gt;
&lt;p /&gt;
2) User accounts between SSH server and the system weren't synchronized properly.&lt;br /&gt;
&lt;p /&gt;
 Thanks for the suggestions.&lt;br /&gt;
&lt;p /&gt;
-Satish&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Thu, 04 Dec 2008 09:08:22 GMT</pubDate>
      <author>satishkn</author>
      <guid>http://communities.vmware.com/message/1115246</guid>
      <dc:date>2008-12-04T09:08:22Z</dc:date>
      <clearspace:dateToText>11 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>6</clearspace:replyCount>
    </item>
    <item>
      <title>Could not find kernel image: ubuntu-installer/i386/linux</title>
      <link>http://communities.vmware.com/message/1106484</link>
      <description>Currently VMware Studio doesn&amp;rsquo;t support building an&lt;br /&gt;
appliance without VMware tools and the embedded management agent. Theoretically&lt;br /&gt;
the end user can tweak the profile and control the tasks and customization that&lt;br /&gt;
are specific to the OS. This is controlled in the &amp;lt;Section&lt;br /&gt;
xsi:type="vadk:JEOSSection_Type"&amp;gt; element of the profile. As I mentioned&lt;br /&gt;
before, customizing this element is not officially supported by VMware Studio&lt;br /&gt;
but feel free to explore and customize for your needs. &lt;br /&gt;
&lt;br /&gt;
We are exploring a way for users to use a newer minor version&lt;br /&gt;
of the OS, without waiting for a newer version of VMware Studio.&lt;br /&gt;
&lt;br /&gt;
Which version of the OS is critical for you at the moment?</description>
      <pubDate>Sun, 23 Nov 2008 20:56:16 GMT</pubDate>
      <author>dannyh</author>
      <guid>http://communities.vmware.com/message/1106484</guid>
      <dc:date>2008-11-23T20:56:16Z</dc:date>
      <clearspace:dateToText>1 year, 1 day ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>module vmxnet not found</title>
      <link>http://communities.vmware.com/message/1103125</link>
      <description>&lt;br /&gt;
Thank you.  I thought I had followed the URL that was given in the guide.  I guess not.  I will give it a try and let you know.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
thanks, again.</description>
      <pubDate>Wed, 19 Nov 2008 15:36:47 GMT</pubDate>
      <author>brent_ski</author>
      <guid>http://communities.vmware.com/message/1103125</guid>
      <dc:date>2008-11-19T15:36:47Z</dc:date>
      <clearspace:dateToText>1 year, 6 days ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>build [error] ISO image checksum match failed for CentOS-5.2-i386-bin-DVD.iso</title>
      <link>http://communities.vmware.com/message/1097622</link>
      <description>To get around you can put a null value in your /opt/vmware/etc/build/templates/your/distro/build_profile.xml    if you do not care about the checksum being correct.  Search the file for md5sum and then delete the value from between the quotes.</description>
      <pubDate>Wed, 12 Nov 2008 21:01:37 GMT</pubDate>
      <author>brent_ski</author>
      <guid>http://communities.vmware.com/message/1097622</guid>
      <dc:date>2008-11-12T21:01:37Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Communication with the virtual machine may have been interrupted</title>
      <link>http://communities.vmware.com/message/1094058</link>
      <description>&lt;br /&gt;
Is this problem reproducible?&lt;br /&gt;
&lt;p /&gt;
If yes, try building the appliance again via command line and this time with the --debug flag so that the transient vm is being kept for debugging.&lt;br /&gt;
&lt;p /&gt;
  studiocli -v --debug -c -p /opt/vmware/var/lib/build/profiles/&amp;lt;yourprofile.xml&amp;gt;&lt;br /&gt;
&lt;p /&gt;
When the build stops with the same failure, open a VMware Server console and connect to 10.0.0.12 along with the same login/pw that you entered in the build profile, then try to launch the targeted transient vm under /tmp. If this test also fails, that probably means the login that you use for the VMware Server isn't adequate for the operation. You want to use an user that can pass this test.</description>
      <pubDate>Fri, 07 Nov 2008 20:13:02 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1094058</guid>
      <dc:date>2008-11-07T20:13:02Z</dc:date>
      <clearspace:dateToText>1 year, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Windows appliances for intra-company use</title>
      <link>http://communities.vmware.com/message/1094042</link>
      <description>&lt;br /&gt;
Windows support is in the roadmap. &lt;br /&gt;
&lt;p /&gt;
Stay tuned, &lt;br /&gt;
&lt;p /&gt;
Komal&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliance</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">iis</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">sql_server</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">windows</category>
      <pubDate>Fri, 07 Nov 2008 19:42:24 GMT</pubDate>
      <author>Komal Mangtani</author>
      <guid>http://communities.vmware.com/message/1094042</guid>
      <dc:date>2008-11-07T19:42:24Z</dc:date>
      <clearspace:dateToText>1 year, 2 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Studio Network Configuration, Server Requirement</title>
      <link>http://communities.vmware.com/message/1087301</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;JMills wrote:&lt;/span&gt;&lt;br /&gt;
&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;nick.couchman wrote:&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;ul class="jive-dash"&gt;
&lt;li&gt;The network configuration on the appliance build is very, very limited.&lt;/li&gt;
&lt;/ul&gt;
The ONLY Server 1.x machine that I have here does not have it's bridged&lt;br /&gt;
network interface set up on vmnet0, which causes all of the builds to&lt;br /&gt;
fail because the newly built ((transient)) appliance can't communicate&lt;br /&gt;
with the Studio ((authoring environment)) server.  Maybe someone knows&lt;br /&gt;
a way to edit the XML file and put in parameters that will allow me&lt;br /&gt;
to use interfaces other than vmnet0 and vmnet1?&lt;/div&gt;
&lt;p /&gt;
&lt;p /&gt;
I will look into how (and where) "bridged" "host-only" and "nat" are translated&lt;br /&gt;
during a VA provisioning cycle, I don't recall that section of code off the top of&lt;br /&gt;
my head. In the VA profile itself, we're still using textual representations rather&lt;br /&gt;
than explicit vmnet# virtual switch numbers.&lt;/div&gt;
&lt;p /&gt;
Unfortunately the mapping between textual representations and explicit vmnet# virtual switch numbers ("bridged" (vmnet0), "hostonly" (vmnet1), and "nat" (vmnet8)) is handled in multiple locations (some deep within the core of our current codebase). Altering this behavior (e.g., to remap "bridged" to vmnet9) would not be as simple as applying a patch to the VMware Studio runtime scripts.</description>
      <pubDate>Thu, 30 Oct 2008 01:27:34 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1087301</guid>
      <dc:date>2008-10-30T01:27:34Z</dc:date>
      <clearspace:dateToText>1 year, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Getting Started with VMWare Studio</title>
      <link>http://communities.vmware.com/message/1079666</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;JMills wrote:&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
The provisioning target will also need an ssh daemon running in the Host OS capable of handling inbound scp and ssh requests -- I'll hunt down a cross-reference for one particular ssh daemon for Win32. &lt;/div&gt;
&lt;br /&gt;
&lt;a class="jive-link-external" href="http://www.vmware.com/support/developer/studio/index.html"&gt;http://www.vmware.com/support/developer/studio/index.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
... Documentation&lt;br /&gt;
... Guide to Building and Implementing Virtual Appliances (URL) -- Information about how to build virtual appliances using VMware Studio.&lt;br /&gt;
&lt;br /&gt;
At page 41, there is a quick run-through of a Win32 ssh daemon implementation -- Appendix A: Installing SSH on Windows.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">getting</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">started</category>
      <pubDate>Tue, 21 Oct 2008 02:05:40 GMT</pubDate>
      <author>JMills</author>
      <guid>http://communities.vmware.com/message/1079666</guid>
      <dc:date>2008-10-21T02:05:40Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Validation fails not finding bootable partition</title>
      <link>http://communities.vmware.com/message/1073494</link>
      <description>&lt;div class="jive-quote"&gt;&lt;span class="jive-quote-header"&gt;leong wrote:&lt;/span&gt;&lt;br /&gt;
&lt;p /&gt;
When you use the web console to create profile and build appliances, there is a dependency on how the browser interpretes a given xml (profile). Since both Safari and Firefox (3.x) are not officially supported, it's possible that the problem you're seeing has association with that (interpretation issue)!&lt;/div&gt;
&lt;br /&gt;
I just tried with Firefox 2.0.0.17 on the same OS X machine, and it validates fine. So it does appear that it's an issue with Safari and Firefox 3.x. Good to know what is causing the problem.&lt;br /&gt;
&lt;br /&gt;
Thanks for your help, leong!&lt;br /&gt;
&lt;br /&gt;
Paul</description>
      <pubDate>Mon, 13 Oct 2008 18:37:04 GMT</pubDate>
      <author>Paul_Chen</author>
      <guid>http://communities.vmware.com/message/1073494</guid>
      <dc:date>2008-10-13T18:37:04Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Hacking VMware Studio</title>
      <link>http://communities.vmware.com/message/1072037</link>
      <description>&lt;br /&gt;
Hey folks I've been using VMware Studio with great success at work. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
At present I'm integrating Studio's command line interfaces into an automated build and test system and have modified appliance payloads, built with custom ISO images and more.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
I'm documenting some of the tweaks I've made over on a blog site and am soliciting questions about using Studio. It's really flexible just by modifying XML and XSL configuration and template files--I'm impressed. &lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Blog is here:  &lt;a class="jive-link-external" href="http://vmwstudio.blogspot.com/"&gt;http://vmwstudio.blogspot.com/&lt;/a&gt;&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Best,&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Will &lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Fri, 10 Oct 2008 19:47:36 GMT</pubDate>
      <author>Will DeHaan</author>
      <guid>http://communities.vmware.com/message/1072037</guid>
      <dc:date>2008-10-10T19:47:36Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
    </item>
    <item>
      <title>VMWare Studio in VMware Fusion?</title>
      <link>http://communities.vmware.com/message/1059657</link>
      <description>&lt;br /&gt;
ESX provisioning is certainly one of the more popular requests and we have taken note about it.</description>
      <category domain="http://communities.vmware.com/tags?communityID=2815">fusion</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">vmware</category>
      <category domain="http://communities.vmware.com/tags?communityID=2815">appliances</category>
      <pubDate>Thu, 25 Sep 2008 19:11:08 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1059657</guid>
      <dc:date>2008-09-25T19:11:08Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>centos 4 support ?</title>
      <link>http://communities.vmware.com/message/1058708</link>
      <description>The runtime components built into the appliances created by VMware Studio have certain dependencies for each version of the Guest OS; and that is the main reason for now it does not claim to be supporting any other OSes than what were listed in the built-in template build profiles. Hope that you can find a workaround for running your app in an CentOS 5 env.</description>
      <pubDate>Thu, 25 Sep 2008 00:31:03 GMT</pubDate>
      <author>leong</author>
      <guid>http://communities.vmware.com/message/1058708</guid>
      <dc:date>2008-09-25T00:31:03Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Read Before Posting</title>
      <link>http://communities.vmware.com/docs/DOC-7721</link>
      <description />
      <pubDate>Sat, 13 Sep 2008 01:52:45 GMT</pubDate>
      <author>Tubo</author>
      <guid>http://communities.vmware.com/docs/DOC-7721</guid>
      <dc:date>2008-09-13T01:52:45Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Welcome to the VMware Studio Communities Forum</title>
      <link>http://communities.vmware.com/docs/DOC-7720</link>
      <description>&lt;br&gt;Welcome to the VMware Studio 1.0 Communities Forum. This interactive portal is designed to serve as a resource to VMware Studio customers, software developers and hardware appliance vendors. Your comments, suggestions and input are very important to the continued success of VMware Studio!&lt;/br&gt;
&lt;br&gt;To begin, familiarize yourself with our &lt;a href="http://readbeforeposting.vmware.com"&gt;Read Before Posting&lt;/a&gt; page, then browse our list of participant entries below. Select the subject heading to read the posting and click &lt;b&gt;Reply&lt;/b&gt; to post a comment. To add content, select one of the action items on the left of this page. Feel free to browse, post and discuss issues relevant to VMware Studio. Product support documentation will be uploaded to this site periodically.&lt;/br&gt;
&lt;br&gt; VMware Studio is available as a free &lt;a href="http://wcm.vmware.com/download/va_authoring/"&gt;download&lt;/a&gt;. Additional information about VMware Studio 1.0 can be obtained on the &lt;a href="http://www.vmware.com/appliances/learn/studio/overview.html"&gt;VMware Studio product web page&lt;/a&gt;, the &lt;a href="http://www.vmware.com/files/pdf/vam/VMware_Virtual_Appliance_Solutions_White_Paper_08Q3.pdf"&gt;Virtual Appliance Solutions White Paper&lt;/a&gt;, the &lt;a href="http://www.vmware.com/files/pdf/vmware_studio_userguide.pdf"&gt;User’s Guide&lt;/a&gt;,  the &lt;a href="http://www.vmware.com/files/pdf/vmware_studio_adminguide.pdf"&gt;Admin Guide,&lt;/a&gt; and the &lt;a href="http://www.vmware.com/support/developer/studio/studio10/studio_relnotes10.html"&gt;Release Notes&lt;/a&gt;.&lt;/br&gt;
&lt;br&gt;Thank you for your participation in the VMware Studio 1.0 Communities Forum!&lt;/br&gt;</description>
      <pubDate>Sat, 13 Sep 2008 01:29:10 GMT</pubDate>
      <author>Tubo</author>
      <guid>http://communities.vmware.com/docs/DOC-7720</guid>
      <dc:date>2008-09-13T01:29:10Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
    </item>
  </channel>
</rss>

