<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Linked Clones are un-linking themselves? in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Linked-Clones-are-un-linking-themselves/m-p/978806#M54669</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I run VMWare Workstation on a Linux External USB drive (Fedora). On that Fedora host I run VMs for school and training. Then whenever I plug that External drive into my Windows host at home and load up a linked clone it naturally complains that it cannot find its base image. When i direct it to that image it seems to take additional steps to create a &lt;STRONG&gt;****-cl1.vmdk&lt;/STRONG&gt; file. This file is 5-15gb and as the external drive as a SSD its a bit annoying. What is causing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your time,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 24 Nov 2013 20:02:31 GMT</pubDate>
    <dc:creator>AdamTher</dc:creator>
    <dc:date>2013-11-24T20:02:31Z</dc:date>
    <item>
      <title>Linked Clones are un-linking themselves?</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Linked-Clones-are-un-linking-themselves/m-p/978806#M54669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I run VMWare Workstation on a Linux External USB drive (Fedora). On that Fedora host I run VMs for school and training. Then whenever I plug that External drive into my Windows host at home and load up a linked clone it naturally complains that it cannot find its base image. When i direct it to that image it seems to take additional steps to create a &lt;STRONG&gt;****-cl1.vmdk&lt;/STRONG&gt; file. This file is 5-15gb and as the external drive as a SSD its a bit annoying. What is causing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your time,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 24 Nov 2013 20:02:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Linked-Clones-are-un-linking-themselves/m-p/978806#M54669</guid>
      <dc:creator>AdamTher</dc:creator>
      <dc:date>2013-11-24T20:02:31Z</dc:date>
    </item>
  </channel>
</rss>

