<?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 Re: Converting a legacy Redhat physical to a virtual machine in Converter Standalone Discussions</title>
    <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946467#M44154</link>
    <description>&lt;P&gt;I have a 6.2 copy and will give a try.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Jan 2023 14:30:10 GMT</pubDate>
    <dc:creator>tisuportealba</dc:creator>
    <dc:date>2023-01-03T14:30:10Z</dc:date>
    <item>
      <title>Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2945897#M44148</link>
      <description>&lt;P&gt;Cannot convert this machine, an old redhat 4.2 server, because this ssh server is to old. Another host in the destination virtual enviroment only connect through ssh with the option "-oKexAlgorithms=+diffie-hellman-group1-sha1", but i don't know how to force the helper vm to use this same key. This way i got error in this.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;FAILED: A general system error occurred: # 10.0.1.21:22 SSH-1.99-OpenSSH_3.9p1 # 10.0.1.21:22 SSH-1.99-OpenSSH_3.9p1 # 10.0.1.21:22 SSH-1.99-OpenSSH_3.9p1 # 10.0.1.21:&lt;BR /&gt;22 SSH-1.99-OpenSSH_3.9p1 Network error. Host 10.0.1.21 key can't be retrieved. (return code 2)&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Dec 2022 17:29:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2945897#M44148</guid>
      <dc:creator>tisuportealba</dc:creator>
      <dc:date>2022-12-29T17:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2945992#M44149</link>
      <description>&lt;P&gt;I am not sure if you will be able to convert it to VM. really old one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;How big is your Server?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Dec 2022 08:36:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2945992#M44149</guid>
      <dc:creator>maksym007</dc:creator>
      <dc:date>2022-12-30T08:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946425#M44150</link>
      <description>&lt;P&gt;Not so big, but a legacy database. The problem: it's running in a old hardware. We need this db only for query some informations when necessary by regulatories mesures.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think create a virtual clone and turn off this old server.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 11:38:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946425#M44150</guid>
      <dc:creator>tisuportealba</dc:creator>
      <dc:date>2023-01-03T11:38:26Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946437#M44151</link>
      <description>&lt;P&gt;Will you be able to upgrade Red Hat to a bit newest version?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 12:35:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946437#M44151</guid>
      <dc:creator>maksym007</dc:creator>
      <dc:date>2023-01-03T12:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946453#M44152</link>
      <description>&lt;P&gt;No way.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The current version of database doesn't permit ti change SO version. This is a huge problem because the cobol applications does not works in new db versions.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 13:30:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946453#M44152</guid>
      <dc:creator>tisuportealba</dc:creator>
      <dc:date>2023-01-03T13:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946462#M44153</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;This is correct, Converter 6.3 cannot convert RHEL versions prior to 6.&lt;/P&gt;&lt;P&gt;Converter 6.2 can, though. It is not available for download, for security reasons as well (including the one that you hit here), but if have a copy left somewhere, or if someone can hand it to you, it is expected to do the job.&lt;/P&gt;&lt;P&gt;HTH and regards,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 14:06:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946462#M44153</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-01-03T14:06:23Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946467#M44154</link>
      <description>&lt;P&gt;I have a 6.2 copy and will give a try.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 14:30:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946467#M44154</guid>
      <dc:creator>tisuportealba</dc:creator>
      <dc:date>2023-01-03T14:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946499#M44155</link>
      <description>&lt;P&gt;Version 6.2 worked great, thanks. Server converted as espected, but the ASM disks.... &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;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A friend told me about&amp;nbsp;a tool called&amp;nbsp;"&lt;SPAN&gt;VMware Convertor Cold Clone" (discontinued)&amp;nbsp;&lt;/SPAN&gt;&amp;nbsp;that converts a &lt;SPAN&gt;physical&amp;nbsp;&lt;/SPAN&gt;linux system with any raw disks, even not been visible by OS. I'm not sure if true, but..... i will try as soon as possible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for all&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jan 2023 17:16:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946499#M44155</guid>
      <dc:creator>tisuportealba</dc:creator>
      <dc:date>2023-01-03T17:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946877#M44156</link>
      <description>&lt;P&gt;Good to see that it works &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;The old cold clone was for Windows only and it is very old. I'd say - don't bother to look for it.&lt;/P&gt;&lt;P&gt;As for the ASM disks, I am not familiar with these. I guess their block devices may look different and Converter doesn't recognize them. The usual workaround in such cases is to copy the volumes manually, i.e. create new disks in the VM, setup logical volumes if needed, format the volumes, and then use scp, rsync, or whatever your favorite way is. Converter itself uses tar during cloning.&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Plamen&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jan 2023 08:29:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946877#M44156</guid>
      <dc:creator>plamen_d</dc:creator>
      <dc:date>2023-01-05T08:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: Converting a legacy Redhat physical to a virtual machine</title>
      <link>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946930#M44160</link>
      <description>&lt;P&gt;I will no longer use "Cold Clone" because it is too old. You are right. Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately I will have to leave for a plan "B". MIgrate the old db to a new one, schema by schema....&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jan 2023 12:33:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Converter-Standalone-Discussions/Converting-a-legacy-Redhat-physical-to-a-virtual-machine/m-p/2946930#M44160</guid>
      <dc:creator>tisuportealba</dc:creator>
      <dc:date>2023-01-05T12:33:24Z</dc:date>
    </item>
  </channel>
</rss>

