Changing boot order of VMware compute resource during provisioning locks out BIOS

Solution In Progress - 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.x configured with VMWare virtual compute resource

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.