I just started an install of KVM to support minikube on Ubuntu 18.04.3.
I can second the behavior noted here in this bug report. And as of today
it is still an issue.
Here is console log of the issue as I am seeing it:
ken@docker:~$ grep -E --color 'vmx|svm' /proc/cpuinfo
flags : fpu v
Here is a bit more background as there may be some confusion for me
based on the documentation I'm following:
https://help.ubuntu.com/community/KVM/Installation
I'm running 18.04.3 as I said. And it appears that there is some
differences based on 18.10 and 9.10
I;m proceeding forward with libvir
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/176925
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
Hi Nur,
that is odd the handling is as following.
In the past there was a group libvirtd - new packaging in Debian and
Ubuntu renamed that to libvirt but the install handles that.
In case of a new install you would have those groups for libvirt:
libvirt:x:132:paelzer
