Project

General

Profile

Actions

Bug #26010

closed

For the vms built using "Network Based" installation mode on VMWare, unable to change the boot sequence via BIOS

Added by Marek Hulán over 5 years ago. Updated over 4 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1398317

Description of problem:
When we deploy a new vm on VMWare from Satellite v 6 with Network Based installation mode, then the vm always boot from the network. As the boot sequence set is network, disk.

The customer do not have DHCP/PXE in the network so they are using host based iso to install a vm. Once the installation is completed after reboot every time the vm search for DHCP and it fails. This is causing delay in booting vm.

This issue is not seen if we build a vm with "Image Based" provisioning option from satellite v 6.

Version-Release number of selected component (if applicable):
Satellite v 6.2

How reproducible:
Always

Steps to Reproduce:
1. Build a system from satellite v 6 with Network Based installation mode.
2. Go to BIOS for the vm and try to change the boot sequence.
3.

Actual results:
It is not allowed to change the boot sequence.

Expected results:
As the customer is installing ISO to complete the installation there should be an option to change the boot order for the vms.

Additional info:


Related issues 2 (1 open1 closed)

Related to Foreman - Bug #5510: Set network as first boot device for VMs in VMware compute resourcesClosedTimo Goebel04/30/2014Actions
Related to Foreman - Feature #4438: Boot order of libvirt machinesNew02/24/2014Actions
Actions

Also available in: Atom PDF