[library] qemu-kvm shouldn't be on controller nodes

Bug #1334834 reported by Aleksandr Shaposhnikov
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Fuel Library (Deprecated)

Bug Description

MOS trying to install qemu-kvm/qemu-system with kvm on controller nodes. Since controller nodes are not allowed to be compute nodes it's not required to be there. Moreover it will and it actually would be a problem if controllers didn't supports HW accelerated virtualization(simple controller server or virtualized controllers).

Changed in fuel:
importance: Undecided → Low
assignee: nobody → Fuel Library Team (fuel-library)
Changed in fuel:
milestone: none → 5.1
Revision history for this message
Andrew Woodward (xarses) wrote :

the qemu-kvm package is supposed to silently ignore if kvm acceleration can not be loaded, so the latter statement is not supposed to be an issue. There was a case of this in the Ubuntu packages and it was already resolved.

If you have any cases of this then we need to raise it as packaging errors.

Dmitry Ilyin (idv1985)
summary: - qemu-kvm shouldn't be on controller nodes
+ [library] qemu-kvm shouldn't be on controller nodes
Changed in fuel:
status: New → Invalid
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Raising to high since this bug renders KVM accelerated compute impossible to deploy on environments with controllers that don't support hardware accelerated virtualization.

Changed in fuel:
status: Invalid → Confirmed
importance: Low → High
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Please elaborate the status, shouldn't qemu-qvm being installed at controller nodes? That is relation for computes ones?

Revision history for this message
Dmitry Ilyin (idv1985) wrote :

I don't see qemu installed on controllers both CentOS and Ubuntu. There is only qemu-img apperently needed by Glance.

Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

The only thing we need on controller is qemu-utils for tools like qemu-img. Installing qemu-kvm package on Ubuntu without kvm support in CPU fails, because the qemu service tries to start and fails. This breaks deployment.

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Looks like this was fixed in 5.1 by merging upstream Puppet manifests for nova: qemu-kvm used to be pulled in as a dependency of guestmount, new manifests only install guestmount on the compute nodes.

Changed in fuel:
status: Invalid → Fix Committed
Revision history for this message
Andrey Danin (gcon-monolake) wrote :

Seems that bug #1338913 is related to this one.
The problem was reproduced with Public ISO #44 Jul 27, 2014
https://fuel-jenkins.mirantis.com/view/ISO/job/publish_fuel_community_iso/17/
After the deployment of Compute nodes finished, a user have to manually run 'modprobe -a kvm; modprobe -a kvm-intel; service libvirtd restart;' on each Compute node.

Changed in fuel:
status: Fix Committed → Triaged
Revision history for this message
Andrey Danin (gcon-monolake) wrote :

The bug #1338913 is a separate bug.

Changed in fuel:
status: Triaged → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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