<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Looking for the paradigm &#187; updated</title>
	<atom:link href="http://www.evanhoffman.com/evan/tag/updated/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.evanhoffman.com/evan</link>
	<description>So I can pass it off</description>
	<lastBuildDate>Thu, 26 Jan 2012 22:17:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Exporting VMWare Server VMs to OVA/OVF with ovftool</title>
		<link>http://www.evanhoffman.com/evan/2009/09/11/exporting-vmware-server-vms-to-ovaovf-with-ovftoo/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=exporting-vmware-server-vms-to-ovaovf-with-ovftoo</link>
		<comments>http://www.evanhoffman.com/evan/2009/09/11/exporting-vmware-server-vms-to-ovaovf-with-ovftoo/#comments</comments>
		<pubDate>Fri, 11 Sep 2009 22:56:25 +0000</pubDate>
		<dc:creator>Evan Hoffman</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[ovftool]]></category>
		<category><![CDATA[updated]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://www.evanhoffman.com/evan/?p=161</guid>
		<description><![CDATA[TweetWell, I thought this was going to be a huge pain in the ass, but it turns out not to be a really big deal. I found this post which includes instructions and a link to download VMWare&#8217;s &#8220;ovftool&#8221;. There&#8217;s a win32 version and a 32-bit and 64-bit linux version: -rwxr--r-- 1 evan evan 19326184 [...]]]></description>
			<content:encoded><![CDATA[<div style="vertical-align: top; float: right; margin-left: 10px;"><a href="http://twitter.com/share?url=http://www.evanhoffman.com/evan/2009/09/11/exporting-vmware-server-vms-to-ovaovf-with-ovftoo/&via=EvanHoffman&text=Exporting VMWare Server VMs to OVA/OVF with ovftool&related=EvanHoffman:&lang=en&count=horizontal" class="twitter-share-button">Tweet</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script></div><div class="plus-one-wrap"><g:plusone size="small" href="http://www.evanhoffman.com/evan/2009/09/11/exporting-vmware-server-vms-to-ovaovf-with-ovftoo/"></g:plusone></div><p>Well, I thought this was going to be a huge pain in the ass, but it turns out not to be a really big deal.  I found <a href="http://www.thoughtpolice.co.uk/vmware/howto/create-and-convert-ovf-files.html">this post</a> which includes instructions and a link to download VMWare&#8217;s &#8220;ovftool&#8221;.  There&#8217;s a win32 version and a 32-bit and 64-bit linux version:</p>
<p><span id="more-161"></span></p>

<div class="wp_syntax"><div class="code"><pre class="txt" style="font-family:monospace;">-rwxr--r-- 1 evan evan 19326184 Sep 11 17:16 VMware-ovftool-installer-1.0.0-166674-lin.i386.sh*
-rwxr--r-- 1 evan evan 17212108 Sep 11 17:16 VMware-ovftool-installer-1.0.0-166674-lin.x86_64.sh*
-rwxr-xr-x 1 evan evan 43833393 Sep 11 17:33 jdk-1_5_0_13-linux-amd64.bin*</pre></div></div>

<p>I installed JDK 1.5.0_r13 because that&#8217;s what I had laying around.  The 64-bit installer for ovftool ran without a hitch.  I haven&#8217;t yet tried importing the .ova to my vCenter cluster (the export was from our Vmware Server (free) environment) but the conversion itself seemed fine.  The one problem I encountered was that it was complaining that the cdrom was connected.  The VM in question had an ISO configured as its cdrom drive, but it wasn&#8217;t connected, yet the ovftool still complained about it.  I shutdown the VM, deleted the device completely, and then the conversion went fine.</p>

<div class="wp_syntax"><div class="code"><pre class="txt" style="font-family:monospace;">[root@thardus ~]# /opt/vmware/ovftool/ovftool /nfsroot/VM/Monitoring/Monitoring.vmx /nfsroot/OVF/test.ova
Opening VMX source: /nfsroot/VM/Monitoring/Monitoring.vmx
Opening OVA target: /nfsroot/OVF/test.ova
Target: /nfsroot/OVF/test.ova
Disk Transfer Completed
Completed successfully</pre></div></div>

<p>The whole thing took about 10-15 minutes I guess for a 20 gig VM.  Actually that&#8217;s another interesting thing: the source directory with the VMDKs was ~20 gigs:</p>

<div class="wp_syntax"><div class="code"><pre class="txt" style="font-family:monospace;">[root@thardus ~]# du -sh /nfsroot/VM/Monitoring/
21G     /nfsroot/VM/Monitoring/</pre></div></div>

<p>But the OVA that was created was only 2.5 gigs.</p>

<div class="wp_syntax"><div class="code"><pre class="txt" style="font-family:monospace;">[root@thardus ~]# ls -lh /nfsroot/OVF/test.ova
-rw------- 1 root root 2.5G Sep 11 18:45 /nfsroot/OVF/test.ova</pre></div></div>

<p>I assume this is due to compression and only including the parts of the VMDK that have actual data (basically thinly provisioning it).  I haven&#8217;t restored yet, which would be the real test, but so far it looks like it&#8217;s a pretty easy tool that does what it&#8217;s supposed to.</p>
<p><b>Update 2009-11-25</b>: With the current version of ovftool you can&#8217;t create .ova files with ovftool for VMDKs larger than 8 gb.  See <a href="http://communities.vmware.com/message/1409396#1409396">this post on the VMware forums</a> for more info.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.evanhoffman.com/evan/2009/09/11/exporting-vmware-server-vms-to-ovaovf-with-ovftoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

