Fix the default for libvirt_cpu_model

Bug #1100366 reported by Flavio Percoco
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Wishlist
Solly Ross

Bug Description

It could be possible to remove the need for manually selecting qemu vs kvm by using some introspection to determine which to use.

It'd be possible to either completely remove this config variable or have a None value for it that tells nova to determine cpu model and features itself.

Revision history for this message
Pádraig Brady (p-draigbrady) wrote :

That's a fair point.
It's already auto detected outside of nova with virt-what in:
  https://github.com/fedora-openstack/openstack-utils/commit/7e4e9d3f
That detection could be pulled inside if needed by looking at /proc etc.

Changed in nova:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Michael Still (mikal) wrote :

This sounds like a nice feature to add to havana when the time comes.

Revision history for this message
Pádraig Brady (p-draigbrady) wrote :
Revision history for this message
Kashyap Chamarthy (kashyapc) wrote :

Tested on Fedora 19:

-> Version
==========
$ rpm -q openstack-utils openstack-nova-compute
openstack-utils-2013.1-5.fc19.1.noarch
openstack-nova-compute-2013.1-0.11.rc1.fc19.noarch
==========

-> Run virt-what which indicates the guest is running on the KVM hypervisor using hardware acceleration
==========
$ virt-what
kvm
$
==========

-> Check the fix is in for openstack-demo-install:
==========
$ grep virt-what /usr/bin/openstack-demo-install -A5
 openstack-utils virt-what \
 -x openstack-swift-plugin-swift3

if [ "$os_dist" != 'essex' ] && [ "$os_dist" != 'folsom' ]; then
  conductor='conductor'
fi
--
if virt-what | grep -q .; then
  # We're running in a VM so set nova-compute up appropriately
  echo '======= Configuring VM. Please wait =======' >&2
  fedora_ver="0$(sed -n 's/Fedora release \([0-9]*\).*/\1/p' /etc/issue)"
  openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_type qemu
  # Workaround (https://bugzilla.redhat.com/show_bug.cgi?id=858216)
$
==========

-> grep for libvirt_type in nova.conf
==========
[root@localhost ~]# grep -i libvirt_type /etc/nova/nova.conf
libvirt_type = qemu
[root@localhost ~]#
==========

-> Search for the SELinux boolean set:
=========
$ getsebool -a | grep virt_use_execmem
virt_use_execmem --> on
$
==========

-> Running nova services:
==========
$ systemctl | grep -i nova | grep -i running
openstack-nova-api.service loaded active running OpenStack Nova API Server
openstack-nova-cert.service loaded active running OpenStack Nova Cert Server
openstac...onductor.service loaded active running OpenStack Nova Conductor Server
openstac...soleauth.service loaded active running OpenStack Nova VNC console auth Server
openstac...-network.service loaded active running OpenStack Nova Network Server
openstac...ectstore.service loaded active running OpenStack Nova Objectstore Server
openstac...cheduler.service loaded active running OpenStack Nova Scheduler Server
==========

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/31133

Changed in nova:
assignee: nobody → Solly Ross (sross-7)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/34444

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/34445

Revision history for this message
Joe Gordon (jogo) wrote :

marked invalid per discussions in the linked reviews above.

Changed in nova:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.