<?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: Message List - Partition Alignment - Significant when converting Workstation VMs?</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esxi3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Fri, 26 Jun 2009 21:59:49 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-06-26T21:59:49Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Partition Alignment - Significant when converting Workstation VMs?</title>
      <link>http://communities.vmware.com/message/1296363?tstart=0#1296363</link>
      <description>Nice thought, but you are giving way too much credit to the design of a VM.  It's basically like a static zip file with files in it.  It may be a file system that hosts a series of files of those 'zips' but what happens inside the zip is basically up to the guest OS.  The only difference in format is the header information for reading vmdk flat files, otherwise they are pretty much the same.&lt;br /&gt;
&lt;br /&gt;
You shouldn't get bogged down with partition info as this is handled by converter, and you won't have issue by moving them over to ESX.  Partition alignment is handled by converter.&lt;br /&gt;
&lt;br /&gt;
So you can't just move a vmdk and copy it to ESX, it would still need to be converted, so this is made easy by using VM Converter to convert a stand alone VM and using the ESX as the target.</description>
      <pubDate>Fri, 26 Jun 2009 21:55:18 GMT</pubDate>
      <author>RParker</author>
      <guid>http://communities.vmware.com/message/1296363?tstart=0#1296363</guid>
      <dc:date>2009-06-26T21:55:18Z</dc:date>
      <clearspace:dateToText>4 months, 4 weeks ago</clearspace:dateToText>
    </item>
    <item>
      <title>Partition Alignment - Significant when converting Workstation VMs?</title>
      <link>http://communities.vmware.com/message/1296341?tstart=0#1296341</link>
      <description>&lt;br /&gt;
Believe I finally am able to wrap my mind around why Partition Alignment is not a factor for VMs created by and running on Workstation vs ESX, on Workstation any data partitions would be at or within the file level whereas defined partitions on ESX appear to be fixed and static physical configurations (someone correct me if I'm wrong here).&lt;br /&gt;
&lt;p /&gt;
 If I understand this correctly, then what are the consequences of converting a Workstation VM to run on ESX? It seems to me that any data partitions which might have been running at or within the file level on Workstation could potentially be running in its own partition on ESX. If this is so, can it be assumed that approved VMware utilities automatically configure the beginning of the partition accordingly (assume some multiple of 128 instead of 64)? Or, at least in the case of an OS like *NIX would this concern be irrelevant because the partition type would be Linux instead of VMFS?&lt;br /&gt;
&lt;p /&gt;
 Basically, I'm looking for any gotchas involved when doing a Workstation/ESX conversion, at least on the topic of Partition Alighment there doesn't seem to be any documentation or mention anywhere I can find (but maybe it's just not an issue).&lt;br /&gt;
&lt;p /&gt;
TIA,&lt;br /&gt;
&lt;p /&gt;
Tony</description>
      <pubDate>Fri, 26 Jun 2009 21:20:58 GMT</pubDate>
      <author>Virtually</author>
      <guid>http://communities.vmware.com/message/1296341?tstart=0#1296341</guid>
      <dc:date>2009-06-26T21:20:58Z</dc:date>
      <clearspace:dateToText>4 months, 4 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
  </channel>
</rss>

