<?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 Problem running V2V in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965951#M47117</link>
    <description>We trying to run an V2V migration and follow the manual (HP PL Essentials VMM Software User Guide) very carefully, in spite of that fact we get the following message direct after selecting Deploy-Virtual Machine-V2V: "No, Only one Virtualization Layer detected. V2V migration cannot be performed." Anyone any ideas.&lt;BR /&gt;&lt;BR /&gt;Jorgen Stenberg</description>
    <pubDate>Thu, 09 Mar 2006 11:15:44 GMT</pubDate>
    <dc:creator>Jorgen Stenberg</dc:creator>
    <dc:date>2006-03-09T11:15:44Z</dc:date>
    <item>
      <title>Problem running V2V</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965951#M47117</link>
      <description>We trying to run an V2V migration and follow the manual (HP PL Essentials VMM Software User Guide) very carefully, in spite of that fact we get the following message direct after selecting Deploy-Virtual Machine-V2V: "No, Only one Virtualization Layer detected. V2V migration cannot be performed." Anyone any ideas.&lt;BR /&gt;&lt;BR /&gt;Jorgen Stenberg</description>
      <pubDate>Thu, 09 Mar 2006 11:15:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965951#M47117</guid>
      <dc:creator>Jorgen Stenberg</dc:creator>
      <dc:date>2006-03-09T11:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running V2V</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965952#M47118</link>
      <description>Think of a V2V migration as a 'conversion' from one virtualization technology to another.  If you need to move or copy a VM from one VMware ESX host to another, you don't need to use V2V.&lt;BR /&gt;&lt;BR /&gt;This message means that HP SIM has only identified one type of virtualization technology.</description>
      <pubDate>Thu, 09 Mar 2006 12:53:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965952#M47118</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2006-03-09T12:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running V2V</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965953#M47119</link>
      <description>David is right.  If you have only one type of Virtualization layer ie either GSX, MSVS or ESX what you need to use is Copy or move feature of VMM.  Migrations are only between unlike Virtualization layer and would cost you one licese per migration.</description>
      <pubDate>Mon, 13 Mar 2006 04:41:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965953#M47119</guid>
      <dc:creator>NEETI TOLIA</dc:creator>
      <dc:date>2006-03-13T04:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running V2V</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965954#M47120</link>
      <description>I have just realized that I haven´t read the manual so carefully as I said. Thanks for your answers!</description>
      <pubDate>Mon, 13 Mar 2006 04:57:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-v2v/m-p/4965954#M47120</guid>
      <dc:creator>Jorgen Stenberg</dc:creator>
      <dc:date>2006-03-13T04:57:59Z</dc:date>
    </item>
  </channel>
</rss>

