Lenovo BIOS lock, unable to run Windows OS

[Martin Du Plooy]

Hi

I have a new Lenovo server (ThinkSystem SR630) and installed Proxmox without any issues. Running my first VM (Windows 2016) I get an error "please check with your computer manufacturer to resolve any issues you are having with this computer. These tools are for use only on x86 server hardware manufactured by Lenovo. Since this system is not recognized as a valid system, the installation can not continue. Please click OK to shutdown"
I have been in contact with Lenovo support and they explained I get this error because the OEM OS I am installing is looking for the IBM bios (serial number or something) to validate it's an OEM server and this can validate the OS key and continue installation. Hyper-V and VMware both have patches to access hardware BIOS to do this validate from the VM BIOS.
Example of VMWare fix
Option A:
1. After creating the virtual machine, go to "Edit Settings" --> select the "Options" tab --> select the "General" item and then click the "Configuration Parameters" button.
2. Add a row, paste "SMBIOS.reflectHost" as the name, and "TRUE" as the value.
Please note that the virtual machine must be shut down to let this change take effect.
Option B:
Add "SMBIOS.reflectHost = TRUE" within the .vmx file of the VM.

In Proxmox If you go to the VM --> Options --> BIOS you do get an option on what BIOS to use.

Could anybody help with a solution on this? I do not want to buy my subscription and then findout Proxmox doesn't have a solution for this?

Regards,
Martin

 

[Martin Du Plooy]

I found the solution, it's already in Proxmox and obvious if you know about it.

On your VM goto "Options", Make sure your default bios is "SeaBIOS", then goto "SMBIOS Settings". Here you'll be able to enter all your Manufacture information for the OEM OS to work correctly.

 

[Republicus]

Did you try this with OVMF; UEFI BIOS?
I created a dump of my ACPI table and pass the SLIC table through args passing my OEM SLIC/serial. I haven't tried the PVE option you posted above.

args: -acpitable file=/path/to/slic.bin

This works great for activating my license. I'll have to try a test case with the BIOS options in PVE to see if I can achieve the same results in OVMF because I prefer GPT partitions/UEFI BIOS for passthrough and other reasons.

 

[Martin Du Plooy]

Thanks mate, I'll look into this.

This gives me great confidence in Proxmox.

 

[Veranio79]

I found the solution, it's already in Proxmox and obvious if you know about it.

On your VM goto "Options", Make sure your default bios is "SeaBIOS", then goto "SMBIOS Settings". Here you'll be able to enter all your Manufacture information for the OEM OS to work correctly.

Is this working?
Thank you

 

[german volpi]

[QUOTE = "Veranio79, publicación: 222962, miembro: 61346"]
¿Esto funciona?
Gracias
[/CITAR]

Me Funcionó Perfecto !! gracias



cambiando el bios a SMBIOS y editando poner en fabricante Lenovo, los demas campos dejar todo igual



funciona !!

 

[cosminidis]

Thanks Martin Du Plooy, much appreciated! It works with UEFI BIOS as well.

 

[Claudio.Sachespi]

HI,
i have a Lenovo ST50 v2 SERVER
i hav insert UUID , SERIAL and MANUFACTURED but not resolve ..... help me .... thnaks thanks thanks

this is my server bios information

 

[emunt6]

HI,
i have a Lenovo ST50 v2 SERVER
i hav insert UUID , SERIAL and MANUFACTURED but not resolve ..... help me .... thnaks thanks thanks

this is my server bios information
View attachment 64581View attachment 64580

Edit your VM configuration file ( "/etc/pve/qemu-server/xxx.conf") add the following:

args: -acpitable /sys/firmware/acpi/tables/SLIC

 

[Beaekr]

What I've found is that you can use either SeaBIOS or UEFI (prefered for me). It was tested on a new Lenovo SR250 V3 using Proxmox 8.2.2. I tried to use it with Model and Serial etc in SMBIOS Settings but it will FAIL. ONLY use the UUID (either from BIOS or BMC) and the Manufacturer as Lenovo. Nothing else! BTW Lenovo tech support was a bust on this one. "It's not a supported software on Lenovo Servers." Get with the program Lenovo. Due to the VMWare "issues" this will become more of a common question.

Just for those that are curious. This also works to install a Lenovo branded MS Server OS on a NON Lenovo Server. Any white box will do.

PS. Make sure to put the hyphens (-) in the correct spots. Some Lenovo Servers do not show the UUID with the - in it.

 

[justinclift]

This also works to install a Lenovo branded MS Server OS on a NON Lenovo Server. Any white box will do.

Heh Heh Heh

That sounds like you can pass it pretty much any kind of info you want, and as a long as the info is legit (ie found online from random searching) the installer will believe it outright.

That could be useful for people needing to get creative to make stuff work.