<?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 - Disk extents on BC converted VM</title>
    <link>http://communities.vmware.com/community/vmtn/desktop/fusion?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Fri, 29 Feb 2008 01:46:43 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-02-29T01:46:43Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Disk extents on BC converted VM</title>
      <link>http://communities.vmware.com/message/873969?tstart=0#873969</link>
      <description>&lt;div class="jive-quote"&gt;Is there a way to combine all the extents into a single?&lt;/div&gt;
&lt;br /&gt;
You can use vmware-vdiskmanager (or my &lt;a class="jive-link-external" href="http://www.vmware.com/community/thread.jspa?messageID=674493&amp;amp;#674493"&gt;GUI wrapper&lt;/a&gt;) to do this.&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;Should this be a concern?&lt;/div&gt;
&lt;br /&gt;
I wouldn't worry about it - I actually prefer the split disk format for the reasons outlined in &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-2523"&gt;Choosing the Right Virtual Machine Settings&lt;/a&gt; and &lt;a class="jive-link-wiki" href="http://communities.vmware.com/docs/DOC-1110"&gt;A Beginner's Guide to VMware Fusion&lt;/a&gt;</description>
      <pubDate>Fri, 29 Feb 2008 01:46:43 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/873969?tstart=0#873969</guid>
      <dc:date>2008-02-29T01:46:43Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disk extents on BC converted VM</title>
      <link>http://communities.vmware.com/message/873617?tstart=0#873617</link>
      <description>Thank you etung.  Got them in the bundle, no problem.  Is there a way to combine all the extents into a single?  Should this be a concern?</description>
      <pubDate>Fri, 29 Feb 2008 01:10:33 GMT</pubDate>
      <author>todivefor</author>
      <guid>http://communities.vmware.com/message/873617?tstart=0#873617</guid>
      <dc:date>2008-02-29T01:10:33Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disk extents on BC converted VM</title>
      <link>http://communities.vmware.com/message/873111?tstart=0#873111</link>
      <description>&lt;div class="jive-quote"&gt;Also I thought the .vmdk files were supposed to be put in the .vmwarevm bundle?  Is that a manual process?&lt;/div&gt;
&lt;br /&gt;
Fusion is the only VMware product to use .vmwarevm bundles, because OS X is the only OS we run on that understands them. If you create a new virtual machine using an existing disk, the existing disk is not moved. You can move the .vmdk files yourself (you'll also have to fix up the path, either when Fusion gets confused and asks or by hand).</description>
      <pubDate>Thu, 28 Feb 2008 15:30:23 GMT</pubDate>
      <author>etung</author>
      <guid>http://communities.vmware.com/message/873111?tstart=0#873111</guid>
      <dc:date>2008-02-28T15:30:23Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Disk extents on BC converted VM</title>
      <link>http://communities.vmware.com/message/873063?tstart=0#873063</link>
      <description>Thank you MandaMS.  Most of the extents are less than 1G.  Why are they split anyway?  I did not request 2G chunks when I converted.</description>
      <pubDate>Thu, 28 Feb 2008 14:49:23 GMT</pubDate>
      <author>todivefor</author>
      <guid>http://communities.vmware.com/message/873063?tstart=0#873063</guid>
      <dc:date>2008-02-28T14:49:23Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Disk extents on BC converted VM</title>
      <link>http://communities.vmware.com/message/873043?tstart=0#873043</link>
      <description>&lt;br /&gt;
Currently your virtual disk is split in 2GB chunk files that&amp;rsquo;s&lt;br /&gt;
why you can see all .vmdk files from s001 to s017</description>
      <pubDate>Thu, 28 Feb 2008 14:35:08 GMT</pubDate>
      <author>MandarMS</author>
      <guid>http://communities.vmware.com/message/873043?tstart=0#873043</guid>
      <dc:date>2008-02-28T14:35:08Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Disk extents on BC converted VM</title>
      <link>http://communities.vmware.com/message/872993?tstart=0#872993</link>
      <description>Why am I getting all these disk extents (see attached) on my converted BC partition?  Also I thought the .vmdk files were supposed to be put in the .vmwarevm bundle?  Is that a manual process?</description>
      <pubDate>Thu, 28 Feb 2008 14:22:27 GMT</pubDate>
      <author>todivefor</author>
      <guid>http://communities.vmware.com/message/872993?tstart=0#872993</guid>
      <dc:date>2008-02-28T14:22:27Z</dc:date>
      <clearspace:dateToText>1 year, 8 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
  </channel>
</rss>

