<?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>plamen_d Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>plamen_d Tracker</description>
    <pubDate>Wed, 15 Nov 2023 13:11:47 GMT</pubDate>
    <dc:date>2023-11-15T13:11:47Z</dc:date>
    <item>
      <title>Re: RHEL 8.FAILED: An error occurred during the conversion: 'Grubinstaller:</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/RHEL-8/m-p/2995757#M44525</link>
      <description>&lt;P&gt;Converter 6.4 can't convert RHEL 8. It is planned for the next release.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Nov 2023 08:27:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/RHEL-8/m-p/2995757#M44525</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-11-15T08:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: vcenter converter stand alone trying to make vm of a existing installation on D drive</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vcenter-converter-stand-alone-trying-to-make-vm-of-a-existing/m-p/2995231#M44523</link>
      <description>&lt;P&gt;I am not sure this will work, but it is worth trying.&lt;BR /&gt;Clone the whole disk. If you have some other program to make an image of the whole disk and then a VM from it, even better. If not - try with Converter - all volumes in &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@B699825BEA7B9353BA12C688F8C7000B/emoticons/1f627.png" alt=":anguished_face:" title=":anguished_face:" /&gt; and deselect reconfiguration.&lt;BR /&gt;Configure machine is nothing special from a user's point of view; just select the VM you have created.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Nov 2023 16:43:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vcenter-converter-stand-alone-trying-to-make-vm-of-a-existing/m-p/2995231#M44523</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-11-11T16:43:41Z</dc:date>
    </item>
    <item>
      <title>Re: vcenter converter stand alone trying to make vm of a existing installation on D drive</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vcenter-converter-stand-alone-trying-to-make-vm-of-a-existing/m-p/2995164#M44520</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;This is a bit strange case. You may try conversion of your machine (e.g. install Converter in it and convert 'this local machine') but then select only &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@B699825BEA7B9353BA12C688F8C7000B/emoticons/1f627.png" alt=":anguished_face:" title=":anguished_face:" /&gt; drive and deselect reconfiguration. After the cloning completes, run c 'Configure machine' on the cloned VM. And cross fingers &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Fri, 10 Nov 2023 18:18:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vcenter-converter-stand-alone-trying-to-make-vm-of-a-existing/m-p/2995164#M44520</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-11-10T18:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: Does vCenter Converter Standalone allow for commercial free use?</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Does-vCenter-Converter-Standalone-allow-for-commercial-free-use/m-p/2993501#M44513</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Converter Standalone is free as in free beer, but it is not free software (as in free speech). It has an EULA that you can see when starting the installer. You can check any details you need there.&lt;BR /&gt;Yes, it is allowed for commercial use; in fact the majority of customers that use it are for profit companies.&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 12:39:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Does-vCenter-Converter-Standalone-allow-for-commercial-free-use/m-p/2993501#M44513</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-10-31T12:39:22Z</dc:date>
    </item>
    <item>
      <title>Re: VCenter Converter</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/VCenter-Converter/m-p/2993185#M44505</link>
      <description>&lt;P&gt;Yes,&lt;/P&gt;&lt;P&gt;If the machine is Windows, Converter will install an Agent service and that's the only change to the physical machine. By default, it will uninstall it automatically after conversion; if it doesn't, you may always uninstall it manually.&lt;BR /&gt;For Linux, Converter deploys a small utility - sysinfo that gathers source information and, deletes it immediately afterwards; so no changes there.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 19:37:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/VCenter-Converter/m-p/2993185#M44505</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-10-28T19:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: V2P converter 6.4 error</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/V2P-converter-6-4-error/m-p/2987167#M44449</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;There is an error in worker's log when it attempts to connect to the agent on the source machine.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2023-09-14T21:04:23.352-07:00 warning vmware-converter-worker[07704] [Originator@6876 sub=IO.Connection] Failed to connect; &amp;lt;io_obj p:0x06b56110, h:1716, &amp;lt;TCP '0.0.0.0 : 63177'&amp;gt;, &amp;lt;TCP '10.11.0.25 : 9089'&amp;gt;&amp;gt;, e: 10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond), duration: 21004msec&lt;/LI-CODE&gt;&lt;P&gt;Note that the agent listens on port 9089, which may well be blocked by a firewall (e.g. the source machine's one).&lt;/P&gt;&lt;P&gt;It is possible to configure the agent to listen on a different port. Edit "%ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone\converter-agent.xml" on the source machine and look for "&amp;lt;soapPort&amp;gt;9089&amp;lt;/soapPort&amp;gt;" in it. Restart the service "VMware vCenter Converter Standalone Agent" after that. In this case you will need to add the port in the wizard the wizard, see &lt;A href="https://docs.vmware.com/en/vCenter-Converter-Standalone/6.4/vcenter-converter/GUID-3C28F188-1A2C-4B32-8C2F-06C63B453DF3.html?hWord=N4IghgNiBc4OYFMB2AXABABwPYCcUgF8g" target="_self"&gt;Select a Powered On Windows Machine to Convert&lt;/A&gt;&lt;/P&gt;&lt;P&gt;There is another error in server's log which looks weird:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2023-09-14T21:04:23.357-07:00 warning vmware-converter-server[04924] [Originator@6876 sub=vmomi.soapStub[0]] SOAP request returned HTTP failure; &amp;lt;&amp;lt;io_obj p:0x080874f0, h:2092, &amp;lt;pipe '\\.\pipe\vmware-converter-worker-soap'&amp;gt;, &amp;lt;pipe '\\.\pipe\vmware-converter-worker-soap'&amp;gt;&amp;gt;, /converter/sdk&amp;gt;, method: validateAgentAvailability; code: 500(Internal Server Error)&lt;/LI-CODE&gt;&lt;P&gt;No idea why this is so.&lt;/P&gt;&lt;P&gt;An alternative could be to install Converter server on the source machine and then do a conversion of "this local machine".&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Mon, 18 Sep 2023 17:56:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/V2P-converter-6-4-error/m-p/2987167#M44449</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-09-18T17:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Connect ISO to Remote VM</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-Connect-ISO-to-Remote-VM/m-p/2985713#M44439</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;It may be a network configuration issue. Starting with ESXi 8.0, connecting the helper ISO uses HTTPS and requires Converter server to access port 443 on the ESX host, instead of port 902 as it is for earlier versions; see &lt;A href="https://docs.vmware.com/en/vCenter-Converter-Standalone/6.4/vcenter-converter/GUID-4814B6B2-12A4-4E66-9B43-F1394F9E7433.html?hWord=N4IghgNiBcIA4HsBOAXAziAvkA" target="_blank"&gt;https://docs.vmware.com/en/vCenter-Converter-Standalone/6.4/vcenter-converter/GUID-4814B6B2-12A4-4E66-9B43-F1394F9E7433.html?hWord=N4IghgNiBcIA4HsBOAXAziAvkA&lt;/A&gt;&lt;/P&gt;&lt;P&gt;However, keep in mind that Ubuntu 20 is not supported by Converter 6.4. Even if the cloning succeeds, the reconfiguration will fail and the converted VM won't be able to boot. You may need to manually install GRUB, create the initramfs image, create an EFI boot entry, patch fstab and network files, etc.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Thu, 07 Sep 2023 13:39:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-Connect-ISO-to-Remote-VM/m-p/2985713#M44439</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-09-07T13:39:24Z</dc:date>
    </item>
    <item>
      <title>Re: Using vCenter Standalone 6.4  to convert Server 2016 to vmWare Fusion instance on a ext USB driv</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Using-vCenter-Standalone-6-4-to-convert-Server-2016-to-vmWare/m-p/2982123#M44421</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;Yes, the USB E: drive should be excluded from conversion. Otherwise, surely, there will a recursive copying resulting in eating up all the space. However, external drives are usually excluded automatically from conversion. To be in the safe side, you may check that in the 'disks-and-volumes' tab in conversion wizard's 'options' page.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 06:35:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Using-vCenter-Standalone-6-4-to-convert-Server-2016-to-vmWare/m-p/2982123#M44421</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-08-14T06:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: RHEL 4: Unable to query the live Linux source machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/RHEL-4-Unable-to-query-the-live-Linux-source-machine/m-p/2977722#M44405</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Unfortunately, since Converter 6.3, RHEL 4 and 5 cannot be converted anymore due to updated 3rd party components for security reasons. For the same reasons versions older than 6.3 are removed from downloads. If you can find 6.2 or an older version from somewhere, it should work.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jul 2023 10:25:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/RHEL-4-Unable-to-query-the-live-Linux-source-machine/m-p/2977722#M44405</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-07-17T10:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: vmware converter 6.4 can't connect to vCenter 7.0.3 nor ESXi 6.7</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-can-t-connect-to-vCenter-7-0-3-nor-ESXi-6-7/m-p/2971823#M44369</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;V2V conversions (from vCenter to vCenter, and w/o touching the source OS) work with the source VM powered off. The source type is called "VMware Infrastructure virtual machine"&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 12:29:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-can-t-connect-to-vCenter-7-0-3-nor-ESXi-6-7/m-p/2971823#M44369</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-06-06T12:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: vmware converter 6.4 connect windows host routines:ssl3_read_bytes:tlsv1 alert internal error</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-connect-windows-host-routines-ssl3-read/m-p/2971822#M44368</link>
      <description>&lt;P&gt;The default RDP port is 3389. But everything is well when it finishes well &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 12:25:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-connect-windows-host-routines-ssl3-read/m-p/2971822#M44368</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-06-06T12:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter converter standalone 6.2 - Error with convert  CentOs 7</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vCenter-converter-standalone-6-2-Error-with-convert-CentOs-7/m-p/2971819#M44366</link>
      <description>&lt;P&gt;It might be some firewall on the path, not in the components specifically. This is the only think I can think of with such a bug delay.&lt;/P&gt;&lt;P&gt;Try to connect from Converter server machine to a VM in the destination virtual network on port 443 to validate that everything is fine.&lt;BR /&gt;You may also try with Converter 6.4. Never mind it's ESX 6.7, it should work.&lt;BR /&gt;Another thing is to attach the logs.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 12:22:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vCenter-converter-standalone-6-2-Error-with-convert-CentOs-7/m-p/2971819#M44366</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-06-06T12:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: vmware converter 6.4 connect windows host routines:ssl3_read_bytes:tlsv1 alert internal error</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-connect-windows-host-routines-ssl3-read/m-p/2971561#M44361</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;It is strange that the port is 3392. This is not the default Converter Agent port (9089). Is the agent explicitly installed with that listen port?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jun 2023 20:42:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-6-4-connect-windows-host-routines-ssl3-read/m-p/2971561#M44361</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-06-04T20:42:04Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter converter standalone 6.2 - Error with convert  CentOs 7</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vCenter-converter-standalone-6-2-Error-with-convert-CentOs-7/m-p/2971560#M44360</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;It is strange that you had to wait for more than an hour. Normally it times out in 20 min. Apart from that, the usual reason for such failures is lack of network connectivity from Converter server machine to the destination VM. See &lt;A href="https://docs.vmware.com/en/vCenter-Converter-Standalone/6.4/vcenter-converter/GUID-4814B6B2-12A4-4E66-9B43-F1394F9E7433.html?hWord=N4IghgNiBcIA4HsBOAXAziAvkA" target="_blank"&gt;Ports Used When Converting a Powered On Machine Running Linux.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jun 2023 20:19:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vCenter-converter-standalone-6-2-Error-with-convert-CentOs-7/m-p/2971560#M44360</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-06-04T20:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a VM from the Cloud to Local</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-VM-from-the-Cloud-to-Local/m-p/2970498#M44350</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;For the ports, better see the &lt;A href="https://docs.vmware.com/en/vCenter-Converter-Standalone/6.4/vcenter-converter/GUID-4814B6B2-12A4-4E66-9B43-F1394F9E7433.html?hWord=N4IghgNiBcIA4HsBOAXAziAvkA" target="_self"&gt;doc page&lt;/A&gt;, there are some intricacies related to ports to ESXi host (its version, whether it is managed).&lt;/P&gt;&lt;P&gt;Note also that, if you install Converter near the destination (which, as Rohit mentioned, is recommended) you may want to install Converter Agent manually on the source machine even for direct conversion (w/o proxy mode); otherwise SMB related ports need to be open in order to deploy it from Converter machine.&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Fri, 26 May 2023 17:07:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-VM-from-the-Cloud-to-Local/m-p/2970498#M44350</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-05-26T17:07:58Z</dc:date>
    </item>
    <item>
      <title>Re: vmware converter freezing  6.4.0</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-freezing-6-4-0/m-p/2970493#M44349</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have also never heard of such behaviour before, too. Really weird.&lt;/P&gt;&lt;P&gt;Btw that folder is for server logs. The client logs are in:&lt;BR /&gt;"%LOCALAPPDATA%\VMware\VMware vCenter Converter Standalone Client\Logs" (or perhaps "%APPDATA%\VMware\VMware vCenter Converter Standalone Client\Logs" in some installations, not sure)&lt;/P&gt;&lt;P&gt;Hopefully there might be something in it.&lt;/P&gt;</description>
      <pubDate>Fri, 26 May 2023 16:52:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/vmware-converter-freezing-6-4-0/m-p/2970493#M44349</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-05-26T16:52:48Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to create a clone of my Virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-create-a-clone-of-my-Virtual-machine/m-p/2969703#M44330</link>
      <description>&lt;P&gt;Hi Frank&lt;/P&gt;&lt;P&gt;Then it really looks like some disk corruption. You might want to run chkdsk / fschk inside the GOS and in Workstation where the VM is.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 19:27:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-create-a-clone-of-my-Virtual-machine/m-p/2969703#M44330</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-05-22T19:27:37Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to create a clone of my Virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-create-a-clone-of-my-Virtual-machine/m-p/2969658#M44328</link>
      <description>&lt;P&gt;It is the first time I see such an error. It may indeed be an issue with the source disk.&lt;/P&gt;&lt;P&gt;On the other hand, Linux V2V just copies the files, it doesn't reconfigure. So you may just copy the whole VM directory instead of using Converter.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 14:40:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-create-a-clone-of-my-Virtual-machine/m-p/2969658#M44328</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-05-22T14:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to create a clone of my Virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-create-a-clone-of-my-Virtual-machine/m-p/2969644#M44325</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The error from the log reads:&lt;/P&gt;&lt;P&gt;2023-05-22T05:10:39.997-04:00 error vmware-converter-worker[19088] [Originator@6876 sub=task-24] Sysimgbase_DiskLib_Clone failed in H2HDiskCloneMgr with error 'Data error (cyclic redundancy check)' (error code:1507337)&lt;/P&gt;&lt;P&gt;It is kind of strange to get a CRC erro. Is it a reproducible issue or a one-timer?&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 13:29:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Failed-to-create-a-clone-of-my-Virtual-machine/m-p/2969644#M44325</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-05-22T13:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to convert a Win XP machine to a VM in 2023</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/How-to-convert-a-Win-XP-machine-to-a-VM-in-2023/m-p/2952098#M44210</link>
      <description>&lt;P&gt;Have you tried installing only Converter Agent on the XP machine (and the server somewhere else, on a newer Windows)? I am not sure whether it will work; Windows 2000 won't but XP might.&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 09:44:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/How-to-convert-a-Win-XP-machine-to-a-VM-in-2023/m-p/2952098#M44210</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-02-02T09:44:34Z</dc:date>
    </item>
  </channel>
</rss>

