Open Stack

I have been curious as to why as mentioned in the thread virt_type=kvm, but
os-hypervisors API call states QEMU.

Interestingly this command mentioned (which works on Ubuntu) gives me a
FAIL and WARN on my home test setup that runs on physical H/W.


$ virt-host-validate
  QEMU: Checking for hardware virtualization
  : PASS
  QEMU: Checking for device /dev/kvm
  : FAIL (Check that the 'kvm-intel' or 'kvm-amd' modules are loaded & the
BIOS has enabled virtualization)
  QEMU: Checking for device /dev/vhost-net
  : WARN (Load the 'vhost_net' module to improve performance of virtio
networking)
  QEMU: Checking for device /dev/net/tun
  : PASS
   LXC: Checking for Linux >= 2.6.26
  : PASS


Ronald Bradford

Web Site: http://ronaldbradford.com
LinkedIn:  http://www.linkedin.com/in/ronaldbradford
Twitter:    @RonaldBradford <http://twitter.com/ronaldbradford>
Skype:     RonaldBradford
GTalk:     Ronald.Bradford
IRC:         rbradfor


On Wed, May 11, 2016 at 12:18 PM, Maish Saidel-Keesing <maishsk at maishsk.com>
wrote:

> Which still brings me back to the original point.
>
> Is this a bug - and should it be reported as such?
>
>
>
> On 11/05/16 18:51, Kashyap Chamarthy 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
>
>
> --
> Best Regards,
> Maish Saidel-Keesing
>
> _______________________________________________
> 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/aea61c34/attachment.html>