Forum Discussion
BIG-IP LTM VE on KVM?
F5 now posts
BIGIP-11.3.0.2806.0.qcow2.zip
I followed the instructions on this document
http://support.f5.com/content/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-kvm-setup-11-3-0/_jcr_content/pdfAttach/download/file.res/BIG-IP%C2%AE_Virtual_Edition_Setup_Guide_for_Linux_KVM.pdf
the VM starts up and everything but some processes do not seem to run correctly.
here is the output of "tmsh show sys version"
[root@localhost:NO LICENSE:] config tmsh show sys version
Cannot connect to mcpd
Cannot connect to mcpd. Your preferences and aliases will not be available until it comes back up.
The connection to mcpd has been lost, try again.
I also get these messages every 10 seconds
[root@localhost:NO LICENSE:] config Jul 8 16:37:18 localhost emerg logger: Re-starting chmand
Jul 8 16:37:28 localhost emerg logger: Re-starting chmand
Jul 8 16:37:38 localhost emerg logger: Re-starting chmand
Jul 8 16:37:48 localhost emerg logger: Re-starting chmand
I tried to post the domain xml file I'm using here on devcentral but no success. so here's the pastebin link.
any suggestions to change this XML file would be GREATLY APPRECAITED.
regards
- symtex_22198NimbostratusI finally got it to work but only on RHEL
- Tom_04_144543NimbostratusI also hit this issue. It seems it's more related to the way the image runs under OpenStack running on Ubuntu with KVM. Under KVM on a standard Ubuntu system, I do not see the issue, it's only when I upload to my OpenStack setup w/OpenVSwitch that I notice the issue. It looks like F5 haven't tested this combination yet and I also note that only CentOS6/RHEL6 is listed for KVM support under their F5 BIGIP VE hypervisor matrix document.
- b_136889Nimbostratusany luck with this running on ubuntu ?
- Gonzalo_A__AranNimbostratus
I managed to get it up and running. I run:
virsh edit the-domainname
Where "the-domainname" is the name of the virtual machine as seen by "Virtual Machine Manager".
Then, I edited this part:
hvm
to
hvm
This was the change that got this working. Prior to this I also changed the virtual processor in "View" > "Details" >"Processor" > "Configuration" by clicking on "Copy host CPU configuration".
So, the relevant part of the XML look like this now:
hvm SandyBridge Intel destroy restart restart
Hope this helps.
- yaxzone_100047NimbostratusGonzalo A. Arana, your suggestion worked. I went ahead and remove the content of /PLATFORM and just added the one line you suggested: "platform=Z100 family=0xC0000000 host=Z100 systype=0x71" Right after I saved, it stopped the the emerg logger error: "May 6 13:09:04 localhost emerg logger: Re-starting chmand" I'm running VE LTM BigIP-11.3.0.39.0, this is on VirtualBox 5.0.16 r105871 on the Mac with El Capitan v10.11.3. Thanks for the suggestion.
- Gonzalo_A__AranNimbostratus
Here's the relevant part: http://pastebin.com/bvCM9cFd
- b_136889Nimbostratus
This is what I have done to make it work in openstack. BIGIP ltm ve versions tried are 11.4.1 and 11.5.1 edit the /PLATFORM file to add
platform=Z100 family=0xC0000000 host=Z100 systype=0x71
and delete the /temp/platform_info file and restart the vm.
I am not sure what will be the adverse effect of these changes so please do it on your own risk. Do let me know if it works.
- F_Barth_183102NimbostratusThanks a lot! Has worked here (KVM, BigIP 11.5.1)...
- bzubair_204319NimbostratusHi All, It didnt work for me. I tested with "BIGIP 11.3.0 on Ubuntu 12.04.5 LTS KVM" AND "BIGIP 11.3.0 on Openstack CentOs7" any other solution? Thanks
- fmarignier_2154NimbostratusHi All, The tricks works for me on my openstack plateforme but I have now a nex problem due to the licence. The F5 licence server return : F5 registration key is not compatible with the detected platform - This platform, "Z100", cannot be activated with this registration key.. ggrrr!! Do you have further informations about parameters we can put in /PLATFORM file ? or another idea ? Thanks in advance.
- What_Lies_Bene1Cirrostratus
Just FYI, I had the same issues with BIG-IQ v4.4 on OpenStack (running on RHEL) and modifying the /PLATFORM file as above did the trick.
Haven't had this issue with BIG-IP v11.4.1 on OpenStack at all.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com