This should not be original. Both methods can be found online. I just explained it and it is not reprinted...
In fact, the OEM system mentioned here refers to windows, and I have never tested any other systems...
Method 1:
Directly edit the vmx configuration file of the VM, and modify or add the following content:
SMBIOS.reflectHost = "true"
Alternatively, on the VM Panel of the vclient, select option-advanced: general-configuration parameters.
Find smbios. reflecthost and enter "true". If not, click "add" to add it.
This method enables the VM to use the BIOS information of the physical machine to verify and activate the guest OS.
This function is supported from ESX 3.0.1. For more information, see http://kb.vmware.com/kb/1002095. In addition, ESX 2 supports this parameter. this parameter is no longer important and is now in the 5 era.
After applying this parameter from ESX 3.0.2, the system displays the manufacturer information of the physical machine.
The negotiation between VMware and Microsoft is beyond our consideration.
Method 2:
Enables virtual loading of modified VMware BIOS files so that the VM can read the required SLIC information.
Directly edit the vmx configuration file of the VM, and modify or add the following content:
bios440.filename = /path/to/biosfile
This parameter cannot be found within the KB of VMware. This modification method is definitely not a normal way...
In addition, the specified BIOS file will not be moved with the migration of the VM. Therefore, you need to place the modified BIOS file in a location accessible to all hosts, or save one copy on each esxi host. Otherwise, the HA will become invalid.
This article is from the foolishfish blog, please be sure to keep this source http://foolishfish.blog.51cto.com/3822001/1538372