<?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 &amp;quot;host: can't find smbios entry point&amp;quot; in VMware Workstation Pro Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/quot-host-can-t-find-smbios-entry-point-quot/m-p/2949213#M179620</link>
    <description>&lt;P&gt;I just resized my disk using the expand and then use gpartd to repair the gpt in the Linux guest.&amp;nbsp; Upon existing gpartd, it recommended rebooting so the kernel would reload the partition.&amp;nbsp; Now when I restart the guest, the screen spins for a while with "Waiting for connection." and then the screen goes blank.&amp;nbsp; Near the end of vmware.log is the host error "host: can't find smbios entry point". From the behavior of the system, this error must mean it is unable to load the bios.&amp;nbsp; Attempting to force bios setup upon restart results in the same failure, thus it doesn't appear to be related to the expanding of the disk.&lt;/P&gt;&lt;P&gt;The disk went from 300GB to 400GB in size.&lt;/P&gt;&lt;P&gt;With respect to the vmware.log file, the only issue possibly related is "AHCI: Tried to enable/disable IO space." shows up a couple times.&lt;/P&gt;&lt;P&gt;Any ideas on how to resolve this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit:&amp;nbsp; I did find this to be interesting.&amp;nbsp; In an older log (likely post disk expansion but pre-gdisk fix of gpt), I got the following differences in a couple places:&amp;nbsp;&lt;/P&gt;&lt;P&gt;newest vmware.log: &amp;lt;, older vmware.log &amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt; In(05) vmx DISK: Opening disks took 37 ms.&lt;BR /&gt;---&lt;BR /&gt;&amp;gt; In(05) vmx DISK: Opening disks took 43 ms.&lt;/P&gt;&lt;P&gt;&amp;lt; In(05) vmx DISKUTIL: (null) : max toolsVersion = 0, type = 0&lt;BR /&gt;&amp;lt; In(05) vmx DISKUTIL: Offline toolsVersion = 0, type = 0&lt;BR /&gt;...&lt;BR /&gt;---&lt;BR /&gt;&amp;gt; In(05) vmx DISKUTIL: scsi0:0 : max toolsVersion = 11269, type = 4&lt;BR /&gt;&amp;gt; In(05) vmx TOOLS setting legacy tools version to '11269' type 4, manifest status is 9&lt;/P&gt;&lt;P&gt;Both logs have the "vcpu-0 Host: can't find host SMBIOS entry point" entry, so this error could be a red herring.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Jan 2023 20:59:08 GMT</pubDate>
    <dc:creator>mailmichael</dc:creator>
    <dc:date>2023-01-17T20:59:08Z</dc:date>
    <item>
      <title>"host: can't find smbios entry point"</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/quot-host-can-t-find-smbios-entry-point-quot/m-p/2949213#M179620</link>
      <description>&lt;P&gt;I just resized my disk using the expand and then use gpartd to repair the gpt in the Linux guest.&amp;nbsp; Upon existing gpartd, it recommended rebooting so the kernel would reload the partition.&amp;nbsp; Now when I restart the guest, the screen spins for a while with "Waiting for connection." and then the screen goes blank.&amp;nbsp; Near the end of vmware.log is the host error "host: can't find smbios entry point". From the behavior of the system, this error must mean it is unable to load the bios.&amp;nbsp; Attempting to force bios setup upon restart results in the same failure, thus it doesn't appear to be related to the expanding of the disk.&lt;/P&gt;&lt;P&gt;The disk went from 300GB to 400GB in size.&lt;/P&gt;&lt;P&gt;With respect to the vmware.log file, the only issue possibly related is "AHCI: Tried to enable/disable IO space." shows up a couple times.&lt;/P&gt;&lt;P&gt;Any ideas on how to resolve this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit:&amp;nbsp; I did find this to be interesting.&amp;nbsp; In an older log (likely post disk expansion but pre-gdisk fix of gpt), I got the following differences in a couple places:&amp;nbsp;&lt;/P&gt;&lt;P&gt;newest vmware.log: &amp;lt;, older vmware.log &amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt; In(05) vmx DISK: Opening disks took 37 ms.&lt;BR /&gt;---&lt;BR /&gt;&amp;gt; In(05) vmx DISK: Opening disks took 43 ms.&lt;/P&gt;&lt;P&gt;&amp;lt; In(05) vmx DISKUTIL: (null) : max toolsVersion = 0, type = 0&lt;BR /&gt;&amp;lt; In(05) vmx DISKUTIL: Offline toolsVersion = 0, type = 0&lt;BR /&gt;...&lt;BR /&gt;---&lt;BR /&gt;&amp;gt; In(05) vmx DISKUTIL: scsi0:0 : max toolsVersion = 11269, type = 4&lt;BR /&gt;&amp;gt; In(05) vmx TOOLS setting legacy tools version to '11269' type 4, manifest status is 9&lt;/P&gt;&lt;P&gt;Both logs have the "vcpu-0 Host: can't find host SMBIOS entry point" entry, so this error could be a red herring.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 20:59:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/quot-host-can-t-find-smbios-entry-point-quot/m-p/2949213#M179620</guid>
      <dc:creator>mailmichael</dc:creator>
      <dc:date>2023-01-17T20:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: "host: can't find smbios entry point"</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/quot-host-can-t-find-smbios-entry-point-quot/m-p/2949224#M179623</link>
      <description>&lt;P&gt;I figured this out on my own.&lt;/P&gt;&lt;P&gt;The reason the screen is blank could be due to Display settings unsupported by the BIOS or grub.&amp;nbsp; I dumb downed my display settings, and now I can see the bios and grub boot.&amp;nbsp; Grub is failing to read the (hd0) partition table.&amp;nbsp; I'll be digging into this next, though not a vmware issue at this point.&amp;nbsp; At least I can now boot off a CDROM and use gparted to see the partition table is recoverable. &lt;img class="lia-deferred-image lia-image-emoji" src="https://communities.vmware.com/html/@DCF4E2F7991292CEECF250394DB2C2BC/emoticons/1f642.png" alt=":slightly_smiling_face:" title=":slightly_smiling_face:" /&gt;&amp;nbsp; I just need to figure out how to get grub to see it.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jan 2023 21:32:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/quot-host-can-t-find-smbios-entry-point-quot/m-p/2949224#M179623</guid>
      <dc:creator>mailmichael</dc:creator>
      <dc:date>2023-01-17T21:32:50Z</dc:date>
    </item>
  </channel>
</rss>

