<?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: Integrity VM: san storage virtualization in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289098#M526280</link>
    <description>... or some such.</description>
    <pubDate>Fri, 24 Oct 2008 08:27:39 GMT</pubDate>
    <dc:creator>Russell.Wood</dc:creator>
    <dc:date>2008-10-24T08:27:39Z</dc:date>
    <item>
      <title>Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289090#M526272</link>
      <description>we are going to install VM on hpu11iv2 an create 3 VM.&lt;BR /&gt;&lt;BR /&gt;the server is connected to the san (an EVA) with one HBA&lt;BR /&gt;we have different LUN's on the EVA and we would like to allocate LUN's to each VM.&lt;BR /&gt;&lt;BR /&gt;i saw in the quicspec of VM that FC HBAs and storage array controllers are not virtualized by Integrity VM&lt;BR /&gt;does that mean that we can't allocate LUN's to each VM? &lt;BR /&gt;could someone help me to understand that&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Oct 2008 12:43:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289090#M526272</guid>
      <dc:creator>Nappy_1</dc:creator>
      <dc:date>2008-10-17T12:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289091#M526273</link>
      <description>No it means you can't allocate whole HBAs or array controllers to a VM. You *can* allocate individual LUNs to a VM with no problem at all, so your config sounds fine.&lt;BR /&gt;&lt;BR /&gt;If possible I would go with a 11iv3 VM Host if you can though, as that will allow you to use HPVM v4.0. You can still have 11iv2 VM guests if you wish.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Duncan</description>
      <pubDate>Fri, 17 Oct 2008 12:50:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289091#M526273</guid>
      <dc:creator>Duncan Edmonstone</dc:creator>
      <dc:date>2008-10-17T12:50:15Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289092#M526274</link>
      <description>Present the LUN to the Host and then add the character DSF as a device to the Guest:&lt;BR /&gt;&lt;BR /&gt;hpvmmodify -p &lt;VMID&gt; -a disk:scsi::/dev/rdsk/c-t-d-&lt;BR /&gt;&lt;BR /&gt;In the Guest, run `ioscan -fn &amp;amp;&amp;amp; insf -ev'. You have raw access to the LUN.&lt;/VMID&gt;</description>
      <pubDate>Wed, 22 Oct 2008 11:48:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289092#M526274</guid>
      <dc:creator>Russell.Wood</dc:creator>
      <dc:date>2008-10-22T11:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289093#M526275</link>
      <description>If you have multiple pathes to the LUN, you should not use the raw disk without any multipathing software. If your path fails, you have no longer access to the LUN. Consider to use LVM or upgrade to HPVM v4.0 (11.31 for the host).</description>
      <pubDate>Wed, 22 Oct 2008 12:00:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289093#M526275</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-10-22T12:00:30Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289094#M526276</link>
      <description>The host handles the multipathing so it's not an issue.</description>
      <pubDate>Thu, 23 Oct 2008 04:04:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289094#M526276</guid>
      <dc:creator>Russell.Wood</dc:creator>
      <dc:date>2008-10-23T04:04:26Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289095#M526277</link>
      <description>"The host handles the multipathing so it's not an issue."&lt;BR /&gt;&lt;BR /&gt;Why you are so sure? It's 11.23 with "raw" disks as backing storage. In this case you need additional software ...</description>
      <pubDate>Thu, 23 Oct 2008 04:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289095#M526277</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-10-23T04:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289096#M526278</link>
      <description>Well, if the system has SAN storage with Multiple paths then one can safely assume they'd use SecurePath (or some such) on the Host.</description>
      <pubDate>Fri, 24 Oct 2008 00:46:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289096#M526278</guid>
      <dc:creator>Russell.Wood</dc:creator>
      <dc:date>2008-10-24T00:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289097#M526279</link>
      <description>How about PVLINKS, Russell?</description>
      <pubDate>Fri, 24 Oct 2008 04:24:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289097#M526279</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-10-24T04:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289098#M526280</link>
      <description>... or some such.</description>
      <pubDate>Fri, 24 Oct 2008 08:27:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289098#M526280</guid>
      <dc:creator>Russell.Wood</dc:creator>
      <dc:date>2008-10-24T08:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: Integrity VM: san storage virtualization</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289099#M526281</link>
      <description>What I want to say is that you cannot assume there is any multipathing software in use, because PVLINKS is the way how (legacy) LVM is handling multiple pathes.&lt;BR /&gt;&lt;BR /&gt;If you assign a raw disk to a VM without add software and this path fails - you and your VMs are lost ...</description>
      <pubDate>Fri, 24 Oct 2008 08:44:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/integrity-vm-san-storage-virtualization/m-p/4289099#M526281</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-10-24T08:44:02Z</dc:date>
    </item>
  </channel>
</rss>

