<?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 crash on HP ESxi in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/vmware-crash-on/m-p/7058903#M2562</link>
    <description>&lt;P&gt;Actually these are the specs of our software.&lt;/P&gt;&lt;P&gt;Client version:&amp;nbsp; 1.23.0&lt;/P&gt;&lt;P&gt;Client build number:&amp;nbsp; 6506686&lt;/P&gt;&lt;P&gt;ESXi version:&amp;nbsp; 6.5.0&lt;/P&gt;&lt;P&gt;ESXi build number:&amp;nbsp; 7388607&lt;/P&gt;</description>
    <pubDate>Fri, 16 Aug 2019 15:40:37 GMT</pubDate>
    <dc:creator>jdatwood</dc:creator>
    <dc:date>2019-08-16T15:40:37Z</dc:date>
    <item>
      <title>VMWARE crash on</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-crash-on/m-p/7058902#M2561</link>
      <description>&lt;DIV&gt;HP Proliant DL380 Gen 9&lt;/DIV&gt;&lt;DIV&gt;ESXi VMWARE 6.0&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Hello,&amp;nbsp; I can't attach an image on the forums here but perhaps someone will understand what I am talking about.&amp;nbsp; With our VMWARE setup, you'll notice I have opened up DATASTORE1.&amp;nbsp; Inside the SQL VM you will see the following files.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;SQL_1.vmdk is 500GB.&amp;nbsp; This is where our SQLVM DB is located.&amp;nbsp; The missing file is SQL_0.vmdk which was about 3.48 GB and that contains our Boot disk.&amp;nbsp; Without the boot disk we cannot boot into the VM and extract anything from SQL_1.vmdk.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;So the question is whether we can actually access that SQL_1.vmdk file by creating a new VM and moving it over? ( Thus we need the new SSD in there ).&amp;nbsp; OR, we are out of luck.&amp;nbsp;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thank you!&lt;/DIV&gt;&lt;DIV&gt;Jim&lt;/DIV&gt;</description>
      <pubDate>Fri, 16 Aug 2019 15:38:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-crash-on/m-p/7058902#M2561</guid>
      <dc:creator>jdatwood</dc:creator>
      <dc:date>2019-08-16T15:38:57Z</dc:date>
    </item>
    <item>
      <title>Re: VMWARE crash on HP ESxi</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/vmware-crash-on/m-p/7058903#M2562</link>
      <description>&lt;P&gt;Actually these are the specs of our software.&lt;/P&gt;&lt;P&gt;Client version:&amp;nbsp; 1.23.0&lt;/P&gt;&lt;P&gt;Client build number:&amp;nbsp; 6506686&lt;/P&gt;&lt;P&gt;ESXi version:&amp;nbsp; 6.5.0&lt;/P&gt;&lt;P&gt;ESXi build number:&amp;nbsp; 7388607&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 15:40:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/vmware-crash-on/m-p/7058903#M2562</guid>
      <dc:creator>jdatwood</dc:creator>
      <dc:date>2019-08-16T15:40:37Z</dc:date>
    </item>
  </channel>
</rss>

