<div dir="ltr">I don't disagree, what we're really getting at is that any lookup (ask the system what it's using on a particular instance, look at the config, look at the output of a nova CLI request, querry via Horizon), should all return the same answer. So one is a bug (Horizon), the other requires looking up information in the system itself. As I suggested, the config is one path, and I still believe will provide the current correct answer for the hypervisor node (Linux QEMU/KVM or QEMU/QEMU) regardless of other issues, and the Horizon path is a bug that should be fixed.<div><br></div><div>R</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 11, 2016 at 9:20 AM, Maish Saidel-Keesing <span dir="ltr"><<a href="mailto:maishsk@maishsk.com" target="_blank">maishsk@maishsk.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Or we could just fix the problem within OpenStack to report the
correct Hypervisor in the first place. <br>
</p>
<p>This kind of reminds me of a story. <br>
</p>
<p>Someone was trying to drive down a path on his bicycle, but there
were some tacks on the path.<br>
So his wheel kept on getting full of holes. So they thought and
thought of how to overcome the problem.</p>
<p>They built small jet engines into the bike so that they could
hover over the ground, instead of riding over<br>
the tacks.</p>
<p>They were happy because they could now go down the path. <br>
</p>
<p>The simple answer should have been - get off the bike and pick up
the tacks - instead of finding ways to <br>
over-engineer the problem</p>
<p>Either show the right thing - or don't show it at all.</p>
<p>My 0.02 Shekels. <br>
</p><div><div class="h5">
<div>On 11/05/16 22:06, Robert Starmer
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">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.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, May 11, 2016 at 8:39 AM, Kris
G. Lindgren <span dir="ltr"><<a href="mailto:klindgren@godaddy.com" target="_blank">klindgren@godaddy.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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).<br>
<br>
___________________________________________________________________<br>
Kris Lindgren<br>
Senior Linux Systems Engineer<br>
GoDaddy<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 5/11/16, 11:58 AM, "Tim Bell" <<a href="mailto:Tim.Bell@cern.ch" target="_blank"></a><a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>>
wrote:<br>
<br>
>Does anyone see a good way to fix this to report KVM or
QEMU/KVM ?<br>
><br>
>I guess the worry is whether this would count as a bug
fix or an incompatible change.<br>
><br>
>Tim<br>
><br>
>On 11/05/16 17:51, "Kashyap Chamarthy" <<a href="mailto:kchamart@redhat.com" target="_blank"></a><a href="mailto:kchamart@redhat.com" target="_blank">kchamart@redhat.com</a>>
wrote:<br>
><br>
>>On Tue, May 03, 2016 at 02:27:00PM -0500, Sergio
Cuellar Valdes wrote:<br>
>><br>
>>[...]<br>
>><br>
>>> I'm confused too about the use of KVM or QEMU
In the computes the<br>
>>> file/etc/nova/nova-compute.conf has:<br>
>>><br>
>>> virt_type=kvm<br>
>>><br>
>>> The output of:<br>
>>><br>
>>> nova hypervisor-show <id> | grep
hypervisor_type<br>
>>><br>
>>> is:<br>
>>><br>
>>> hypervisor_type | QEMU<br>
>><br>
>>As Dan noted in his response, it's because it is
reporting the libvirt driver<br>
>>name (which is reported as QEMU).<br>
>><br>
>>Refer below if you want to double-confirm if your
instances are using KVM.<br>
>><br>
>>><br>
>>> The virsh dumpxml of the instances shows:<br>
>>><br>
>>> <domain type='kvm' id='44'><br>
>><br>
>>That means, yes, you using KVM. You can confirm
that by checking your QEMU<br>
>>command-line of the Nova instance, you'll see
something like "accel=kvm":<br>
>><br>
>> # This is on Fedora 23 system<br>
>> $ ps -ef | grep -i qemu-system-x86_64<br>
>> [...] /usr/bin/qemu-system-x86_64 -machine
accel=kvm [...]<br>
>><br>
>>> ....<br>
>>>
<emulator>/usr/bin/qemu-system-x86_64</emulator><br>
>>><br>
>>> But according to this document [1], it is
using QEMU emulator instead of<br>
>>> KVM, because it is not using /usr/bin/qemu-kvm<br>
>>><br>
>>><br>
>>> So I really don't know if it's using KVM or
QEMU.<br>
>><br>
>>As noted above, a sure-fire way to know is to see if
the instance's QEMU<br>
>>command-line has "accel=kvm".<br>
>><br>
>>A related useful tool is `virt-host-validate` (which
is part of libvirt-client<br>
>>package, at least on Fedora-based systems):<br>
>><br>
>> $ virt-host-validate | egrep -i 'kvm'<br>
>> QEMU: Checking if device /dev/kvm exists
: PASS<br>
>> QEMU: Checking if device /dev/kvm is accessible
: PASS<br>
>><br>
>><br>
>>> [1] <a href="https://libvirt.org/drvqemu.html" rel="noreferrer" target="_blank">https://libvirt.org/drvqemu.html</a><br>
>>><br>
>><br>
>><br>
>>--<br>
>>/kashyap<br>
>><br>
>>_______________________________________________<br>
>>OpenStack-operators mailing list<br>
>><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
>_______________________________________________<br>
>OpenStack-operators mailing list<br>
><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
OpenStack-operators mailing list
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</blockquote>
<br>
</div></div><span class="HOEnZb"><font color="#888888"><div>-- <br>
Best Regards,<br>
Maish Saidel-Keesing</div>
</font></span></div>
</blockquote></div><br></div>