Project

General

Profile

Bug #33749

ESXi 7.0 U2 and later (VM version 19) EFI Boot Failure

Added by Doug Forster 10 months ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

When the VM vmx-19 is set to network boot automatically it fails.
When the VM vmx-19 is set to prompt and Normal/network boot is chosen it is successful.

Default PXE scripts are in use. Grub fails on the chainload option only when automatically booting. When the Setup menu is forced it tries again to boot and succeeds.

Screen Shot 2021-10-20 at 9.12.38 AM.png View Screen Shot 2021-10-20 at 9.12.38 AM.png 396 KB Screenshot of grub debug=all with failed and successful runs. Doug Forster, 10/20/2021 05:14 PM
Screen%20shot%202021 10 20%20at%209.12.38%20am

History

#1 Updated by Doug Forster 10 months ago

How do I remove the fixed in release option as this hasn't been fixed.

#2 Updated by Doug Forster 10 months ago

If I change vmx-19 to vmx-15 the server boots and works without interaction.

The hammer command used to create said VM is:
hammer -v \
host create \
--architecture x86_64 \
--compute-attributes cpus=4,memory_mb=8192,cluster='VM Cluster',path=/Datacenters/VM/vm,start=1,firmware=efi,guest_id=otherGuest64,hardware_version=vmx-19,guest_id=rhel8_64Guest,scsi_controller_type=ParaVirtualSCSIController \
--compute-resource "vCenter" \
--domain example.net \
--puppet-environment production \
--hostgroup-title linux \
--name server.example.net \
--interface ip=10.0.0.20,subnet_id=106,compute_network=NET_10.0.0.0,compute_type=VirtualVmxnet3 \
--location "Default" \
--medium "RHEL 8.4 Install Media" \
--operatingsystem "RHEL Server 8.4" \
--organization Example \
--puppet-ca-proxy puppet.example.net \
--puppet-proxy puppet.example.net \
--volume "size_gb=200,datastore=PROD,thin=true,eager_zero=false" \
--partition-table="Kickstart default" \
--pxe-loader "Grub2 UEFI"

#3 Updated by Doug Forster 8 months ago

I have confirmed with RedHat that there is a bug effecting network efi booting on 7.0 versions of the VM/vmx-19. Perhaps the best option at this point is to block someone from using it for network based provisioning until it has been fixed.

#4 Updated by Doug Forster 8 months ago

I have found a workaround from VMware Support.
Set "efi.quickBoot.enabled = FALSE" as an advanced property on the VM allows the vm to boot normally.

Also available in: Atom PDF