Bug ID 542664: No default boot volume is set when installing a vCMP guest from a hotfix iso.

Last Modified: Oct 16, 2023

Affected Product(s):
BIG-IP vCMP(all modules)

Known Affected Versions:
11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6

Opened: Aug 31, 2015

Severity: 3-Major

Related Article: K39334424


When creating a vCMP guest using both an initial-image and initial-hotfix, the default boot volume is not set. This causes any future software installation performed inside that guest to automatically become the default boot volume.


The default boot location is not set, which causes subsequent software installations inside the guest to be automatically marked default. Upon a reboot of an affected guest, the system boots into a newly installed volume, which might not be the desired behavior.


This issue occurs when a vCMP guest is created from a hotfix build of BIG-IP.


Once the vCMP guest is running perform the following steps: 1. Login to the guest via ssh or the vconsole utility. 2. Run the switchboot utility. 3. Select the appropriate volume to be the default boot location (there might be only one option in this list). 4. Press enter. If the selected boot location is the current or only volume, it is marked as the default boot volume and the guest does not reboot. If the selected boot location is not the currently booted volume, the guest immediately reboots into the selected volume. Verify the operation was successful by issuing the command: grub_default -l. The output of the command should resemble this: -- config # grub_default -l HD1.1 active yes default yes title BIG-IP 11.6.0 Build 5.0.429 As long as the appropriate volume is marked 'default yes', the operation is complete.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips