Open Stack

You could just ask for the value of virt_type parameter from a compute host
(or the output of something like grep 'virt_type' /etc/nova/nova*) if you
are using qemu or kvm.  I believe that's how nova figures out what
parameters to use when launching an instance.

On Wed, May 11, 2016 at 8:39 AM, Kris G. Lindgren <klindgren at godaddy.com>
wrote:

> In the next user survey - could we clarify that qemu == full software cpu
> emulation and kvm (qemu/kvm) = hardware accelerated virtualization or some
> similar phrasing.  It's totally possible that people are like: I run both
> qemu and kvm (thinking that’s qemu/kvm) - when in fact they only run kvm
> (qemu/kvm).
>
> ___________________________________________________________________
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
>
>
>
>
>
>
> On 5/11/16, 11:58 AM, "Tim Bell" <Tim.Bell at cern.ch> wrote:
>
> >Does anyone see a good way to fix this to report KVM or QEMU/KVM ?
> >
> >I guess the worry is whether this would count as a bug fix or an
> incompatible change.
> >
> >Tim
> >
> >On 11/05/16 17:51, "Kashyap Chamarthy" <kchamart at redhat.com> wrote:
> >
> >>On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio Cuellar Valdes wrote:
> >>
> >>[...]
> >>
> >>> I'm confused too about the use of KVM or QEMU In the computes the
> >>> file​/etc/nova/nova-compute.conf has:
> >>>
> >>> virt_type=kvm
> >>>
> >>> The output of:
> >>>
> >>> nova hypervisor-show <id> | grep hypervisor_type
> >>>
> >>> is:
> >>>
> >>> hypervisor_type           | QEMU
> >>
> >>As Dan noted in his response, it's because it is reporting the libvirt
> driver
> >>name (which is reported as QEMU).
> >>
> >>Refer below if you want to double-confirm if your instances are using
> KVM.
> >>
> >>>
> >>> The virsh dumpxml of the instances shows:
> >>>
> >>> <domain type='kvm' id='44'>
> >>
> >>That means, yes, you using KVM.  You can confirm that by checking your
> QEMU
> >>command-line of the Nova instance, you'll see something like "accel=kvm":
> >>
> >>      # This is on Fedora 23 system
> >>      $ ps -ef | grep -i qemu-system-x86_64
> >>      [...] /usr/bin/qemu-system-x86_64 -machine accel=kvm [...]
> >>
> >>> ....
> >>> <emulator>/usr/bin/qemu-system-x86_64</emulator>
> >>>
> >>> ​But according to ​this document [1], it is using QEMU emulator
> instead of
> >>> KVM, because it is not using /usr/bin/qemu-kvm
> >>>
> >>>
> >>> So I really don't know if it's using KVM or QEMU.
> >>
> >>As noted above, a sure-fire way to know is to see if the instance's QEMU
> >>command-line has "accel=kvm".
> >>
> >>A related useful tool is `virt-host-validate` (which is part of
> libvirt-client
> >>package, at least on Fedora-based systems):
> >>
> >>   $ virt-host-validate | egrep -i 'kvm'
> >>    QEMU: Checking if device /dev/kvm exists
>        : PASS
> >>    QEMU: Checking if device /dev/kvm is accessible
>       : PASS
> >>
> >>
> >>> [1] https://libvirt.org/drvqemu.html
> >>>
> >>
> >>
> >>--
> >>/kashyap
> >>
> >>_______________________________________________
> >>OpenStack-operators mailing list
> >>OpenStack-operators at lists.openstack.org
> >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >_______________________________________________
> >OpenStack-operators mailing list
> >OpenStack-operators at lists.openstack.org
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160511/ff3264bf/attachment.html>