Differences

This shows you the differences between two versions of the page.

--- virtualization:vmware:7:old_hardware [2023/10/02 07:35] – rplecko
+++ virtualization:vmware:7:old_hardware [2023/10/02 08:09] (current) – rplecko
@@ Line 6: / Line 6: @@
 If you try to install ESXi 7 on an hardware with older CPU(s) that is no longer officially supported by VMware, you will get a error message similar to this when booting the installation medium:
+<code>
 VMB: 611:
 Unsupported CPU: Intel family 0x06, model 0x1a, stepping 0x5
 Intel(R) Xeon(R) CPU		E5520  @ 2.27GHz
 See http://www.vmware.com/resources/compatibility
+</code>
 Even if it is unsupported it might work in practice.
 To bypass this error in the boot, do as follows:
-    Reboot into boot media again
+  * Reboot into boot media again
-    After the ESXi boot menu when the “Loading ESXi Installer” is starting click SHIFT+O within 5 seconds to add boot options.
+  * After the ESXi boot menu when the “Loading ESXi Installer” is starting click SHIFT+O within 5 seconds to add boot options.
-    Type “ allowLegacyCPU=true” behind the line. Like this:
+  *     Type “ allowLegacyCPU=true” behind the line. Like this:
+<code>
 <ENTER: Apply options and boot>
 > cdromBoot runweasel allowLegacyCPU=true
+</code>
-    Click ENTER and continue installation as normal.
+  * Click ENTER and continue installation as normal.
-    Eventually you will come across error messages like this:
+  * Eventually you will come across error messages like this:
+<code>
 Error(s)/Warning(s) Found During System Scan
@@ Line 31: / Line 36: @@
 ESXi 7.0.0. Please refer to the VMware Compatibility Guide (VCG)
 for the list of supported CPUs.>
+</code>
-    Click ENTER to continue, and finnish the installation.
+  * Unordered List ItemClick ENTER to continue, and finnish the installation.
-    After the installation medium is removed and the server is restarted the boot options have to be set every time you restart the server.
+  * After the installation medium is removed and the server is restarted the boot options have to be set every time you restart the server.
-    This can be avoided, read on.
+This can be avoided, read on.
+=== Permanently allow boot from Legacy CPU ===
-Permanently allow boot from Legacy CPU
 The easiest way to accomplish automatic boot with a legacy CPU is to do as follows:
-    Shut down the ESXi Server and remove the boot-USB-drive.
+  * Shut down the ESXi Server and remove the boot-USB-drive.
-    Insert the drive in another computer. It will contain two FAT-partitions.
+  * Insert the drive in another computer. It will contain two FAT-partitions.
-    Open the the drive with multiple files including BOOT.CFG, and open it in a text-editor.
+  * Open the the drive with multiple files including BOOT.CFG, and open it in a text-editor.
-    One of the partitions is just containing a BOOT.CFG file and nothing else. this is NOT the one you should edit.
+  * One of the partitions is just containing a BOOT.CFG file and nothing else. this is NOT the one you should edit.
+{{ :virtualization:vmware:7:vm7_unsupported_hw_01.png?700 }}
 The bottom drive in this picture is the correct one to edit BOOT.CFG on
-    Add “ allowLegacyCPU=true” to the end of the line starting with “kernelopt=“
+Add “ allowLegacyCPU=true” to the end of the line starting with “kernelopt=“
+<code>
 bootstate=0
 title=Loading VMware ESXi
@@ Line 58: / Line 70: @@
 build=7.0.0-1.25.16324942
 updated=1
+</code>
-    Save the file and move the drive back to the server
+  * Save the file and move the drive back to the server
-    Start the server, ESXi should now boot up without the need of any manual boot option input.
+  * Start the server, ESXi should now boot up without the need of any manual boot option input.
+=== Fixing “This host does not support virtualizing real mode” error ===
-Fixing “This host does not support virtualizing real mode” error
 Now when VMware ESXi 7.0 is up and running and all looks good you still might run into problems, not unlikely this one (when trying to start a VM):
-Failed to power on virtual machine Home-Assistant. This host does not support virtualizing real mode. The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor. Click here for more details.
+<code>
+Failed to power on virtual machine Home-Assistant.
+This host does not support virtualizing real mode.
+The Intel "VMX Unrestricted Guest" feature is necessary to run this virtual machine on an Intel processor.
+Click here for more details.
+</code>
-Power On VM
+{{ :virtualization:vmware:7:vm7_unsupported_hw_02.png?700 }}
+  * Power On VM
 Key
 haTask-2-vim.VirtualMachine.powerOn-3629474806
@@ Line 86: / Line 107: @@
 This issue has to be solved for every current and future VM, but the process is easy and fast when you know how.
-    Click “Edit” on the VM
+  * Click “Edit” on the VM
-    Select “VM Options”
+  * Select “VM Options”
-    Open “Advanced” and select “Edit Configuration…”
+  * Open “Advanced” and select “Edit Configuration…”
-    Click “Add parameter” and fill as follows:
+  * Click “Add parameter” and fill as follows:
+<code>
     Key: monitor.allowLegacyCPU
     Value: true
+</code>
+{{ :virtualization:vmware:7:vm7_unsupported_hw_03.png?700 }}
+  * Click “OK” and “Save”
+  * The VM should now work, but be patient. It can take a very long time to boot.
+{{ :virtualization:vmware:7:vm7_unsupported_hw_04.png?700 }}
-    Click “OK” and “Save”
-    The VM should now work, but be patient. It can take a very long time to boot.
-I hope this is to good use. Running unsupported is however not recommended, but for uncritical servers why not.