Ask Your Question
0

Openstack on Proxmox

asked 2014-12-21 00:30:32 -0500

Fishbone gravatar image

updated 2014-12-22 16:08:26 -0500

Hello I am running openstack in a development environment on my PC. My PC hardware is very capable of supporting openstack; however I have run into a bit of a dilemma.

I have the Proxmox hypervisor running on my host machine and I have installed openstack icehouse under the 3-node architecture with the neutron networking feature under guest kvms. All components of my setup work 100% except one simple flaw. I cannot get the compute node working for various reasons and I have tried the following:

Originally I setup the compute node as a guest kvm as I did with the other nodes. This setup produced the error: libvirtError: internal error: no supported architecture for os type 'hvm' even after adjusting the nova.conf file with the libvirt kvm directive as instructed by the documentation. I also receive an error: An error occurred while trying to define a domain with xml: <domain type="kvm">

I soon attempted to force hardware virtualization on the kvm by disabling it in the hypervisor web GUI as instructed by the proxmox wiki to enable hardware virtualization from within a guest kvm. This produced an unreliable guest OS in regards to interface, as expected, but did allow hardware accelleration within the guest, however; then the nova-compute service would not be able to start properly. Any time I attempted to restart the service it would claim it refers to an unknown instance and echo that it started but the results wouldn't change.

I abolished the idea of using a kvm and attempted to modify an openvz container. The container would never be able to install the nova-compute package, echoing invoke-rc.d: initscript nova-compute, action "start" failed. All other features work properly, when the libvirtError: internal error: no supported architecture for os type 'hvm' message is the issue, the compute node is detected by the controller and able to communicate with the neutron server. I am running the icehouse deployment on 3 ubuntu 14.04 nodes as kvms and are provisioned as follows:

Controller = 1 core, 3GB RAM, 25GB HDD Neutron = 1 core, 2 GB RAM, 20 GB HDD KVM/Openvz - Nova = 6 core, 6 GB RAM, 750 GB HDD

All of these errors lead me to believe that a true nova compute node may be unable to run under a proxmox hypervisor host. Which leads to my question, is it possible to run a compute node under proxmox and if so, what would be the best approach.

Thank you for your time.

edit retag flag offensive close merge delete
add a comment

3 answers

Sort by ยป oldest newest most voted
1

answered 2014-12-23 10:00:12 -0500

Fishbone gravatar image

updated 2015-05-28 16:05:14 -0500

Thanks, I have found a resolution when researching the second error: An error occurred while trying to define a domain with xml: on page https://bugs.launchpad.net/ubuntu/+so...

In order for the domain to be recognized as qemu the settings: 

compute_driver = libvirt.LibvirtDriver
[libvirt]
virt_type = qemu

must be in the nova-compute.conf file. I modified that file and restart the service and now it works.

Hello all, turns out running openstack inside proxmox kvm is possible, following the steps articulated in this forum. http://forum.proxmox.com/threads/18093-Nested-KVM I have purchased a new server and enabled nested kvm and I can run vm instances inside a proxmox vm without the need to change the virt_type to qemu. Please be aware that a modern intel or standard amd processor is required for this, I recommend near TOL and be sure to have extra resources available.

edit flag offensive delete link more

Comments

How far you got with openstack on proxmox for production purposes

UHL-Services gravatar imageUHL-Services ( 2019-12-29 10:17:43 -0500 )edit
add a comment
1

answered 2014-12-22 01:20:44 -0500

dbaxps gravatar image

Per http://docs.openstack.org/juno/config...
To enable QEMU on Compute node, add these settings to nova.conf:

compute_driver = libvirt.LibvirtDriver
[libvirt]
virt_type = qemu

You don't have nested KVM on Virtual machine.

edit flag offensive delete link more

Comments

Thank you so much for the response, I did not have that top line inserted in my nova.conf. However; i get the same error when inputting that line. I modified the question also.

Fishbone gravatar imageFishbone ( 2014-12-22 16:07:00 -0500 )edit

The new error is: An error occurred while trying to define a domain with xml: <domain type="kvm"> I'm sure there is something I've been doing wrong, I just can't seem to find a solution.

Fishbone gravatar imageFishbone ( 2014-12-22 16:09:43 -0500 )edit

Should be <domain type="qemu">. Who creates this entry ? Does it do "nova boot ...." command ?

dbaxps gravatar imagedbaxps ( 2014-12-22 22:49:39 -0500 )edit

Yes, thank you, I never noticed that error until now. The entry was created when running the nova boot command, correct. Thank you very much for your guidance and assistance, I have found a solution and will post as the answer.

Fishbone gravatar imageFishbone ( 2014-12-23 09:54:52 -0500 )edit

When you mentioned that I don't have nested KVM on virtual machine, are you saying that it isn't possible to run kvm inside a vm?

Fishbone gravatar imageFishbone ( 2014-12-31 08:53:47 -0500 )edit
see more comments
0

answered 2014-12-31 08:46:38 -0500

Fishbone gravatar image

The issue with setting the environment to qemu is working now. Would it be possible to run the nova-compute node in the kvm environment as a vm in proxmox. I am testing specifically to utilize openstack in a future proxmox production environment.

edit flag offensive delete link more
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

subscribe to rss feed

Stats

Asked: 2014-12-21 00:30:32 -0500

Seen: 8,462 times

Last updated: May 28 '15

Related questions

Openstack and KVM integration

libvirtError: invalid argument: could not find capabilities for domaintype=kvm??

XenServer on OpenStack/KVM

how to connect to a container

swift Error: Unable to create container.

kvm instance launch error [closed]

single swift container limitations

container based open stack environment security risks

PciPassthrough and NumaTopollogy filters returns 0 hosts in Liberty

cannot create container