Sadly, I don't care to create and spin up KVM instances from a command line, I prefer (as I presume most people do) to use virt-manager.
When I set dynamic_ownership = 0, I am unable to boot due to a permission denied error:
Error starting domain: internal error: process exited while connecting to monitor: 2018-08-09T18:44:58.668207Z qemu-system-x86_64: -drive file=/home/bladernr/Downloads/bionic-live-server-amd64.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on: Could not open '/home/bladernr/Downloads/bionic-live-server-amd64.iso': Permission denied
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
self._backend.create()
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1062, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: 2018-08-09T18:44:58.668207Z qemu-system-x86_64: -drive file=/home/bladernr/Downloads/bionic-live-server-amd64.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on: Could not open '/home/bladernr/Downloads/bionic-live-server-amd64.iso': Permission denied
So if I change it back to 1 and restart libvirtd I can start KVM instances, but we're back to the original issue.
Is there some other setting necessary so virt-manager (running via my normal user) doesn't try launching things as the libvirt-kvm user, which is what I presume is the root of all this?
Thanks Christian.
Sadly, I don't care to create and spin up KVM instances from a command line, I prefer (as I presume most people do) to use virt-manager.
When I set dynamic_ownership = 0, I am unable to boot due to a permission denied error:
Error starting domain: internal error: process exited while connecting to monitor: 2018-08- 09T18:44: 58.668207Z qemu-system-x86_64: -drive file=/home/ bladernr/ Downloads/ bionic- live-server- amd64.iso, format= raw,if= none,id= drive-ide0- 0-1,readonly= on: Could not open '/home/ bladernr/ Downloads/ bionic- live-server- amd64.iso' : Permission denied
Traceback (most recent call last): virt-manager/ virtManager/ asyncjob. py", line 89, in cb_wrapper asyncjob, *args, **kwargs) virt-manager/ virtManager/ asyncjob. py", line 125, in tmpcb virt-manager/ virtManager/ libvirtobject. py", line 82, in newfn virt-manager/ virtManager/ domain. py", line 1508, in startup _backend. create( ) python2. 7/dist- packages/ libvirt. py", line 1062, in create 09T18:44: 58.668207Z qemu-system-x86_64: -drive file=/home/ bladernr/ Downloads/ bionic- live-server- amd64.iso, format= raw,if= none,id= drive-ide0- 0-1,readonly= on: Could not open '/home/ bladernr/ Downloads/ bionic- live-server- amd64.iso' : Permission denied
File "/usr/share/
callback(
File "/usr/share/
callback(*args, **kwargs)
File "/usr/share/
ret = fn(self, *args, **kwargs)
File "/usr/share/
self.
File "/usr/lib/
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error: process exited while connecting to monitor: 2018-08-
So if I change it back to 1 and restart libvirtd I can start KVM instances, but we're back to the original issue.
Is there some other setting necessary so virt-manager (running via my normal user) doesn't try launching things as the libvirt-kvm user, which is what I presume is the root of all this?
bladernr 15974 2.4 0.3 1269564 118660 ? Ssl 14:52 0:01 \_ /usr/bin/python2 /usr/share/ virt-manager/ virt-manager
root 5898 0.0 0.0 211108 7480 ? Ssl 13:11 0:00 /usr/sbin/virtlogd
root 15674 0.4 0.1 1894392 47552 ? Ssl 14:51 0:00 /usr/sbin/libvirtd
Or... also possible, am I just confused?