<?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: vmware issue in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639042#M707</link>
    <description>yep..this is what I am asking for.but I dont know how to do that.pls give me the steps...&lt;BR /&gt;</description>
    <pubDate>Sat, 29 May 2010 08:47:15 GMT</pubDate>
    <dc:creator>kunjuttan</dc:creator>
    <dc:date>2010-05-29T08:47:15Z</dc:date>
    <item>
      <title>vmware issue</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639040#M705</link>
      <description>hi gurus,&lt;BR /&gt;i am facing a problem in my HP-EVA8400 storage.I am having a server running windows 2003 server os.And around 700GB space is mapped to my storage.now we have to move this server to a vmware.Now my question is how to map this 700GB space in vmware.&lt;BR /&gt;&lt;BR /&gt;thx &lt;BR /&gt;rgds&lt;BR /&gt;kunju</description>
      <pubDate>Fri, 28 May 2010 05:28:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639040#M705</guid>
      <dc:creator>kunjuttan</dc:creator>
      <dc:date>2010-05-28T05:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: vmware issue</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639041#M706</link>
      <description>If you don't want to move the data into a VMDK on a VMFS, why not map the virtual disk to the ESX server and set up a Raw Device Mapping (RDM)?&lt;BR /&gt;&lt;BR /&gt;That way you can even 'flip back' to the physical server. Make sure only one of them has access to the disk at a time, though!</description>
      <pubDate>Fri, 28 May 2010 13:22:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639041#M706</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-05-28T13:22:23Z</dc:date>
    </item>
    <item>
      <title>Re: vmware issue</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639042#M707</link>
      <description>yep..this is what I am asking for.but I dont know how to do that.pls give me the steps...&lt;BR /&gt;</description>
      <pubDate>Sat, 29 May 2010 08:47:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639042#M707</guid>
      <dc:creator>kunjuttan</dc:creator>
      <dc:date>2010-05-29T08:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: vmware issue</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639043#M708</link>
      <description>Hello,&lt;BR /&gt;here are steps:&lt;BR /&gt;1. install server in Vmware&lt;BR /&gt;2. present Eva storage to ESX server/servers&lt;BR /&gt;3. rescan FC HBA's on you ESX/ESX's&lt;BR /&gt;4. DO NOT create vmfs storage on newly detected volume!&lt;BR /&gt;5. POWER OFF your virtual server&lt;BR /&gt;6. go to Edit setting in your VM, clik Add disk, click Raw device mapping disk, select it from the list, confirm setting.&lt;BR /&gt;7. Power on you VM.&lt;BR /&gt;8. Enjoy your old disk in new virtual enviroment. :)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Sun, 30 May 2010 18:03:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639043#M708</guid>
      <dc:creator>Jan Soska</dc:creator>
      <dc:date>2010-05-30T18:03:42Z</dc:date>
    </item>
    <item>
      <title>Re: vmware issue</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639044#M709</link>
      <description>thanx..&lt;BR /&gt;  i have 2 more doubts,&lt;BR /&gt;1)Is anything is to be done from the storage size apart from presenting the LUN to the ESX host?&lt;BR /&gt;2)My data will be intact.r8???</description>
      <pubDate>Mon, 31 May 2010 04:20:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639044#M709</guid>
      <dc:creator>kunjuttan</dc:creator>
      <dc:date>2010-05-31T04:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: vmware issue</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639045#M710</link>
      <description>1. No, that's it. What I do is, I use different 'ranges' of LUN addresses to have it easier to tell a virtual disk that is used for a VMFS data store from an RDM.&lt;BR /&gt;&lt;BR /&gt;E.g. addresses 1..19 are used for VMFS.&lt;BR /&gt;Addresses 20..39 are used for RDMs.&lt;BR /&gt;&lt;BR /&gt;2. The data is not touched, but be careful with tools like FDISK, DD, ... and never use the "Add Storage" on an RDM disk - many people are confused by this, but it is only used to create a new VMFS datastore.&lt;BR /&gt;&lt;BR /&gt;That's why I recommend using different address ranges for LUN addresses.</description>
      <pubDate>Mon, 31 May 2010 04:27:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-issue/m-p/4639045#M710</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-05-31T04:27:20Z</dc:date>
    </item>
  </channel>
</rss>

