Honestly, it's really a docs bug.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Changed in: nova
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1195361
Title:
QEMU hypervisor type returned when libvirt_type = kvm
Status in OpenStack Compute (Nova):
Won't Fix
Status in OpenStack Manuals:
New
Bug description:
As the following output indicates, the QEMU hypervisor type is used
even when libvirt_type = kvm in nova.conf.
# grep libvirt_type /etc/nova/nova.conf
libvirt_type = kvm
# nova hypervisor-show 1 | grep hypervisor_type
| hypervisor_type | QEMU
It appears that the OpenStack libvirt driver uses the libvirt
connection type to determine the hypervisor type instead of the
libvirt_type configuration option. Should libvirt_type be used to
determine KVM vs QEMU hypervisor type or is there another
configuration for this? From a user perspective, getting the QEMU
versus KVM hypervisor type correct is important when setting the
hypervisor_type property on an image.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1195361/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
