<?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: SGLX in VMware in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299972#M58008</link>
    <description>SGLX can run in VMware server under certain conditions, but is NOT SUPPORTED.  There are a number of reasons it is not supported.  Specifically, Lock LUN cannot be supported because of how shared storage is supported in VMware server (not very well).  Also, for similar reasons, there is a possibility of data corruption in VMware server.&lt;BR /&gt;&lt;BR /&gt;For practical reasons, HP cannot support our products in a platform that is not offically supported by a vendor.  Since VMware server is free, it is not officially supported by VMware.  Therefore, if we had issues, we could not support our customers.&lt;BR /&gt;&lt;BR /&gt;That said, I have used VMware server as a training vehicle.  The "trick" is setting up additional LUNs as shared storage. The only process I have generated is one that has all virtual machines that are part of the cluster on the same servers and using files that represent shared storage.  You can see why this is only for training (or some development). &lt;BR /&gt;&lt;BR /&gt;Given this STRONG statement of non-support, and given the following is on the web (although difficult to find) here is the process.  Read this 3 times before trying this.&lt;BR /&gt;&lt;BR /&gt;First, make sure the virtual servers are powered off.  Before adding any extra disks add the following lines to the servers â  .vmxâ   files.  Watch for typos, especially on the last line since it is slightly different.&lt;BR /&gt;&lt;BR /&gt;scsi1.present = "TRUE"&lt;BR /&gt; scsi1.virtualDev = "lsilogic"&lt;BR /&gt; scsi1.sharedBus = "virtualâ   &lt;BR /&gt;disk.locking = "FALSE"&lt;BR /&gt;&lt;BR /&gt;Note the â  lsilogicâ   assumes that scsi0 is also â  lsilogicâ  &lt;BR /&gt;&lt;BR /&gt;Edit virtual machine Node1 (using the VMware GUI, not an editor)&lt;BR /&gt;Add&lt;BR /&gt;Hard disk&lt;BR /&gt;Create new virtual disk&lt;BR /&gt;SCSI&lt;BR /&gt;Size&lt;BR /&gt;When it asked for disk file I suggest the following:&lt;BR /&gt; Use a different directory than the servers.  For instance, use the â  .vmdkâ   extension.  For example: shares/share1.vmdk&lt;BR /&gt;Before selecting Finished â   select Advanced (this is important)&lt;BR /&gt;Select a SCSI address with scsi1:x (recommend 1 for first package (LUN), etc).&lt;BR /&gt;Select â  independentâ   (persistent will be selected by default)&lt;BR /&gt;Select â  Finishedâ   - A disk will now be created&lt;BR /&gt;&lt;BR /&gt;Edit the â  .vmxâ   file for the first server and you will find â  independent-persistentâ   listed for the new disk.  Make this be â  persistentâ  .&lt;BR /&gt;&lt;BR /&gt;Each disk should have the following entries: scsi1:x.present = â  trueâ  &lt;BR /&gt; scsi1:x.filename = â  this will be the pathâ   &lt;BR /&gt;scsi1:x.mode = â  persistentâ  &lt;BR /&gt; scsi1:x.deviceType = â  plainDiskâ  &lt;BR /&gt;&lt;BR /&gt;For the second machine do the same except select the â  use an existing diskâ  .  Everything else is the same.  Make sure you select the same SCSI identifier for the disk, e.g. 1:1&lt;BR /&gt;&lt;BR /&gt;Some of this info is on the web.  You now had a lot of keywords to google if you need.&lt;BR /&gt;&lt;BR /&gt;Expect that you may have to reboot servers an extra couple of times if you have ANY problems related to disk access.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Nov 2008 17:12:08 GMT</pubDate>
    <dc:creator>Serviceguard for Linux</dc:creator>
    <dc:date>2008-11-05T17:12:08Z</dc:date>
    <item>
      <title>SGLX in VMware</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299969#M58005</link>
      <description>According to the link below SGLX in VMWARE is possible using VMWARE server (as well as esx), does anyone have an instructions on doing this in VMWARE Server? In the link below Erick describes his setup, but no instructions on setting it up.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1221017" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1221017&lt;/A&gt;</description>
      <pubDate>Tue, 04 Nov 2008 11:09:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299969#M58005</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2008-11-04T11:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: SGLX in VMware</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299970#M58006</link>
      <description>See "Using Serviceguard for Linux with VMware Virtual Machines, October 2007"&lt;BR /&gt;( Red Hat Linux, SUSE Linux )&lt;BR /&gt;PDF @ &lt;A href="http://docs.hp.com/en/12122/SGLX-VMware.pdf" target="_blank"&gt;http://docs.hp.com/en/12122/SGLX-VMware.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Nov 2008 14:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299970#M58006</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2008-11-04T14:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: SGLX in VMware</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299971#M58007</link>
      <description>Stephen thanks for the reply. i've actually seen that document already however it seems more closely related to VMware ESX rather than VMware Server. As an example it talks about raw device mappings for your disk type which you don't get in vmware server version (unless my verision is out of date). &lt;BR /&gt;&lt;BR /&gt;In the link i mentioned Erick said he had done this in VMware Server, so rather than reinvent the wheel i'd hoped that he (or someone else) had documented what they'd done.</description>
      <pubDate>Tue, 04 Nov 2008 15:00:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299971#M58007</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2008-11-04T15:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: SGLX in VMware</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299972#M58008</link>
      <description>SGLX can run in VMware server under certain conditions, but is NOT SUPPORTED.  There are a number of reasons it is not supported.  Specifically, Lock LUN cannot be supported because of how shared storage is supported in VMware server (not very well).  Also, for similar reasons, there is a possibility of data corruption in VMware server.&lt;BR /&gt;&lt;BR /&gt;For practical reasons, HP cannot support our products in a platform that is not offically supported by a vendor.  Since VMware server is free, it is not officially supported by VMware.  Therefore, if we had issues, we could not support our customers.&lt;BR /&gt;&lt;BR /&gt;That said, I have used VMware server as a training vehicle.  The "trick" is setting up additional LUNs as shared storage. The only process I have generated is one that has all virtual machines that are part of the cluster on the same servers and using files that represent shared storage.  You can see why this is only for training (or some development). &lt;BR /&gt;&lt;BR /&gt;Given this STRONG statement of non-support, and given the following is on the web (although difficult to find) here is the process.  Read this 3 times before trying this.&lt;BR /&gt;&lt;BR /&gt;First, make sure the virtual servers are powered off.  Before adding any extra disks add the following lines to the servers â  .vmxâ   files.  Watch for typos, especially on the last line since it is slightly different.&lt;BR /&gt;&lt;BR /&gt;scsi1.present = "TRUE"&lt;BR /&gt; scsi1.virtualDev = "lsilogic"&lt;BR /&gt; scsi1.sharedBus = "virtualâ   &lt;BR /&gt;disk.locking = "FALSE"&lt;BR /&gt;&lt;BR /&gt;Note the â  lsilogicâ   assumes that scsi0 is also â  lsilogicâ  &lt;BR /&gt;&lt;BR /&gt;Edit virtual machine Node1 (using the VMware GUI, not an editor)&lt;BR /&gt;Add&lt;BR /&gt;Hard disk&lt;BR /&gt;Create new virtual disk&lt;BR /&gt;SCSI&lt;BR /&gt;Size&lt;BR /&gt;When it asked for disk file I suggest the following:&lt;BR /&gt; Use a different directory than the servers.  For instance, use the â  .vmdkâ   extension.  For example: shares/share1.vmdk&lt;BR /&gt;Before selecting Finished â   select Advanced (this is important)&lt;BR /&gt;Select a SCSI address with scsi1:x (recommend 1 for first package (LUN), etc).&lt;BR /&gt;Select â  independentâ   (persistent will be selected by default)&lt;BR /&gt;Select â  Finishedâ   - A disk will now be created&lt;BR /&gt;&lt;BR /&gt;Edit the â  .vmxâ   file for the first server and you will find â  independent-persistentâ   listed for the new disk.  Make this be â  persistentâ  .&lt;BR /&gt;&lt;BR /&gt;Each disk should have the following entries: scsi1:x.present = â  trueâ  &lt;BR /&gt; scsi1:x.filename = â  this will be the pathâ   &lt;BR /&gt;scsi1:x.mode = â  persistentâ  &lt;BR /&gt; scsi1:x.deviceType = â  plainDiskâ  &lt;BR /&gt;&lt;BR /&gt;For the second machine do the same except select the â  use an existing diskâ  .  Everything else is the same.  Make sure you select the same SCSI identifier for the disk, e.g. 1:1&lt;BR /&gt;&lt;BR /&gt;Some of this info is on the web.  You now had a lot of keywords to google if you need.&lt;BR /&gt;&lt;BR /&gt;Expect that you may have to reboot servers an extra couple of times if you have ANY problems related to disk access.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Nov 2008 17:12:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299972#M58008</guid>
      <dc:creator>Serviceguard for Linux</dc:creator>
      <dc:date>2008-11-05T17:12:08Z</dc:date>
    </item>
    <item>
      <title>Re: SGLX in VMware</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299973#M58009</link>
      <description>Thanks. i had seen some of these references on the web but was unsure as to whether it would work for serviceguard for Linux. &lt;BR /&gt;&lt;BR /&gt;As for your non-support statement i understand. This is not for production or development purposes. i have been working on HPUX for over 10 years and until recently had a test (play) lab made up of a couple of D-Class servers (Cannibalised) using serviceguard 11.15.&lt;BR /&gt;&lt;BR /&gt;However as all things come to an end one of my nodes died recently and i had to lay it to rest. so i'm looking for another play area and servicguard in linux via vmware server looked to be a reasonable lower cost approach.</description>
      <pubDate>Wed, 05 Nov 2008 17:37:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299973#M58009</guid>
      <dc:creator>unixdaddy</dc:creator>
      <dc:date>2008-11-05T17:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: SGLX in VMware</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299974#M58010</link>
      <description>OK.  And it should be clear but the funny characters are standard double quotes&lt;BR /&gt;&lt;BR /&gt;"&lt;BR /&gt;&lt;BR /&gt;I think the copy and paste had some side effects.</description>
      <pubDate>Wed, 05 Nov 2008 17:43:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sglx-in-vmware/m-p/4299974#M58010</guid>
      <dc:creator>Serviceguard for Linux</dc:creator>
      <dc:date>2008-11-05T17:43:23Z</dc:date>
    </item>
  </channel>
</rss>

