开发者

virt-install error [closed]

开发者 https://www.devze.com 2023-03-12 05:21 出处:网络
Closed. This qu开发者_运维知识库estion does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed. This qu开发者_运维知识库estion does not meet Stack Overflow guidelines. It is not currently accepting answers.

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

Closed 6 years ago.

Improve this question

I have setup kvm, libvirt on one of Dell poweredge1000m blades. I am using the following syntax for installing a virtual machine from an existing image (executing as root).

virt-install --name=vm_test --ram=1024 --arch=i686 --vcpus=1 --os-type=linux --import --disk path=/root/shared.qcow2,bus=virtio,format=qcow2 --graphics vnc,port=5901,listen=0.0.0.0,password=newone --noautoconsole --description --autostart

I am getting the following error.

Starting install...
ERROR    internal error process exited while connecting to monitor: char device redirected to /dev/pts/1
open /dev/kvm: Permission denied
failed to initialize KVM: Operation not permitted

Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
  virsh --connect qemu:///system start vm_test
otherwise, please restart your installation.

I have used exactly the same command with one of other desktop hosts and it works there. I can install a VM from virt-manager using an ISO image with virt-manager storing the disk image at default location.

It seems like a file permissions error to me as it is not working with /vms directory but is working with some other /home/vm directory.

Thanks for help in advance


I got the same error message on a server, which has libvirt up for weeks. Setting libvirt to run as root (as mentioned in the link) didn't work for me. However, granting read & execute access to /var/lib/libvirt/images solved my problem.

chmod go+rx /var/lib/libvirt/images
chmod o-rwx /var/lib/libvirt/images/*


If you follow all the instructions on creating vm using libvirt, you may still meet the error message above. The root cause is AppArmor which can be found on recent Ubuntu distributions. The easiest way is to remove AppArmor if security is not a concern.

The official documentation of Ubuntu gives many advice on disable AppArmor:

Disable AppArmor


I had found the solution to my problem, here it is.

The real reason was that /vms was an NFS mount and its configuration(no_root_squash + rw) was such that it was required to be accessed over root.

By default libvirt runs a virtual machine with the user and group permissions of libvirt-qemu:kvm which would create trouble even if you run it with sudo privileges. So we need to set qemu process's user & group to root in /etc/libvirt/qemu.conf.

Also as others have pointed out, there can be multiple other reasons for this error and its sad that libvirt throws such a generic error.

The least frustrating solution is to give all permissions, disable selinux and make sure that it runs. Now one by one revoke the permissions testing that it works at each step and finally understanding why you were required to give the final set of permissions.


This can happen, if the modules were loaded too soon™ (the actual problem is not known to me, so please enhance this answer if you know it).

Just try to unload the modules and load them again. This did the trick for me:

rmmod kvm_intel # use kvm-amd if you use an amd processor.
rmmod kvm
modprobe kvm
modprobe kvm_intel # use kvm-amd if you use an amd processor.


I got this permission denied error on Arch. The problem turned out to be the access control list. Even though the Unix permissions showed group rw, getfacl showed group::---. This fixed it for me:

setfacl -m g::rw /dev/kvm


I confronted with this same problem. And after look into it, I found it is a problem of permission. You can just run the command below to deal with it:

chown root:kvm /dev/kvm

and you don't need to reboot.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号