libvirt 2.5 without kvm requires cpu_mode="none"

[lzamel]

- [x] This is a doc addition request.
In Finalize installation please add a second note:

When running qemu without no support for HW virtualization setting cpu_mode="none" along side virt_type=qemu in /etc/nova/nova-compute.conf solves 'libvirtError: unsupported configuration: CPU mode 'host-model' for x86_64 qemu domain on x86_64 host is not supported by hypervisor" error.

-----------------------------------
Release: 15.0.0 on 2017-03-27 13:54
SHA: 4fd887114cb355b3972851b2d13c7cf5a366d646
Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/nova-compute-install.rst
URL: https://docs.openstack.org/ocata/install-guide-ubuntu/nova-compute-install.html

[Lana (loquacity)]

I think the Install Guide doesn't need to mention this, it's an opinionated install. This is troubleshooting info, and more rightly belongs somewhere in the User Guides. Happy to discuss.

[lzamel (lukasz-zamel)]

Perfectly happy to get this note added to user guides. Is at the end of 'Launch an instance' section in 'Launch and manage instances' better?

[Joseph Robinson (joseph-r-email)]

In the User Guide, it does look like a good place for this information is a subsection of the dashboard-launch-instances file. Please stat in the note content this is a troubleshooting for KVM images point.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/465957
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=c5d4645ab7ea255124571e07235820b9369fa197
Submitter: Jenkins
Branch: master

commit c5d4645ab7ea255124571e07235820b9369fa197
Author: Alexandra Settle <email address hidden>
Date: Thu May 18 14:07:21 2017 +0100

    [user-guide] Add note for troubleshooting error

    libvirt 2.5 without kvm requires cpu_mode="none"

    Change-Id: I0efdc219de3501d00c53e0f6ecd6c448c721a250
    Closes-bug: 1678636