Reviewed: https://review.openstack.org/122218 Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=59a201bdf276d751f41066373db125bd46f3c400 Submitter: Jenkins Branch: master
commit 59a201bdf276d751f41066373db125bd46f3c400 Author: Robb Romans <[email protected]> Date: Wed Sep 17 13:31:07 2014 -0500 Remove kvm as a hypervisor_type argument QEMU is used whether specifying either qemu or kvm as an argument to hypervisor_type. Therefore, remove kvm as a supported argument. Change-Id: I89f2b907fa868e50c2b65c2bf4a8e414242dd9fc Closes-bug: #1195361 ** Changed in: openstack-manuals Status: In Progress => Fix Released -- 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: Fix Released 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
