4/30/2023 0 Comments Vmware workstation 14![]() This will be confirmation that we did configure the VMDK hard drive image to load correctly and will have no unexpected issues. Observe the screen for “boot-loader” information related to EFI. Select our new Virtual Machine & click “Play virtual machine”. We are now ready to start our image and begin to use the Home Assistance application. ![]() (If this happens, please restart the lab from Step 4a.)Īppend the following string to the bottom of the file & save the file.įirmware = “efi“ Start the new Virtual Machine ![]() Note: If the VM image was started before we add in our entry, then startup issues will occur. If the VM image was not started, we will NOT find a key:value pair with the string “firmware”. Use either MS Windows notepad.exe or Notepad++ or similar tool to edit the configuration file. Edit configuration file for new Virtual Machine The “*.vmx” filename extension/suffix will contain hardware configuration for booting the VWmare VM server image. ![]() You will now see several other files, include the primary configuration file for our new Virtual Machine. Navigate to the folder where the VMDK was extracted. To address this challenge, we will use VMware documented method to directly update the configuration file for our new Virtual machine for one (1) setting. However, VMware Player does not expose this setting in the GUI. If you have VMware workstation/ ESXi server, you may have access to a GUI entry to adjust this virtual firmware bootloader configuration. The Home Assistant bootable VMDK disk was designed and configured for the boot-loader of EFI, instead of the older legacy “BIOS” boot-loader. Convert “BIOS” (default) to “EFI” type for new Virtual Machine Required the following step to adjust VMware Player to boot correctly. Used information from your example to adjust VMware Player deployment to use the VMDK.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |