Differences

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

--- virtualization:vmware:7:old_hardware [2023/10/02 07:42] – rplecko
+++ virtualization:vmware:7:old_hardware [2023/10/02 08:09] (current) – rplecko
@@ Line 52: / Line 52: @@
   * 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.
+{{ :virtualization:vmware:7:vm7_unsupported_hw_01.png?700 }}
 The bottom drive in this picture is the correct one to edit BOOT.CFG on
@@ Line 72: / Line 75: @@
   * 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>
+{{ :virtualization:vmware:7:vm7_unsupported_hw_02.png?700 }}
-Power On VM
+  * Power On VM
 Key
 haTask-2-vim.VirtualMachine.powerOn-3629474806
@@ Line 96: / 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.