/Install vSphere 7 in a non-supported HP DL360-G7

Install vSphere 7 in a non-supported HP DL360-G7

In this Install vSphere 7 in a non-supported HP DL360-G7, I will quickly go through how to install this.

We know that vSphere 7.x is not supported on a G7. If we go for the official support from VMware, it is not even supported on 6.5 and 6.7. But these last two, we can install without any issues and no need for any changes before installation.

In the official VMware HCL, these are the supported ESXi version for an HPE DL360-G7.

For this case, this is the DL360-G7 hardware: Is a Xeon 5630

I had this server for a while in my homelab. The first install on this server was ESXi 6.0, then 6.5, and finally updated for 6.7. But to bypass any issues with old vibs, and since I used HP VMware ISO for the initial install, I will not do any update, but only a fresh install. Since to install vSphere 7.0 on G7, we need to use the official VMware ISO and not the HPE VMware ISO. If not, it will not work, and we have a lot of issues with the installation.

So the best option is always to do a fresh install.

Since vSphere 7.0 does not support this legacy CPU, we need to use a parameter in the boot(before installing) AllowLegacyCPU=True.

The process is the same when using iLO virtual CD-ROM(my case) or a USB key to boot the ISO.

Boot the server with the ISO when the vSphere 7.0 boot starts(yellow screen), press Shift + O to open boot parameters and add the above parameter AllowLegacyCPU=True (is there is any parameter on the line after a blank space insert the new parameter).

You will also see a warning when is to install the vSphere 7.0. This is a warning that we also see in 6.7 when installing in a DL360-G7, just ignored by clicking Enter.

Next, press Enter, and vSphere 7.0 will start to install normally. In the end, we have an HPE DL360-G7 with a vSphere 7.0 fresh install.

Note: There are some blog posts stating that we need to add AllowLegacyCPU=True to boot.cfg after the first boot, if not we will need to add this parameter every time we reboot the ESXi. Never tested with previous versions, but with ESXi-7.0U3c this is not the case.

Update 19/02/2022: So that I make sure that the ESXi doesn’t lose the parameter AllowLegacyCPU=True after a reboot, I also tested with a version vSphere 7.0 U1. So I think is not a matter of version, the parameter will be saved in boot.cfg after you added in your installation boot.

Important note: This is not recommended for critical production environments. I understand that small companies cannot buy new hardware like big companies and may use this solution in production. But for critical systems, you should not implement this non-supported hardware with vSphere 7.0.

Also, beware of any old Network cards that you may have that will not work with vSphere 7.0, even using vSphere 6.5/6.7 drivers.

This solution in my homelab is working without any issues, I also did this with G8 in some “production” systems, and they are working without any problems. But this doesn’t mean you can’t have issues with this Install vSphere 7 in a non-supported HP DL360-G7. So always be careful when using this, and if possible, only use it in test environments.

Share this article if you think it is worth sharing. If you have any questions or comments, comment here, or contact me on Twitter.

©2022 ProVirtualzone. All Rights Reserved
By | 2022-02-19T11:29:45+01:00 February 17th, 2022|VMware Posts, vSphere|0 Comments

About the Author:

I am over 20 years’ experience in the IT industry. Working with Virtualization for more than 10 years (mainly VMware). I am an MCP, VCP6.5-DCV, VMware vSAN Specialist, Veeam Vanguard 2018/2019, vExpert vSAN 2018/2019 and vExpert for the last 4 years. Specialties are Virtualization, Storage, and Virtual Backups. I am working for Elits a Swedish consulting company and allocated to a Swedish multinational networking and telecommunications company as a Teach Lead and acting as a Senior ICT Infrastructure Engineer. I am a blogger and owner of the blog ProVirtualzone.com

Leave A Comment