{"id":6262,"date":"2020-06-28T17:01:35","date_gmt":"2020-06-28T14:01:35","guid":{"rendered":"https:\/\/kifarunix.com\/?p=6262"},"modified":"2024-03-14T21:09:54","modified_gmt":"2024-03-14T18:09:54","slug":"how-to-fix-qemu-kvm-not-connected-error-on-ubuntu-20-04","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/how-to-fix-qemu-kvm-not-connected-error-on-ubuntu-20-04\/","title":{"rendered":"How to fix QEMU\/KVM Not Connected Error on Ubuntu 20.04"},"content":{"rendered":"\n

In this tutorial, you will learn how to fix QEMU\/KVM Not connected error on Ubuntu 20.04. Maybe you have installed KVM hypervisor on Ubuntu 20.04 for you to run virtual machines on it as a regular, non-root, user. However for some reasons, when your try to run virsh<\/code> command to even the virt-manager<\/code>, display the virtual machine desktop management tool, you end up with such errors as Qemu\/KVM no connected. Let us see how to fix such error.<\/p>\n\n\n\n

Disclaimer: The tutorial outlines how i fix the issue myself. This is not an official fix for the issue. Use it ayor.<\/em><\/p>\n\n\n\n

Fixing QEMU\/KVM Not Connected Error<\/h2>\n\n\n\n

A sample of the errors you encounter when running KVM as a non-root user on Ubuntu 20.04 might include the ones sampled below;<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
virsh -c qemu:\/\/\/system<\/code><\/pre>\n\n\n\n
error: failed to connect to the hypervisor\nerror: End of file while reading data: Input\/output error<\/code><\/pre>\n\n\n\n
virsh list --all<\/code><\/pre>\n\n\n\n
error: failed to connect to the hypervisor\nerror: End of file while reading data: Input\/output error<\/code><\/pre>\n\n\n\n
So you have done all that is required to run KVM as a non root user, by adding your standard user name to libvirt<\/code> group, but still you cannot run KVM as a standard user.<\/p>\n\n\n\n
id -nG<\/code><\/pre>\n\n\n\n
koromicha kvm<\/strong> netdev nm-openvpn libvirt<\/strong><\/code><\/pre>\n\n\n\n
All the required modules are loaded;<\/p>\n\n\n\n
lsmod | grep kvm<\/code><\/pre>\n\n\n\n
kvm_intel             282624  0\nkvm                   663552  1 kvm_intel<\/code><\/pre>\n\n\n\n
You have scoured through internet, but no suggested solution has so far fixed the issue with QEMU\/KVM not connected? Perhaps there is something you are not looking for?<\/p>\n\n\n\n
What About AppArmor?<\/h3>\n\n\n\n
According to Ubuntu AppArmor wiki page<\/a>;<\/p>\n\n\n\n
AppArmor is a Mandatory Access Control (MAC) system which is a kernel (LSM) enhancement to confine programs to a limited set of resources. Its security model is to bind access control attributes to programs rather than to users.<\/p>\n\n\n\n
Its confinement is provided via profiles loaded into the kernel, typically on boot. AppArmor profiles can be in one of two modes:<\/p>\n\n\n\n