Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP MA-VE
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
Fixed In:
12.0.0, 11.6.1, 11.6.0 HF6
Opened: Jan 14, 2014
Severity: 3-Major
Related Article:
K17185
BIG-IP Virtual Edition (VE) instances created using OpenStack interfaces may fail to detect the Kernel-based Virtual Machine (KVM) hypervisor.
As a result of this issue, you may encounter one or more of the following symptoms: -- The BIG-IP VE instance fails to start. -- When starting the BIG-IP VE instance, diagnostic messages may indicate that the hypervisor is not recognized.
This issue occurs when all of the following conditions are met: -- You are deploying a BIG-IP VE instance on a KVM hypervisor. -- You are using the OpenStack interface tool set to perform the deployment.
To work around this issue, you can modify your OpenStack compute nodes to run all instances as KVM. To do so, perform the following procedure: Note: The workaround assumes that your compute nodes use KVM as the default hypervisor. Impact of workaround: Performing the following procedure should not have a negative impact on your system. 1. Log in to the OpenStack compute node as the root user. 2. Using an editor, create a file in the /etc/nova directory named release. 3. Add the following content to the new file: [Nova] vendor = Red Hat product = Bochs package = RHEL 6.3.0 PC 4. Restart all services or reboot the compute note. 5. Redeploy a new BIG-IP VE instance using the OpenStack interface tool set.
BIG-IP VE instances created using OpenStack interfaces now detect the KVM hypervisor. Important: If you performed the steps to work around this issue (as described in the known issue for this bug), removing the workaround might require a license change.
