Project

General

Profile

Actions

Bug #5510

closed

Set network as first boot device for VMs in VMware compute resources

Added by Marco De Vitis about 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When creating a virtual machine via Foreman on a VMware compute resource (ESX), the boot order of the VM has the hard disk as first boot device and network as last boot device.
This works for the first VM build because there's nothing on the VM HDD, but when you try to rebuild the VM the PXE image is never loaded from the network because the installed OS is booted first from HDD.
Somehow the default boot order should have network set as the first boot device, just like it happens for other compute resource types, e.g. libvirt/KVM.

This would also partly satisfy this feature request: http://projects.theforeman.org/issues/4317


Related issues 4 (0 open4 closed)

Related to Foreman - Feature #4317: Build button - Vmware provisioning - single click rebuildResolved02/11/2014Actions
Related to Foreman - Bug #14160: VMware image-based provisioning: 'configSpec.bootOptions.bootOrder' parameter incorrectClosedChris Roberts03/11/2016Actions
Related to Foreman - Bug #26010: For the vms built using "Network Based" installation mode on VMWare, unable to change the boot sequence via BIOSClosedOndřej EzrActions
Blocked by Foreman - Refactor #12612: Update fog to 1.37.0ClosedTimo Goebel11/26/2015Actions
Actions

Also available in: Atom PDF