Why boot sequence in BIOS is locked for vms provisioned on VMware compute resource from Red Hat Satellite 6?

Solution Verified - Updated -

Issue

  • When deploying a new VM on VMware from Satellite v 6 with Network Based installation mode, the VM always boots from the network. This is because the boot sequence is set network, disk.

  • Once the installation is completed after reboot every time the VM will search for DHCP and/or a PXE server. This can cause unintended consequences

  • The BIOS cannot be changed to boot from the hard disk first.

Environment

  • Red Hat Satellite 6.2. and above configured with VMWare as a compute resource

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content